From: Roland Hieber <rhi@pengutronix.de>
To: Ariel Garcia <a.garcia@gemfony.eu>
Cc: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Docu for "fixup" rules
Date: Mon, 15 Jun 2020 10:57:40 +0200 [thread overview]
Message-ID: <20200615085740.b4esrkndguknndsd@pengutronix.de> (raw)
In-Reply-To: <3547520.gePCWmBn0L@atenea>
On Sat, Jun 13, 2020 at 01:01:39PM +0200, Ariel Garcia wrote:
> Hello,
>
> using the hint from this discussion
> https://www.mail-archive.com/ptxdist@pengutronix.de/msg16103.html
>
> i would like to add a "rules/post/kernel-fixup.make"
> kind of rule file to "extend" the rule run when i execute
> ptxdist clean kernel
>
> But i don't find any info regarding pre/post rule files in the official docu/
> reference manual.
>
> Any hint is really appreciated, thanks, Ariel
The makefiles in rules/pre are evaluated before any other in rules/, and
contain all macro and variable definitions that should be available for
rule files.
The files in rules/post are evaluated last, so you can e.g. override
makefiles and menu entries from upstream PTXdist in your BSP without
needing to forking the whole rule file.
All files are evaluated in lexical order, but other than that, the file
name is not important for functionality.
I don't think there's any more magic to it :)
- Roland
--
Roland Hieber, Pengutronix e.K. | r.hieber@pengutronix.de |
Steuerwalder Str. 21 | https://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de
next prev parent reply other threads:[~2020-06-15 8:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-13 11:01 Ariel Garcia
2020-06-15 8:57 ` Roland Hieber [this message]
2020-06-19 5:49 ` 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=20200615085740.b4esrkndguknndsd@pengutronix.de \
--to=rhi@pengutronix.de \
--cc=a.garcia@gemfony.eu \
--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