@@ -722,8 +722,6 @@ staging-finalize:
.PHONY: target-finalize
target-finalize: $(PACKAGES) host-finalize
@$(call MESSAGE,"Finalizing target directory")
- # Check files that are touched by more than one package
- ./support/scripts/check-uniq-files -t target $(BUILD_DIR)/packages-file-list.txt
$(foreach hook,$(TARGET_FINALIZE_HOOKS),$($(hook))$(sep))
rm -rf $(TARGET_DIR)/usr/include $(TARGET_DIR)/usr/share/aclocal \
$(TARGET_DIR)/usr/lib/pkgconfig $(TARGET_DIR)/usr/share/pkgconfig \
@@ -786,6 +784,9 @@ endif
$(call MESSAGE,"Executing post-build script $(s)"); \
$(EXTRA_ENV) $(s) $(TARGET_DIR) $(call qstrip,$(BR2_ROOTFS_POST_SCRIPT_ARGS))$(sep))
+ # Check files that are touched by more than one package
+ ./support/scripts/check-uniq-files -t target $(BUILD_DIR)/packages-file-list.txt
+
touch $(TARGET_DIR)/usr
.PHONY: target-post-image
Packages that install info pages will update the info index when doing so. But we do not have that file in the target, so we do not care what content that file has, or whether it is modified by many packages. This is basically also valid for any file that we remove as part of our target-finalize cleanups: the files are not in target. Consequently, we will want to check for that condition to decide whether a file should, or should not, be reported as being touched by more than one package. For that, we'll need check-uniq-files to be run after all our cleanups. We even do it after the user-provided post-build scripts, in case they are explicitly doing some cleanups of their own in those scripts. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> --- Makefile | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-)