-
Notifications
You must be signed in to change notification settings - Fork 163
Partial builds on CI cross targets #96
Comments
From what I can see, the issue seems to lie in these lines of the android build log:
I am a bit of a noob when it comes to config, so I will need a bit of guidance. Would I simply be setting environment variables to the openssl binary and setting the cross-compilation flag to true, or is it a bit more complicated than that? |
Welcome @ifkb99! Great to see you. I'd suggest trying out your instincts here and seeing how far that gets you. They sound correct, as that would be the first thing I'd try. |
Thanks for the warm welcome! I am looking to add the line |
Welcome from me as well!
I don't think any kind of exploration access is available. The system doing the cross compilation should be quite the usual boring ubuntu though. Could be that the issue is nothing more than the env variable you mentioned to 1. You should be able to try this if you just fork the repo, add the env variable and create a pull request. If you don't want to do a work in progress PR you can adjust the first section of .github/workflows/ci.yml to run on all pushed branches to get a CI run on your forked repo. |
You could also try Edit: or |
During #95 I excluded building
rust-http-ipfs
on cross targets (incl. android). Fixing this probably isn't anything else than to find/add the prebuiltopenssl-sys
friendly packages for the cross targets. Could also be that the env variable just needed to be set, as mentioned byopenssl-sys
build script.See https://github.com/ipfs-rust/rust-ipfs/runs/503319261 where the android builds failed and macos cross builds were not actually run because I fumbled
--target xyz
away from the build command by mistake.The logs are not loading as of writing this so hopefully they'll work later on.
The text was updated successfully, but these errors were encountered: