@@ -87,6 +87,21 @@ define step_pkg_size
endef
GLOBAL_INSTRUMENTATION_HOOKS += step_pkg_size
+define step_check_build_dir_one
+ if [ -d $(2) ]; then \
+ printf "%s: installs files in %s\n" $(1) $(2) >&2; \
+ exit 1; \
+ fi
+endef
+
+define step_check_build_dir
+ $(if $(filter install-staging,$(2)),\
+ $(if $(filter end,$(1)),$(call step_check_build_dir_one,$(3),$(STAGING_DIR)/$(O))))
+ $(if $(filter install-target,$(2)),\
+ $(if $(filter end,$(1)),$(call step_check_build_dir_one,$(3),$(TARGET_DIR)/$(O))))
+endef
+GLOBAL_INSTRUMENTATION_HOOKS += step_check_build_dir
+
# User-supplied script
ifneq ($(BR2_INSTRUMENTATION_SCRIPTS),)
define step_user
Some packages misbehave, and install files in either $(STAGING_DIR)/$(O) or in $(TARGET_DIR)/$(O) . One common reason for that is that pkgconf now prepends the sysroot path to all the paths it returns. Other reasons vary, but are mostly due to poorly writen generic-packages. And a new step hooks to check that no file gets installed in either location, called after the install-target and install-staging steps. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Cc: Romain Naour <romain.naour@openwide.fr> --- package/pkg-generic.mk | 15 +++++++++++++++ 1 file changed, 15 insertions(+)