-
-
Notifications
You must be signed in to change notification settings - Fork 229
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
Build system does not work with Android NDK cross compiler #111
Comments
A possible approach is to include a config.h database. These are files copied from known platforms identified by their target triples. When cross-compilation is detected, only feature flags (like --enable-vfs) are checked. Other #defines are copied from the database. |
Hello @truboxl, Well, it looks like there are not that many programs that have good support for Canadian Cross setups, where the build, host, and target (or should we say "guest") platforms might all potentially be different. To allow for {build platform} ≠ {host platform}, a possible fix might be to allow the
but maybe instead of running Yet another more simplistic alternative might be to skip the Thank you! |
Contributions welcome |
The
configure
script operates on the basis that tests are compiled and run on build machine.config.h
andconfig.mk
are generated so that finalblink
binary works on the build machine.This does not work for Android in which Android NDK are cross compilers.
configure
tests are cross compiled, erroneously run on build machine, failed and disabling all features.Example log: https://github.com/termux/termux-packages/actions/runs/4768306570/jobs/8477478253#step:6:426
My past effort but abandoned:
https://github.com/truboxl/termux-packages/pull/88/files
https://github.com/truboxl/termux-packages/pull/91/files
Any chance to improve this situation?
Will manually intervene
config.h
andconfig.mk
for now downstream...The text was updated successfully, but these errors were encountered: