mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Mitigate build stamp disadvantages for local_src packages
Date: Wed, 3 Jul 2019 10:04:20 +0200	[thread overview]
Message-ID: <20190703080420.gkeerqnu5xtw2plk@pengutronix.de> (raw)
In-Reply-To: <2551525.rF1KUiLOMo@dabox>

Hi,

On Wed, Jul 03, 2019 at 08:58:54AM +0200, Tim Sander wrote:
> I have noticed that in yocto which is also basically build stamp based that 
> local cmake projects get build when they are not updated. So i am wondering if 
> something like this would be also possible with ptxdist?
> 
> This is one of the most observed errors after a git pull...

'...get build when they are not updated.'? This makes no sense to me. Is
the 'not' correct here? If not then I assume you want to automatically
rebuild local_src packages when the code changes.

There is no integrated solution for this, but it's all make dependencies,
so you can implement something yourself.
If the local_src package has a separate git repository, then you could add
a dependency like this:

$(STATEDIR)/<pkg>.<commitish>.githash:
	rm $(STATEDIR)/<pkg>.*.githash
	touch $@

$(STATEDIR)/<pkg>.prepare: $(STATEDIR)/<pkg>.<commitish>.githash

and generate the commitish with
$(call ptx/force-sh,git -C <dir> rev-parse HEAD)
or something like that.

I'm open to ideas on howto integrate this better. Maybe track
$(<PKG>_VERSION) changes. The you could add the appropriate shell code
there to generate some version string.
Hmm, maybe some helper macro to generate a useful version.

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

      reply	other threads:[~2019-07-03  8:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-03  6:58 Tim Sander
2019-07-03  8:04 ` Michael Olbrich [this message]

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=20190703080420.gkeerqnu5xtw2plk@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