diff options
author | Stewart Smith <stewart@linux.vnet.ibm.com> | 2015-08-27 13:02:09 +1000 |
---|---|---|
committer | Joel Stanley <joel@jms.id.au> | 2018-03-05 17:23:18 +1030 |
commit | 70035c23a2e2a76c7285365517a23da057c992f6 (patch) | |
tree | f2bdc8250ba020c59c7347dbbef5ddab4ae88c56 /package/php/0009-ext-xml-expat_compat.h-add-missing-php.h-include.patch | |
parent | 8a94ff12d232ada68cff5957089a78a1f0b8f192 (diff) | |
download | buildroot-70035c23a2e2a76c7285365517a23da057c992f6.tar.gz buildroot-70035c23a2e2a76c7285365517a23da057c992f6.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>
Signed-off-by: Joel Stanley <joel@jms.id.au>
Diffstat (limited to 'package/php/0009-ext-xml-expat_compat.h-add-missing-php.h-include.patch')
0 files changed, 0 insertions, 0 deletions