Opened 10 years ago
Closed 10 years ago
#7527 closed Bugs (fixed)
Compilation broken on Android
Reported by: | anonymous | Owned by: | John Maddock |
---|---|---|---|
Milestone: | To Be Determined | Component: | TR1 |
Version: | Boost 1.52.0 | Severity: | Problem |
Keywords: | Cc: | psiha@… |
Description
Before using boost::tr1 when ANDROID is defined I have to "help" boost\tr1\detail\config_all.hpp with: #define BOOST_TR1_GCC_INCLUDE_PATH include. Otherwise the wrong path is deduced and compilation fails (tested with ANDROID NDK r8b and the GCC 4.6 toolset).
Change History (6)
comment:1 by , 10 years ago
Cc: | added |
---|
comment:2 by , 10 years ago
Cc: | removed |
---|---|
Component: | None → TR1 |
Owner: | set to |
comment:3 by , 10 years ago
Cc: | added |
---|
comment:4 by , 10 years ago
comment:5 by , 10 years ago
As written in the description, it "should" be defined to simply "include". I placed "should" in quotes because this is what "worked for me" with NDK versions r8b and r8c and the GCC 4.6 toolset. In the current NDK r8d there are the GCC 4.4, 4.6, 4.7 and Clang 3.1 toolsets and maybe these require different treatment (haven't tested)...
The Android NDK does not require installation, merely unpacking from an archive (http://developer.android.com/tools/sdk/ndk/index.html) so you might be able to deduce the "correct course of action" by merely inspecting the (include) directory structure...
comment:6 by , 10 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Do you have a patch? To what should BOOST_TR1_GCC_INCLUDE_PATH be set?
Thanks.