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
Building our library with NDK 14 on windows results in an unresolved symbol when loading our shared library of stderr on Android 5.0/5.1. It is ok on 6 & above
We used the following command to create the standalone toolchain
python build\tools\make_standalone_toolchain.py --arch arm --api 21 --unified-headers --install-dir=e:\compilers\android\android-ndk-r14-arm --stl=libc++
The result of this is that the bash scripts bin/clang & bin/clang++ pass -D ANDROID_API=21 to clang38
but the bin/clang.cmd & bin/clang++.cmd do not add the define. I think this is a bug in the generation scripts and I don't believe from the documentation of unified headers that we are supposed to pass that define to the compiler when using the standalone toolchain.
Environment Details
Not all of these will be relevant to every bug, but please provide as much
information as you can.
NDK Version: Value: 14
Build sytem:standalone toolchain/ custom?
Host OS: Windows,
Compiler: clang.
ABI:
STL: libc++
NDK API level: 21
Device API level:
The text was updated successfully, but these errors were encountered:
We rebuild the list of flags when we create the Windows standalone
toolchains since we need to use batch variables/paths instead. Add
the unified headers flags there too.
This slipped by before because the standalone toolchain tests were
still disabled on Windows from back when they weren't supported there.
I enabled them recently so those are being run now.
Test: ./validate.py # On Windows.
Bug: android/ndk#321
Change-Id: I5f00e6469343f5bbe6c0d415eed2b27d11184ba0
(cherry picked from commit d90623e)
We rebuild the list of flags when we create the Windows standalone
toolchains since we need to use batch variables/paths instead. Add
the unified headers flags there too.
This slipped by before because the standalone toolchain tests were
still disabled on Windows from back when they weren't supported there.
I enabled them recently so those are being run now.
Test: ./validate.py # On Windows.
Bug: android/ndk#321
Change-Id: I5f00e6469343f5bbe6c0d415eed2b27d11184ba0
Description
Building our library with NDK 14 on windows results in an unresolved symbol when loading our shared library of stderr on Android 5.0/5.1. It is ok on 6 & above
We used the following command to create the standalone toolchain
python build\tools\make_standalone_toolchain.py --arch arm --api 21 --unified-headers --install-dir=e:\compilers\android\android-ndk-r14-arm --stl=libc++
The result of this is that the bash scripts bin/clang & bin/clang++ pass -D ANDROID_API=21 to clang38
but the bin/clang.cmd & bin/clang++.cmd do not add the define. I think this is a bug in the generation scripts and I don't believe from the documentation of unified headers that we are supposed to pass that define to the compiler when using the standalone toolchain.
Environment Details
Not all of these will be relevant to every bug, but please provide as much
information as you can.
The text was updated successfully, but these errors were encountered: