569db40574
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>
81 lines
2.4 KiB
Plaintext
81 lines
2.4 KiB
Plaintext
// -*- mode:doc; -*-
|
|
// vim: set syntax=asciidoc:
|
|
|
|
[[pkg-build-steps]]
|
|
|
|
==== Package-specific _make_ targets
|
|
|
|
Running +make <package>+ builds and installs that particular package
|
|
and its dependencies.
|
|
|
|
For packages relying on the Buildroot infrastructure, there are
|
|
numerous special make targets that can be called independently like
|
|
this:
|
|
|
|
------------
|
|
make <package>-<target>
|
|
------------
|
|
|
|
The package build targets are (in the order they are executed):
|
|
|
|
[width="90%",cols="^1,4",options="header"]
|
|
|===================================================
|
|
| command/target | Description
|
|
|
|
| +source+ | Fetch the source (download the tarball, clone
|
|
the source repository, etc)
|
|
|
|
| +depends+ | Build and install all dependencies required to
|
|
build the package
|
|
|
|
| +extract+ | Put the source in the package build directory
|
|
(extract the tarball, copy the source, etc)
|
|
|
|
| +patch+ | Apply the patches, if any
|
|
|
|
| +configure+ | Run the configure commands, if any
|
|
|
|
| +build+ | Run the compilation commands
|
|
|
|
| +install-staging+ |
|
|
*target package:* Run the installation of the package in the
|
|
staging directory, if necessary
|
|
|
|
| +install-target+ |
|
|
*target package:* Run the installation of the package in the
|
|
target directory, if necessary
|
|
|
|
| +install+ |
|
|
*target package:* Run the 2 previous installation commands
|
|
|
|
*host package:* Run the installation of the package in the host
|
|
directory
|
|
|
|
|===================================================
|
|
|
|
Additionally, there are some other useful make targets:
|
|
|
|
[width="90%",cols="^1,4",options="header"]
|
|
|===================================================
|
|
| command/target | Description
|
|
|
|
| +show-depends+ | Displays the dependencies required to build the
|
|
package
|
|
|
|
| +graph-depends+ | Generate a dependency graph of the package, in the
|
|
context of the current Buildroot configuration. See
|
|
xref:graph-depends[this section] for more details about dependency
|
|
graphs.
|
|
|
|
| +dirclean+ | Remove the whole package build directory
|
|
|
|
| +rebuild+ | Re-run the compilation commands - this only makes
|
|
sense when using the +OVERRIDE_SRCDIR+ feature or when you modified a file
|
|
directly in the build directory
|
|
|
|
| +reconfigure+ | Re-run the configure commands, then rebuild - this only
|
|
makes sense when using the +OVERRIDE_SRCDIR+ feature or when you modified a
|
|
file directly in the build directory
|
|
|
|
|===================================================
|