-
Notifications
You must be signed in to change notification settings - Fork 44
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
Compilation issues for --target armv7-unknown-linux-gnueabihf
#68
Comments
After some painful hours, I've figured out a way to cross compile to armv7-unknown-linux-gnueabihf from an Ubuntu host. I mostly ran into errors with openssl and sqlite3, so I had to add and update some dependencies in the Cargo.toml to fix these. openssl = { version = "0.10.41", features = ["vendored"] } And r2d2_sqlite = { version = "0.21.0", features = ["bundled"] } These are the commands I had to use for the compiler to succeed:
If you are coss compiling to armv7, you also have to add the following to
If this file and folder don’t exist, you’ll have to create them yourself. |
hi @WarmBeer in the docker configuration I'm working on here, I'm using a docker image that probably does that internally. It works with I think we could add a GitHub workflow to test cross-compilations like this. We can start with only this case for the time being so we do not lose this information. I think it's very important to know the exact dependencies of the program to ensure it runs in as many systems as possible. This could be a pain if we keep adding more and more "hidden" or unexplicit indirect dependencies. At least with the docker configuration, I'm working we know well the dependencies for one system. |
Torrust won't compile to armv7-unknown-linux-gnueabihf (Raspberry Pi etc..).
The text was updated successfully, but these errors were encountered: