Skip to content
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

Improve Android cross-compile scenario by covering extra cases #3842

Open
uilianries opened this issue Sep 16, 2024 · 1 comment
Open

Improve Android cross-compile scenario by covering extra cases #3842

uilianries opened this issue Sep 16, 2024 · 1 comment
Assignees

Comments

@uilianries
Copy link
Member

Greetings, this issue is a follow-up over #3351 and conan-io/conan-center-index#24915

The current documentation https://docs.conan.io/2/examples/cross_build/android/ndk.html#examples-cross-build-android-ndk shows how to cross-compile to Android by using a NDK installed in the system in a very regular case using CMake. It works for the example, but when exploring other cases, like trying to build using autotools or not well prepared project, it may fail.

It would be nice updating the documentation by adding some hints, as cross-building is always a harder scenario and not always work at first try, being frustrating for users.

  • Add android-ndk/r25c as tool-requirement, as alternative. That CCI package configures everything already, including ndk-path.
  • Complement the configuration with compiler path (tools.build:compiler_executables) to cover other scenarios when ndk path is not enough (e.g. Boost recipe using B2)

/cc @cjserio @neobrain

@neobrain
Copy link

Might be helpful to collect more packages here that don't compile with the recipe from the documentation:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants