2012-11-11 04:14:42 +01:00
|
|
|
// -*- mode:doc; -*-
|
2013-02-13 13:59:02 +01:00
|
|
|
// vim: set syntax=asciidoc:
|
2012-11-11 04:14:42 +01:00
|
|
|
|
manual: high-level restructuring
The structure of the buildroot manual is not always clear. There is a large
number of chapters, and some chapters seem to overlap. The distinction
between general usage and developer information is not always clear.
This patch restructures the manual into four large parts:
- getting started
- user guide
- developer guide
- appendix
Except for the names of these parts, the section names are not yet changed.
Content-wise there are no changes yet either. This will be handled in
subsequent patches.
In order to achieve the introduction of a new level 'parts' above
'chapters', the section indicators (=, ==, ===, ...) of several sections
have to be moved one level down. Additionally, the leveloffset indication to
asciidoc has to be removed. Finally, to maintain more or less the same level
of detail in the table of contents, the toc.section.depth attribute is
reduced as well. Note that for some sections, less detail is visible now.
Signed-off-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2014-08-12 22:20:06 +02:00
|
|
|
==== Using the generated toolchain outside Buildroot
|
2011-10-10 10:46:39 +02:00
|
|
|
|
|
|
|
|
You may want to compile, for your target, your own programs or other
|
|
|
|
|
software that are not packaged in Buildroot. In order to do this you
|
|
|
|
|
can use the toolchain that was generated by Buildroot.
|
|
|
|
|
|
|
|
|
|
The toolchain generated by Buildroot is located by default in
|
|
|
|
|
+output/host/+. The simplest way to use it is to add
|
2017-07-05 13:14:32 +02:00
|
|
|
+output/host/bin/+ to your PATH environment variable and then to
|
2011-10-10 10:46:39 +02:00
|
|
|
use +ARCH-linux-gcc+, +ARCH-linux-objdump+, +ARCH-linux-ld+, etc.
|
|
|
|
|
|
2018-02-18 15:50:42 +01:00
|
|
|
It is possible to relocate the toolchain, this allows to distribute
|
|
|
|
|
the toolchain to other developers to build applications for your
|
|
|
|
|
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.
|
2011-10-10 10:46:39 +02:00
|
|
|
|
