DistroKit Mailinglist
 help / color / mirror / Atom feed
From: Roland Hieber <r.hieber@pengutronix.de>
To: distrokit@pengutronix.de
Cc: Roland Hieber <rohieb@rohieb.name>
Subject: [DistroKit] [PATCH] ptxconfig: build and use development packages
Date: Wed, 12 Dec 2018 01:33:39 +0100	[thread overview]
Message-ID: <20181212003339.pweqefvf7kbocv3a@pengutronix.de> (raw)

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(-)

diff --git a/configs/ptxconfig b/configs/ptxconfig
index f485c01..4efeeeb 100644
--- a/configs/ptxconfig
+++ b/configs/ptxconfig
@@ -30,8 +30,10 @@ PTXCONF_PROJECT_VERSION="-${PTXDIST_BSP_AUTOVERSION}"
 #
 # ------------------------------------
 #
-# PTXCONF_PROJECT_CREATE_DEVPKGS is not set
-# PTXCONF_PROJECT_USE_DEVPKGS is not set
+PTXCONF_PROJECT_CREATE_DEVPKGS=y
+PTXCONF_PROJECT_USE_DEVPKGS=y
+PTXCONF_PROJECT_DEVPKGDIR="${PTXDIST_WORKSPACE}/devpkgs/"
+PTXCONF_PROJECT_DEVMIRROR=""
 
 #
 # ------------------------------------
-- 
2.19.2



_______________________________________________
DistroKit mailing list
DistroKit@pengutronix.de

             reply	other threads:[~2018-12-12  0:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-12  0:33 Roland Hieber [this message]
2018-12-12 17:40 ` Robert Schwebel
2018-12-17  9:03   ` Robert Schwebel
2018-12-17 10:03     ` Roland Hieber

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=20181212003339.pweqefvf7kbocv3a@pengutronix.de \
    --to=r.hieber@pengutronix.de \
    --cc=distrokit@pengutronix.de \
    --cc=rohieb@rohieb.name \
    /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