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

Making Android toolchain portable #115

Open
FeodorFitsner opened this issue Apr 25, 2024 · 2 comments
Open

Making Android toolchain portable #115

FeodorFitsner opened this issue Apr 25, 2024 · 2 comments

Comments

@FeodorFitsner
Copy link

Thank you for the great tool!

In our case host Python distributive is built on VM with Android SDK installed at /usr/lib/android-sdk/ndk/26.2.11394342/toolchains/llvm/prebuilt/linux-x86_64 and if a user has toolchain installed in a different location this host python, obviously, does not work with crossenv on their machine.

I see original toolchain path presents in multiple files:

  • bin/python3-config
  • bin/python3.12-config
  • lib/python3.12/_sysconfigdata__linux_.py
  • lib/python3.12/config-3.12/Makefile

What would be the solution to make crossenv and host-python to work with Android toolchain in location, different from the one Python was built with?

Is there an already some option in crossenv? Would simple find-replace over those files work?

@benfogle
Copy link
Owner

Sorry, I somehow missed this issue.

Crossenv has a --relative-toolchain option that should do what you want. You will just need to make sure that the SDK binaries are in $PATH.

@FeodorFitsner
Copy link
Author

Will give it a try!

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

2 participants