From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Building a package every time
Date: Wed, 4 Jan 2012 11:01:12 +0100 [thread overview]
Message-ID: <20120104100112.GG21393@pengutronix.de> (raw)
In-Reply-To: <CAKPCGKvvVaQmAw9FbmCW7mLYVCWAY+ZFJCb7yNhow+-WeCuRWA@mail.gmail.com>
Hi,
On Tue, Jan 03, 2012 at 01:09:10PM +0100, Bart Jonkers wrote:
> Is there a way to build a package every time "ptxdist go" is executed
> without dropping any of its stages?
> The package generates a file for the target root file system which
> contains build information (build time, host, ...) which should
> updated every time a build is triggered.
Remove the '@$(call touch)' from the first stage that should be rebuilt.
Michael
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2012-01-04 10:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-03 12:09 Bart Jonkers
2012-01-03 21:49 ` Tim Sander
2012-01-04 10:01 ` Michael Olbrich [this message]
2012-01-04 10:12 ` Bart Jonkers
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=20120104100112.GG21393@pengutronix.de \
--to=m.olbrich@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