From: Roland Hieber <rhi@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Roland Hieber <rhi@pengutronix.de>
Subject: [ptxdist] [PATCH 3/3] doc: ref: document config hash macros and variables
Date: Tue, 6 Dec 2022 12:12:11 +0100 [thread overview]
Message-ID: <20221206111211.3961424-3-rhi@pengutronix.de> (raw)
In-Reply-To: <20221206111211.3961424-1-rhi@pengutronix.de>
Signed-off-by: Roland Hieber <rhi@pengutronix.de>
---
doc/ref_make_macros.rst | 18 ++++++++++++++++++
doc/ref_make_variables.rst | 9 +++++++++
2 files changed, 27 insertions(+)
diff --git a/doc/ref_make_macros.rst b/doc/ref_make_macros.rst
index 4c1ca2f0375f..3ea331baee4b 100644
--- a/doc/ref_make_macros.rst
+++ b/doc/ref_make_macros.rst
@@ -681,6 +681,24 @@ be installed with some other ``install_*`` command before
@$(call install_replace, timezone, /etc/timezone, @TIMEZONE@, \
$(PTXCONF_TIMEZONE_LOCALTIME))
+.. _ptx/cfghash:
+.. _ptx/cfghash-file:
+
+ptx/cfghash, ptx/cfghash-file
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Usage:
+
+.. code-block:: make
+
+ $(call ptx/cfghash, <PKG>, <string>)
+ $(call ptx/cfghash-file, <PKG>, <file>)
+
+Add an arbitrary **<string>** or the content of **<file>** to the config hash
+for **<PKG>**.
+This has the effect that the package will be rebuilt when the string or the
+content of the file changes.
+
.. _param_macros:
.. _ptxEndis:
.. _ptxDisen:
diff --git a/doc/ref_make_variables.rst b/doc/ref_make_variables.rst
index beca984edccc..7ec09cbb3e91 100644
--- a/doc/ref_make_variables.rst
+++ b/doc/ref_make_variables.rst
@@ -345,6 +345,15 @@ Build Environment for all Stages
Prepare Stage
^^^^^^^^^^^^^
+``<PKG>_CFGHASH``
+ This variable contains the config hash for the package.
+ If it changes, PTXdist rebuilds the prepare stage of the package (and
+ successively, all following stages).
+
+ You should not need to touch this variable directly.
+ To add content to the config hash, you can use the macros :ref:`ptx/cfghash
+ and ptx/cfghash-file <ptx/cfghash>`.
+
``<PKG>_CONF_ENV``
The environment for the prepare stage. If undefined, PTXdist will use
``$(CROSS_ENV)`` for target packages, ``$(HOST_ENV)`` for host packages
--
2.30.2
next prev parent reply other threads:[~2022-12-06 11:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-06 11:12 [ptxdist] [PATCH 1/3] doc: ref_make_macros: fix jump target Roland Hieber
2022-12-06 11:12 ` [ptxdist] [PATCH 2/3] doc: ref_make_macros: add missing synopses Roland Hieber
2022-12-15 7:34 ` [ptxdist] [APPLIED] " Michael Olbrich
2022-12-06 11:12 ` Roland Hieber [this message]
2022-12-15 7:35 ` [ptxdist] [APPLIED] doc: ref: document config hash macros and variables Michael Olbrich
2022-12-15 7:34 ` [ptxdist] [APPLIED] doc: ref_make_macros: fix jump target Michael Olbrich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20221206111211.3961424-3-rhi@pengutronix.de \
--to=rhi@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox