DistroKit Mailinglist
 help / color / mirror / Atom feed
From: Roland Hieber <r.hieber@pengutronix.de>
To: Robert Schwebel <r.schwebel@pengutronix.de>
Cc: distrokit@pengutronix.de
Subject: Re: [DistroKit] [PATCH] ptxconfig: build and use development packages
Date: Mon, 17 Dec 2018 11:03:50 +0100	[thread overview]
Message-ID: <20181217100350.rpmyc4htddlpqmqm@pengutronix.de> (raw)
In-Reply-To: <20181217090325.ejxkc3mt6tysdq6b@pengutronix.de>

On Mon, Dec 17, 2018 at 10:03:25AM +0100, Robert Schwebel wrote:
> On Wed, Dec 12, 2018 at 06:40:14PM +0100, Robert Schwebel wrote:
> > On Wed, Dec 12, 2018 at 01:33:39AM +0100, Roland Hieber wrote:
> > > From: Roland Hieber <rohieb@rohieb.name>
> > > 
> > > When building all platforms, the host tools are also built multiple
> > > times. Since all platforms use the same versions and config hashes for
> > > the host tools, we can simply build one platform first, then copy
> > > platform-dir/packages/host-*dev.tar.gz into ./devpkgs/, and future
> > > builds will only need to extract the already built host-* packages from
> > > there instead of rebuilding everything again.
> > > 
> > > Signed-off-by: Roland Hieber <rohieb@rohieb.name>
> > > ---
> > > Although I don't know why this is in ptxconfig instead of ptxdist setup...
> > > ---
> > >  configs/ptxconfig | 6 ++++--
> > >  1 file changed, 4 insertions(+), 2 deletions(-)
> > 
> > Pushed to next...
> 
> It warns with
> 
> -----------------------------------
> target: host-genext2fs.install.post
> -----------------------------------
> 
> finished target host-genext2fs.install.post
> finished target world.targetinstall
> + ./p images
> ptxdist: warning: No dev packages found in 'next--v7a/devpkgs/'    <-------------

Meh okay. I guess you either have to ignore that warning when there are
none (ptxdist will happily build everything from scratch), or enabling
devpkgs is something you can simply not check into a git and have to
enable it manually before building a BSP, always remebering to stash and
unstash it when switching branches :-/

 - Roland


-- 
Roland Hieber                     | r.hieber@pengutronix.de     |
Pengutronix e.K.                  | https://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim | Phone: +49-5121-206917-5086 |
Amtsgericht Hildesheim, HRA 2686  | Fax:   +49-5121-206917-5555 |

_______________________________________________
DistroKit mailing list
DistroKit@pengutronix.de

      reply	other threads:[~2018-12-17 10:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-12  0:33 Roland Hieber
2018-12-12 17:40 ` Robert Schwebel
2018-12-17  9:03   ` Robert Schwebel
2018-12-17 10:03     ` Roland Hieber [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=20181217100350.rpmyc4htddlpqmqm@pengutronix.de \
    --to=r.hieber@pengutronix.de \
    --cc=distrokit@pengutronix.de \
    --cc=r.schwebel@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