[Buildroot] [PATCH] docs/manual: clarify hooks and dependencies build order

Baruch Siach baruch at tkos.co.il
Thu Feb 27 13:30:01 UTC 2020

As explained in commit bdc9364ffae ("package/fail2ban: The
(host-python3) 2to3 utility needs to be present"), hooks before
_PRE_CONFIGURE_HOOKS can't rely on package dependencies build artefacts.
Mention this point in hooks documentation.

Cc: Thomas De Schampheleire <thomas.de_schampheleire at nokia.com>
Signed-off-by: Baruch Siach <baruch at tkos.co.il>
 docs/manual/adding-packages-hooks.txt | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/docs/manual/adding-packages-hooks.txt b/docs/manual/adding-packages-hooks.txt
index 0ce79f8907f8..c80f5cb52d32 100644
--- a/docs/manual/adding-packages-hooks.txt
+++ b/docs/manual/adding-packages-hooks.txt
@@ -59,6 +59,14 @@ endef
+==== Hooks run order
+Hooks up to, and including, +LIBFOO_POST_PATCH_HOOKS+ might run before
++LIBFOO_DEPENDENCIES+ finish building. You can not rely on build artefacts of
+dependency packages in these early hooks. +LIBFOO_PRE_CONFIGURE_HOOKS+ and
+later hooks will run only when +LIBFOO_DEPENDENCIES+ have been built. As a
+result, you can use dependencies build artefacts in these later hooks.
 ==== Using the +POST_RSYNC+ hook
 The +POST_RSYNC+ hook is run only for packages that use a local source,

More information about the buildroot mailing list