f08a7f3fc5
This provides generic functions for Qt5 qmake based packages. It will
make it possible to remove lots of redefinition of
QT5_xxx_{CONFIGURE|BUILD|INSTALL_STAGING}_CMDS. Additionally it
provides a generic target install method which will make most of the
package specific commands obsolete.
This is done by re-running the install step of the qmake generated
Makefile with the package build directory prepended (to the
staging/host path). Even though this does create lengthy pathes it
allows for easy separation of the staging files from the host destined
files by just omitting the resulting BUILD_DIR+HOST_DIR path from the
following rsync call to the real target folder. The cleanup of many
files we dont want in target is deferred to the target-finalize
step. In addition to what's being removed already, we also have to
cleanup some Qt5 specific files (prl) and the documentation directory.
This approach was chosen over copying all files recorded in the pkg-files-list
after some discussion which Thomas Petazzoni summed up:
"We don't yet use pkg-files-list really as part of the build
process anywhere, I feel a bit more comfortable at this point with what
Andreas is proposing."
Thanks to this infrastructure, it will be possible to get rid of the
many conditional install commands because qmake already takes care of
this when generating the Makefile install targets with the given or
autodetected configure options of each package.
However, custom install steps may have to remain in cases where a
particular Buildroot option has no corresponding setting in the
packages configuration options.
Signed-off-by: Andreas Naumann <anaumann@ultratronik.de>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
59 lines
1.4 KiB
Plaintext
59 lines
1.4 KiB
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.
|
|
|
|
When you add a new package, be sure to test it in various conditions
|
|
(see xref:testing-package[]) and also check it for coding style (see
|
|
xref:check-package[]).
|
|
|
|
include::adding-packages-directory.txt[]
|
|
|
|
include::adding-packages-generic.txt[]
|
|
|
|
include::adding-packages-autotools.txt[]
|
|
|
|
include::adding-packages-cmake.txt[]
|
|
|
|
include::adding-packages-python.txt[]
|
|
|
|
include::adding-packages-luarocks.txt[]
|
|
|
|
include::adding-packages-perl.txt[]
|
|
|
|
include::adding-packages-virtual.txt[]
|
|
|
|
include::adding-packages-kconfig.txt[]
|
|
|
|
include::adding-packages-rebar.txt[]
|
|
|
|
include::adding-packages-waf.txt[]
|
|
|
|
include::adding-packages-meson.txt[]
|
|
|
|
include::adding-packages-cargo.txt[]
|
|
|
|
include::adding-packages-golang.txt[]
|
|
|
|
include::adding-packages-qmake.txt[]
|
|
|
|
include::adding-packages-kernel-module.txt[]
|
|
|
|
include::adding-packages-asciidoc.txt[]
|
|
|
|
include::adding-packages-linux-kernel-spec-infra.txt[]
|
|
|
|
include::adding-packages-hooks.txt[]
|
|
|
|
include::adding-packages-gettext.txt[]
|
|
|
|
include::adding-packages-tips.txt[]
|
|
|
|
include::adding-packages-conclusion.txt[]
|