-
-
Notifications
You must be signed in to change notification settings - Fork 228
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to start Octodash with mdns on Pi3 #1033
Comments
mdns also gave me a lot of headaches. Replaced it with bonjour already (which doesn't rely on gyp to be build and I think (not tested though) does not require libavahi-compat-libdnssd-dev. It's in this branch: https://github.com/UnchartedBull/OctoDash/tree/fix/text-wrap let me know if it works :) |
Nice man ! One more point, the screen is very long to respond as mentioned in this issue #838 |
you would need to pack on the arm you can't pack it on x86 and run it on arm as it's building static binaries. |
Yes, I understood that if i pack on x86 or x64, the binaries are building for those arch. I'm sorry if I miss some information that can be obvious. I will re-test with mdns when I will have a pi 4 as I can't build it on Pi3. Did you manage to build it on Pi3 ? |
I did it on Pi4, but I"ll test it on Pi3 tonight I have one some place ;). But the Pi4 binary should work on Pi3 as they are both armhf That being said the changes that UnchartedBull made should negate the need to build a static version of mdns I believe. |
This issue is now solved. |
Describe the bug
Since 6458cc6, i'm not able to build and launch Octodash on my Pi3.
I know that we need Zeroconf/libavahi-compat-libdnssd-dev.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Octodash launch on Raspberry
General Information:
Additional context
npm start is working correctly on ubuntu and MacOS as mdns is correctly build for the arch
We probably need to build and compile on raspberry but the pi3 doesn't enough ressources for this. Maybe a Pi4 can do the job...
The text was updated successfully, but these errors were encountered: