NetCube-Systems-Austria/kumquat-buildroot
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
bfafe9b3e9
kumquat-buildroot/toolchain/toolchain-buildroot/toolchain-buildroot.mk

21 lines
722 B
Makefile
Raw Normal View History

toolchain-buildroot: convert to the package infrastructure This commit converts the toolchain-buildroot logic to the package infrastructure. The package is fairly simple as it only defines BUILDROOT_LIBC, and depends on host-gcc-final to get the overall internal toolchain build logic started. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Acked-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2013-10-08 20:17:02 +02:00
################################################################################
#
# toolchain-buildroot
#
################################################################################
Rename BUILDROOT_LIBC to BR_LIBC No functional change, but internal variables should be name BR_foo, not BUILDROOT_foo (I think ..). Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2014-02-04 15:03:06 +01:00
BR_LIBC = $(call qstrip,$(BR2_TOOLCHAIN_BUILDROOT_LIBC))
toolchain-buildroot: convert to the package infrastructure This commit converts the toolchain-buildroot logic to the package infrastructure. The package is fairly simple as it only defines BUILDROOT_LIBC, and depends on host-gcc-final to get the overall internal toolchain build logic started. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Acked-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2013-10-08 20:17:02 +02:00
package/gcc/gcc-final: add a target variant in charge of target installation This commit adds a target package "gcc-final", which is a target package responsible for installing the gcc runtime libraries to STAGING_DIR and TARGET_DIR. This task was so far done by the host gcc-final package. The motivation for splitting it up into a target package is to be able to properly handle the licensing situation of GCC, where the host part of GCC (the compiler itself) is under GPLv3, but the runtime libraries on the target are under GPLv3-with-exception. So far, we were not handling at all the license of gcc. So what this commit does is: * Add a gcc-final target package, which is depended on by the toolchain-buildroot package, and which depends on host-gcc-final. * Moves to gcc-final the logic for installing target/staging libraries Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Signed-off-by: Romain Naour <romain.naour@smile.fr>
2023-09-30 09:54:22 +02:00
# Triggering the build of the gcc-final will automatically do the
toolchain-buildroot: convert to the package infrastructure This commit converts the toolchain-buildroot logic to the package infrastructure. The package is fairly simple as it only defines BUILDROOT_LIBC, and depends on host-gcc-final to get the overall internal toolchain build logic started. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Acked-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2013-10-08 20:17:02 +02:00
# build of binutils, uClibc, kernel headers and all the intermediate
# gcc steps.
package/gcc/gcc-final: add a target variant in charge of target installation This commit adds a target package "gcc-final", which is a target package responsible for installing the gcc runtime libraries to STAGING_DIR and TARGET_DIR. This task was so far done by the host gcc-final package. The motivation for splitting it up into a target package is to be able to properly handle the licensing situation of GCC, where the host part of GCC (the compiler itself) is under GPLv3, but the runtime libraries on the target are under GPLv3-with-exception. So far, we were not handling at all the license of gcc. So what this commit does is: * Add a gcc-final target package, which is depended on by the toolchain-buildroot package, and which depends on host-gcc-final. * Moves to gcc-final the logic for installing target/staging libraries Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Signed-off-by: Romain Naour <romain.naour@smile.fr>
2023-09-30 09:54:22 +02:00
TOOLCHAIN_BUILDROOT_DEPENDENCIES = gcc-final
toolchain-buildroot: convert to the package infrastructure This commit converts the toolchain-buildroot logic to the package infrastructure. The package is fairly simple as it only defines BUILDROOT_LIBC, and depends on host-gcc-final to get the overall internal toolchain build logic started. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Acked-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2013-10-08 20:17:02 +02:00
package: add toolchain dependency to every target package This commit makes the dependency from the target toolchain explicit. This way we can buid from command line a package that use inner-generic-package right after the configuration phase, example: make clean <package-name> Also remove TARGETS_ALL because the only purpose was to add toolchain dependency so it's superseded by this commit. To prevent circular dependency add the new variable <pkgname>_ADD_TOOLCHAIN_DEPENDENCY to avoid adding the toolchain dependency for toolchain packages. This is also a step forward supporting top-level parallel make. Signed-off-by: Fabio Porcedda <fabio.porcedda@gmail.com> Acked-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2014-02-14 10:55:04 +01:00
TOOLCHAIN_BUILDROOT_ADD_TOOLCHAIN_DEPENDENCY = NO
toolchain/toolchain-buildroot: add comment about using virtual package infra Commit "9a8ec9195c toolchain/toolchain-buildroot: migrate to virtual package infrastructure" made the packages toolchain and toolchain-buildroot to use the virtual package infra even they being generic packages. This works because on package/pkg-virtual.mk when a package do not define neither _PROVIDES_ or _HAS_ symbols, only _IS_VIRTUAL is set to YES and _VERSION and _SOURCE are set to empty before relaying the call to inner-generic-package. Add a comment explaining why the virtual package infra is used in these cases. Cc: Giulio Benetti <giulio.benetti@benettiengineering.com> Cc: Romain Naour <romain.naour@gmail.com> Cc: Thomas De Schampheleire <thomas.de_schampheleire@nokia.com> Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Cc: Yann E. MORIN <yann.morin.1998@free.fr> Signed-off-by: Ricardo Martincoski <ricardo.martincoski@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2022-11-27 14:07:27 +01:00
# Not really a virtual package, but we use the virtual package infra here so
# both the build log and build directory look nicer (toolchain-buildroot-virtual
# instead of toolchain-buildroot-undefined)
toolchain/toolchain-buildroot: migrate to virtual package infrastructure This patch migrates the toolchain and toolchain-buildroot packages to the virtual package infrastructure, causing the log messages to change from: >>> toolchain undefined Downloading >>> toolchain undefined Extracting ... to >>> toolchain virtual Downloading >>> toolchain virtual Extracting ... and similar for 'toolchain-buildroot', simply because it looks nicer. At the same time, the directory names also become toolchain-virtual, toolchain-buildroot-virtual instead of the corresponding 'undefined' variants. Signed-off-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com> Acked-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Acked-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2014-06-11 21:12:27 +02:00
$(eval $(virtual-package))
Reference in New Issue Copy Permalink