diff options
author | Stewart Smith <stewart@linux.vnet.ibm.com> | 2015-08-27 13:02:09 +1000 |
---|---|---|
committer | Joel Stanley <joel@jms.id.au> | 2019-03-05 13:30:28 +1030 |
commit | be24e9e7aa684569ccfd0435678477db37a33d99 (patch) | |
tree | 8293cefae5b4e4a09664c782c8f5bf9a23ffad2f /package/python-oauthlib/python-oauthlib.mk | |
parent | b9674056fbe8d37c1b11ad524075f21dc5deaa15 (diff) | |
download | buildroot-be24e9e7aa684569ccfd0435678477db37a33d99.tar.gz buildroot-be24e9e7aa684569ccfd0435678477db37a33d99.zip |
Separate target-building make targets from image-building make targets
Currently, it's not possible to have dependencies from an image-building
target to a rootfs-building target.
For example, the boot-wrapper-aarch64 package uses the kernel build as
an input file. It supplies a dependency on 'linux', but this will break
if we're using BR2_TARGET_ROOTFS_INITRAMFS - the wrapper will include
the first kernel build, not the rebuild (which contains the embedded
initramfs).
This means we'd need to express a dependency from the target build to
the image build. However, if we do something like:
-BOOT_WRAPPER_AARCH64_DEPENDENCIES = linux
+BOOT_WRAPPER_AARCH64_DEPENDENCIES = linux26-rebuild-with-initramfs
- then we get a circular dependency, because boot-wrapper-aarch64 is in
the TARGETS list, which linux26-rebuild-with-initramfs depends on.
This change splits the possible targets into two separate lists,
TARGET_TARGETS (dependencies for building the target dir) and
IMAGE_TARGETS (dependencies for building images). We keep TARGETS as a
list of everything, and use TARGET_TARGETS for the rootfs-finalize
target.
Signed-off-by: Jeremy Kerr <jk@ozlabs.org>
Signed-off-by: Stewart Smith <stewart@linux.vnet.ibm.com>
[fix for PACKAGES variable rename 8a58e0238ef3]
Signed-off-by: Joel Stanley <joel@jms.id.au>
Diffstat (limited to 'package/python-oauthlib/python-oauthlib.mk')
0 files changed, 0 insertions, 0 deletions