public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: isar-users <isar-users@googlegroups.com>
Cc: Claudius Heine <ch@denx.de>
Subject: Re: [PATCH] Set STAMPCLEAN variable
Date: Mon, 12 Aug 2019 19:03:32 +0200	[thread overview]
Message-ID: <277559e2-a461-2fcd-452b-562639ce84fe@siemens.com> (raw)
In-Reply-To: <37986885-5647-f58c-c732-0bc076485594@siemens.com>

On 12.08.19 18:44, [ext] Jan Kiszka wrote:
> From: Jan Kiszka <jan.kiszka@siemens.com>
> 
> This ensures that stamp files are cleaned when a task is rebuilt. Not
> providing this pattern likely caused a lot of failures when doing
> partial rebuilds.
> 
> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
> ---
> 
> This does not solve rebuilding isar-bootstrap* after config changes,
> though. But that's a topic for a separate thread - I don't understand
> its logic yet.
> 
>   meta/conf/bitbake.conf | 1 +
>   1 file changed, 1 insertion(+)
> 
> diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
> index 3d18223..d1e039f 100644
> --- a/meta/conf/bitbake.conf
> +++ b/meta/conf/bitbake.conf
> @@ -36,6 +36,7 @@ S = "${WORKDIR}/${P}"
>   AUTOREV = "${@bb.fetch2.get_autorev(d)}"
>   SRC_URI = "file://${FILE}"
>   STAMP = "${TMPDIR}/stamps/${PF}"
> +STAMPCLEAN = "${STAMP}.*"
>   SVNDIR = "${DL_DIR}/svn"
>   T = "${WORKDIR}/temp"
>   TMPDIR = "${TOPDIR}/tmp"
> 

Damn, some last-minute editing seems to have broken this again. Plus I noticed 
that do_clean() could/should use this as well. v2 will come.

Jan

-- 
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux

      reply	other threads:[~2019-08-12 17:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-12 16:44 Jan Kiszka
2019-08-12 17:03 ` Jan Kiszka [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=277559e2-a461-2fcd-452b-562639ce84fe@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=ch@denx.de \
    --cc=isar-users@googlegroups.com \
    /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