# HG changeset patch # User Trevor Woerner # Date 1321477602 18000 # Node ID 710fa859bfe675d1ecb0cbe08657fa75f3566f99 # Parent c4452a1a18fb5c57b991eb75f7ff480d33e91704 docs: --target versus --host In the very beginnings, eons ago, autotools also got confused by this whole build vs. host vs. target, and got it wrong. Now they fixed it, but they want to keep backward compatibility, so the --target is still recongised, although ./configure will complain if you do so. It is better to use --host. Signed-off-by: "Trevor Woerner" [yann.morin.1998@anciens.enib.fr: add build/host clarification] Signed-off-by: "Yann E. MORIN" diff -r c4452a1a18fb -r 710fa859bfe6 docs/5 - Using the toolchain.txt --- a/docs/5 - Using the toolchain.txt Tue Nov 15 19:11:57 2011 +0100 +++ b/docs/5 - Using the toolchain.txt Wed Nov 16 16:06:42 2011 -0500 @@ -11,15 +11,20 @@ your PATH, such as: export PATH="${PATH}:/your/toolchain/path/bin" -and then using the target tuple to tell the build systems to use your -toolchain: - ./configure --target=your-target-tuple +and then using the '--host' tuple to tell the build systems to use your +toolchain (if the software package uses the autotools system you should +also pass --build, for completeness): + ./configure --host=your-host-tuple --build=your-build-tuple or - make CC=your-target-tuple-gcc + make CC=your-host-tuple-gcc or - make CROSS_COMPILE=your-target-tuple- + make CROSS_COMPILE=your-host-tuple- and so on... +(Note: in the above example, 'host' refers to the host of your program, +not the host of the toolchain; and 'build' refers to the machine where +you build your program, that is the host of the toolchain.) + It is strongly advised not to use the toolchain sysroot directory as an install directory for your programs/packages. If you do so, you will not be able to use your toolchain for another project. It is even strongly advised