mirror of
https://gitlab.com/buildroot.org/buildroot.git
synced 2026-09-30 22:11:59 -09:00
docs/manual: add documentation for the "make sdk" target
Signed-off-by: Daniel Serpell <daniel.serpell@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
This commit is contained in:
committed by
Thomas Petazzoni
parent
2b170210c9
commit
d61e4ad9ef
@@ -12,11 +12,15 @@ The toolchain generated by Buildroot is located by default in
|
|||||||
+output/host/bin/+ to your PATH environment variable and then to
|
+output/host/bin/+ to your PATH environment variable and then to
|
||||||
use +ARCH-linux-gcc+, +ARCH-linux-objdump+, +ARCH-linux-ld+, etc.
|
use +ARCH-linux-gcc+, +ARCH-linux-objdump+, +ARCH-linux-ld+, etc.
|
||||||
|
|
||||||
It is possible to relocate the toolchain - but then +--sysroot+ must
|
It is possible to relocate the toolchain, this allows to distribute
|
||||||
be passed every time the compiler is called to tell where the
|
the toolchain to other developers to build applications for your
|
||||||
libraries and header files are.
|
target. To achieve this:
|
||||||
|
|
||||||
|
* run +make sdk+, which prepares the toolchain to be relocatable;
|
||||||
|
* tarball the contents of the +output/host+ directory;
|
||||||
|
* distribute the resulting tarball.
|
||||||
|
|
||||||
|
Once the toolchain is installed to the new location, the user must run
|
||||||
|
the +relocate-sdk.sh+ script to make sure all paths are updated with
|
||||||
|
the new location.
|
||||||
|
|
||||||
It is also possible to generate the Buildroot toolchain in a directory
|
|
||||||
other than +output/host+ by using the +Build options -> Host dir+
|
|
||||||
option. This could be useful if the toolchain must be shared with
|
|
||||||
other users.
|
|
||||||
|
|||||||
Reference in New Issue
Block a user