core/pkg-generic: allow packages to declare target-finalize hooks
Currently, packages using target finalize hooks must remember that they need to register their hook in TARGET_FINALIZE_HOOKS conditionally (otherwise their hook will be triggered even if the package is disabled). In order to avoid this potential mistake, this commit introduces a per-package target-finalize hook variable, in which packages can register their target-finalize hooks, with the guarantee that they will only be triggered if the package is enabled. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Reviewed-by: Romain Naour <romain.naour@gmail.com> [Thomas: rework commit log.] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
This commit is contained in:
parent
af9bb14f3c
commit
624dbec7e1
@ -77,3 +77,10 @@ others, use the following variables:
|
||||
|
||||
* +$(SRCDIR)+: the path to the overridden source directory
|
||||
* +$(@D)+: the path to the build directory
|
||||
|
||||
==== Target-finalize hook
|
||||
|
||||
Packages may also register hooks in +LIBFOO_TARGET_FINALIZE_HOOKS+.
|
||||
These hooks are run after all packages are built, but before the
|
||||
filesystem images are generated. They are seldom used, and your
|
||||
package probably do not need them.
|
||||
|
@ -572,6 +572,7 @@ $(2)_PRE_INSTALL_IMAGES_HOOKS ?=
|
||||
$(2)_POST_INSTALL_IMAGES_HOOKS ?=
|
||||
$(2)_PRE_LEGAL_INFO_HOOKS ?=
|
||||
$(2)_POST_LEGAL_INFO_HOOKS ?=
|
||||
$(2)_TARGET_FINALIZE_HOOKS ?=
|
||||
|
||||
# human-friendly targets and target sequencing
|
||||
$(1): $(1)-install
|
||||
@ -882,6 +883,7 @@ endif
|
||||
ifneq ($$($(2)_USERS),)
|
||||
PACKAGES_USERS += $$($(2)_USERS)$$(sep)
|
||||
endif
|
||||
TARGET_FINALIZE_HOOKS += $$($(2)_TARGET_FINALIZE_HOOKS)
|
||||
|
||||
ifeq ($$($(2)_SITE_METHOD),svn)
|
||||
DL_TOOLS_DEPENDENCIES += svn
|
||||
|
Loading…
Reference in New Issue
Block a user