buildroot/Makefile, branch 2019.02-op-build

Merge tag '2019.02.1' into 2019.02-op-build

2019-04-01T00:13:00+00:00

Signed-off-by: Joel Stanley

Update for 2019.02.1

2019-03-29T22:52:57+00:00

Signed-off-by: Peter Korsgaard

Makefile: release: really drop build/docs from release tarball

2019-03-29T22:20:32+00:00

Commit 15cb98769e4 (release: remove manual build files from release tarballs) tried to remove the temporary files from the manual build from the release tarball, but manual-clean only removes build/docs/manual and leaves build/docs in the tarball. Instead use 'make clean' to completely remove the build directory from the tarball. Signed-off-by: Peter Korsgaard (cherry picked from commit c24faa81e859a773c72a84dca1eadffd1ddeffcf) Signed-off-by: Peter Korsgaard

Separate target-building make targets from image-building make targets

2019-03-05T03:00:28+00:00

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 Signed-off-by: Stewart Smith [fix for PACKAGES variable rename 8a58e0238ef3] Signed-off-by: Joel Stanley

Update for 2019.02

2019-03-04T21:49:56+00:00

Signed-off-by: Peter Korsgaard

Update for 2019.02-rc3

2019-03-01T11:57:30+00:00

Signed-off-by: Peter Korsgaard

Update for 2019.02-rc2

2019-02-23T14:06:12+00:00

Signed-off-by: Peter Korsgaard

Update for 2019.02-rc1

2019-02-13T08:03:54+00:00

Signed-off-by: Peter Korsgaard

Makefile: allow rootfs overlays to override symbolic links

2019-02-06T16:11:02+00:00

Since commit 0db34529f48 we use rsync with the --keep-dirlinks option to prevent overlays from accidentally overwriding /{usr,bin,sbin,lib} links when BR2_ROOTFS_MERGED_USR option is enabled. Unfortunately this also prevents replacing a symlink by a directory on purpose (e.g. /var/log, to persist system logs). Steps to reproduce: - enable BR2_ROOTFS_MERGED_USR and BR2_PACKAGE_SKELETON_INIT_SYSV - mkdir some_path/rootfs-overlay/var/log - enable BR2_ROOTFS_OVERLAY="some_path/rootfs-overlay" - run 'make' - 'target/var/log' is still a symlink to '../tmp', not a directory The --keep-dirlinks option can be dropped, since we run sanity checks on overlays. Now the rsync invocation is identical to the SYSTEM_RSYNC logic we have in system/system.mk, so use that variable. Signed-off-by: Carlos Santos Signed-off-by: Arnout Vandecappelle (Essensium/Mind)

Makefile: check rootfs overlays with BR2_ROOTFS_MERGED_USR enabled

2019-02-06T16:09:28+00:00

Add a step to target-finalize that checks each rootfs overlay, following the criteria established for custom skeletons and using the same script uesd by skeleton-custom.mk. Add a paragraph to the documentation clarifying that rootfs overlays don't need to contain /bin, /lib or /sbin and must not contain them when BR2_ROOTFS_MERGED_USR is enabled. Signed-off-by: Carlos Santos Signed-off-by: Arnout Vandecappelle (Essensium/Mind)