7ae2b8ef88
Split out the information on hooks to a separate section (and source file). Not only because the hooks are useful for all infrastructures (and thus don't really fit specifically in the generic infrastructure section), but also for clarity when the info on hooks will be expanded in later patches. Signed-off-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com> Acked-by: Samuel Martin <s.martin49@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
28 lines
684 B
Plaintext
28 lines
684 B
Plaintext
// -*- mode:doc; -*-
|
|
// vim: set syntax=asciidoc:
|
|
|
|
[[adding-packages]]
|
|
Adding new packages to Buildroot
|
|
--------------------------------
|
|
|
|
This section covers how new packages (userspace libraries or
|
|
applications) can be integrated into Buildroot. It also shows how
|
|
existing packages are integrated, which is needed for fixing issues or
|
|
tuning their configuration.
|
|
|
|
include::adding-packages-directory.txt[]
|
|
|
|
include::adding-packages-generic.txt[]
|
|
|
|
include::adding-packages-autotools.txt[]
|
|
|
|
include::adding-packages-cmake.txt[]
|
|
|
|
include::adding-packages-hooks.txt[]
|
|
|
|
include::adding-packages-gettext.txt[]
|
|
|
|
include::adding-packages-tips.txt[]
|
|
|
|
include::adding-packages-conclusion.txt[]
|