What is a separate toolchain?

Question

I am trying to understand what a separate toolchain means. Below are my findings. A toolchain that is ready for use with the entire configuration, which are the headers and libraries of the system in the right way. For Android, it will also have API headers in the path where the toolchain can find it. Why is the term "standalone"? This is likely to differ from the regular toolchain in the sense that RT will need to be configured and prepared for use in android using the sysroot and libc header paths, etc. Please comment.

Hmm, I compiled for android, and one process ran a script called make-standalone-toolchain.sh. An autonomous toolchain has been created. I went through this script to understand what this does. The shell script does not work very well. But he did certain things. Msgstr "Create a custom Android tool installation that includes a working sine. The result is something that can be more easily used as a stand-alone cross-compiler, for example, to run configure and create scripts." - toolchain arch ndk-dir. Platform parameters system-dir system platform installed. Computing Source sysroot SRC_SYSROOT = "$ NDK_DIR / platform / $ PLATFORM arch- $ ARCH" Copying sysroot headers and libraries ... libstdC ++ headers and libraries ... pre-created binaries.all to a temporary folder and then copying from the Tmp directory for installation, dir creates tar, i.e. the package file for adding tmpdir wanted to know what exactly is happening here, or a link or suggestion where to look. But, of course, you do not want to read very complex manuals. ~

Answer 1

This blog post may answer your question:

http://clseto.mysinablog.com/index.php?op=ViewArticle&articleId=3480794

There is a recommended way to create your own C / C ++ program on Android: list the source files in the script (Android.mk) and run 'ndk-build'. It may not be a problem if you are writing new programs, but if you already have a working script build (for example, open source software) that can build your program on Linux well, it would be a headache to port your script to Android .mk. All you need in this situation is the C / C ++ cross-compiler, and then replace the variables in the script (e.g. CC, CXX, AR, AS, RANLIB, ...) with something like "arm-linux- androideabi- gcc ',' arm-linux-androideabi-g ++ ', ...

Fortunatley, inside the “Android NDK Dev Guide”, there is a section “Standalone Toolchain” that simply describes what we need ....