c++ - Android Building Toolchain can't find/missing STL header directory -


I have manually built Android NDK Toolchain. By the time I use the compiler, everything works, it can not be found like the original STL stuff. Therefore, it can not compile the STL code because it is not known where to look for the header by default. I have never had this problem before using custom or prebuilt toolchain, however, if you add manually added directories, then

  -i $ (NDK_TOOLCHAIN) / arm-linux-androidb / Incorporate / C ++ / 4.6 /   

Then it works just fine. It is a pain to manually add every important dior (this is more than one). Certainly some process is broken.

This is the following steps for the actions I have made:

  download sudo apt-get git-core gnupg flex bison gperf build-essential zip curl download NDK pomegranate NDK Do / FTP / NDK / NDK_ROOT = / OPT / NDK / Download / MPC Tower / SRC / MPC / ./build/tools/build-gcc.sh --gmp-version = 4.3 by using / build / tools / download-toolchain-associates.sr src / download MPC 0.9 .2 - MPC-version = 0.9 - MPFR-version = 2.4.2 - Binet-version = $ 2.21 (pwd) arm-linux-androideabi-4.6 ./build/tools/build- Gcc.sh --gmp-version = 4.3.2 --mpc-version = 0.9 --mpfr-version = 2.4.2 - -benit-version = 2.21 $ (pwd) / src $ (pwd) x86-4.6 ./ Build / tools / build -gcc.sh --gmp-version = 4.3.2 - MPC-version = 0.9 - mp3 F-version = 2.4.2 --Binet-version = 2.21 $ (PWD) / src $ (PWD) mipsel-linux-android-4.6   

All STL files are in the proper place . All the headers and the compiled libraries for each customer if I create a standalone toolchain after using these custom made toolchains as reference.

== UPDATE

GCC spitting Forcing the search path to include:

  echo "#include  int main) {}" & gt; T.c; / Opt / android-9_arm / bin / arm-linux-androideabi-gcc -v t.c; RM TC   

contains a search path in it:

  /opt/android-9_arm/bin/../lib/gcc/arm- Linux -AndroidEb / 4.6.x-google /../../../../Hand-Linux-AndroidB / Include   

is really low at that place. / Cxx / 4.6 / STL_Headers

The comparison of outputs to Google with NDK build is actually different in serious places. The real question is how do I get the G-5 STL header location appropriate for my custom GCC construction? Guarantee.

It was a bug in Make-Stand-with-Tolkien shots: < Previous> mv $ NDK_TOLCHAIN ​​/ arm-linux-androideabi / include / c ++ / 4.6 $ NDK_TOLCHAIN ​​/ hand-linux-androideabi / include / c ++ / 4.6.x-google

He fixed it for the most part. However now it is that ndkr8b has released this bug image with official GCC 4.6 support (till July 25, 2012). More details on some bugs related to standalone toolchain (http://code.google.com/p/android/issues/detail?id=35279)

Comments

Popular posts from this blog

Python SQLAlchemy:AttributeError: Neither 'Column' object nor 'Comparator' object has an attribute 'schema' -

java - How not to audit a join table and related entities using Hibernate Envers? -

mongodb - CakePHP paginator ignoring order, but only for certain values -