mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Juergen Borleis <jbe@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Loss of speedup for subsequent different -but still similar- images build
Date: Fri, 24 Sep 2021 13:33:28 +0200	[thread overview]
Message-ID: <8ef71c12c1a0900b32792ffa9c0007fd7ea8588f.camel@pengutronix.de> (raw)
In-Reply-To: <DM6PR17MB3387966C096FE47960185725B5A39@DM6PR17MB3387.namprd17.prod.outlook.com>

Hi Kevin,

Am Donnerstag, dem 23.09.2021 um 13:02 +0000 schrieb Henzer, Kevin:
> […]
> ./ptxdist go --ptxconfig=configs/config_1 --platformconfig=configs/platformconfig       # takes time only the first time, else quite fast
> ./ptxdist images --ptxconfig=configs/ config_1  --platformconfig=configs/platformconfig  # quite fast
> 
> ./ptxdist go --ptxconfig=configs/config_2 --platformconfig=configs/platformconfig       # quite fast
> ./ptxdist images --ptxconfig=configs/ config_2  --platformconfig=configs/platformconfig  # quite fast

What is the difference between 'configs/config_1' and 'configs/config_2'? Maybe
they differ in the setting of some kind of base package and then always all
dependencies must be rebuilt.

jb

-- 
Pengutronix e.K.                       | Juergen Borleis             |
Steuerwalder Str. 21                   | https://www.pengutronix.de/ |
31137 Hildesheim, Germany              | Phone: +49-5121-206917-128 |
Amtsgericht Hildesheim, HRA 2686       | Fax:   +49-5121-206917-9 |


_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de

  parent reply	other threads:[~2021-09-24 11:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-23 13:02 Henzer, Kevin
2021-09-24 10:23 ` Ian Abbott
2021-09-24 11:33 ` Juergen Borleis [this message]
2021-09-29 12:44 ` 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=8ef71c12c1a0900b32792ffa9c0007fd7ea8588f.camel@pengutronix.de \
    --to=jbe@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