core/pkg-generic: check proper package installation
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> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
This commit is contained in:
parent
b63951da35
commit
938f47c7e8
@ -95,6 +95,21 @@ define check_host_rpath
|
||||
endef
|
||||
GLOBAL_INSTRUMENTATION_HOOKS += check_host_rpath
|
||||
|
||||
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
|
||||
|
Loading…
Reference in New Issue
Block a user