You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ld: error: undefined symbol: __extenddftf2
>>> referenced by sqlite3.c
>>> sqlite3.o:(sqlite3_str_vappendf) in archive /target/x86_64-linux-android/release/deps/liblibsqlite3_sys-a59c0c668a489339.rlib
>>> referenced by sqlite3.c
>>> sqlite3.o:(sqlite3_str_vappendf) in archive /target/x86_64-linux-android/release/deps/liblibsqlite3_sys-a59c0c668a489339.rlib
>>> referenced by sqlite3.c
>>> sqlite3.o:(sqlite3_str_vappendf) in archive /target/x86_64-linux-android/release/deps/liblibsqlite3_sys-a59c0c668a489339.rlib
>>> referenced 6 more times
This PR adds a GH workflow that builds across platforms, specifically the android platforms referenced in the cross_build.sh scripts, but can be extended to build for others. It seems like one of the next steps is to hook up version publishing in general for these packages/platforms, but this PR just focuses on getting the builds running in CI for continuous validation/testing and further iteration. The builds are still relatively slow in CI, taking about 15 minutes to complete, but not nearly as slow as when running locally on a mac via qemu.
https://github.com/bitcoindevkit/bdk-ffi/blob/master/.github/workflows/publish-android.yaml seems like a good example of the full build + publish workflow that we'd want to evolve this into.
Note that the `x86_64-linux-android` build is failing, with some context in #134. I spent some time trying to figure this out, unsuccessfully, and ultimately decided to spin up an issue to track it separately and get a PR up for the builds that work.
Example: https://github.com/xmtp/libxmtp/actions/runs/5166007186/jobs/9305846305
This seems to happen both in CI and locally.
Related errors reports:
__extenddftf2
termux/termux-packages#14576cannot locate symbol "__extendsftf2"
termux/termux-packages#8029The text was updated successfully, but these errors were encountered: