Describe the bug
The xvenv environment created for Android contains definitions for CC and other build tools that reference the full path to ANDROID_HOME on the machine where Python was built.
Steps to reproduce
- Create and activate an Android xvenv
- Run `python -c "import sysconfig; print(sysconfig.get_config_var('CC'))"
- See a path like
/Users/msmith/Library/Android/sdk/ndk/27.2.12479018/toolchains/llvm/prebuilt/darwin-x86_64/bin/aarch64-linux-android21-clang, even if you're not msmith.
Expected behavior
Portions of the sysconfig file that include references to the build machine (especially ANDROID_HOME) should be delocalised.
Screenshots
No response
Environment
- Operating System: Any (but targing Android)
- Python version: 3.13.5
- Software versions:
Logs
Additional context
cibuildwheel avoids this by invoking android_env.sh to set variables in the Android environment. It may be appropriate for xbuild to do the same - although it's unclear where that environmental configuration would be applied.
Describe the bug
The
xvenvenvironment created for Android contains definitions for CC and other build tools that reference the full path toANDROID_HOMEon the machine where Python was built.Steps to reproduce
/Users/msmith/Library/Android/sdk/ndk/27.2.12479018/toolchains/llvm/prebuilt/darwin-x86_64/bin/aarch64-linux-android21-clang, even if you're not msmith.Expected behavior
Portions of the sysconfig file that include references to the build machine (especially
ANDROID_HOME) should be delocalised.Screenshots
No response
Environment
Logs
Additional context
cibuildwheelavoids this by invokingandroid_env.shto set variables in the Android environment. It may be appropriate forxbuildto do the same - although it's unclear where that environmental configuration would be applied.