DistroKit Mailinglist
 help / color / mirror / Atom feed
* [DistroKit] [PATCH] ptxconfig: build and use development packages
@ 2018-12-12  0:33 Roland Hieber
  2018-12-12 17:40 ` Robert Schwebel
  0 siblings, 1 reply; 4+ messages in thread
From: Roland Hieber @ 2018-12-12  0:33 UTC (permalink / raw)
  To: distrokit; +Cc: Roland Hieber

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

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [DistroKit] [PATCH] ptxconfig: build and use development packages
  2018-12-12  0:33 [DistroKit] [PATCH] ptxconfig: build and use development packages Roland Hieber
@ 2018-12-12 17:40 ` Robert Schwebel
  2018-12-17  9:03   ` Robert Schwebel
  0 siblings, 1 reply; 4+ messages in thread
From: Robert Schwebel @ 2018-12-12 17:40 UTC (permalink / raw)
  To: Roland Hieber; +Cc: distrokit, Roland Hieber

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...

rsc
-- 
Pengutronix e.K.                           | Dipl.-Ing. Robert Schwebel  |
Industrial Linux Solutions                 | https://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
DistroKit mailing list
DistroKit@pengutronix.de

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [DistroKit] [PATCH] ptxconfig: build and use development packages
  2018-12-12 17:40 ` Robert Schwebel
@ 2018-12-17  9:03   ` Robert Schwebel
  2018-12-17 10:03     ` Roland Hieber
  0 siblings, 1 reply; 4+ messages in thread
From: Robert Schwebel @ 2018-12-17  9:03 UTC (permalink / raw)
  To: Roland Hieber; +Cc: distrokit, Roland Hieber

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/'    <-------------

See for example here:
http://jenkins.hi.pengutronix.de/job/ptxdist-bsps/job/DistroKit/job/next--v7a/2/consoleFull

I'm dropping the patch for now.

rsc
-- 
Pengutronix e.K.                           | Dipl.-Ing. Robert Schwebel  |
Industrial Linux Solutions                 | https://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
DistroKit mailing list
DistroKit@pengutronix.de

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [DistroKit] [PATCH] ptxconfig: build and use development packages
  2018-12-17  9:03   ` Robert Schwebel
@ 2018-12-17 10:03     ` Roland Hieber
  0 siblings, 0 replies; 4+ messages in thread
From: Roland Hieber @ 2018-12-17 10:03 UTC (permalink / raw)
  To: Robert Schwebel; +Cc: distrokit

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

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2018-12-17 10:03 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-12-12  0:33 [DistroKit] [PATCH] ptxconfig: build and use development packages Roland Hieber
2018-12-12 17:40 ` Robert Schwebel
2018-12-17  9:03   ` Robert Schwebel
2018-12-17 10:03     ` Roland Hieber

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox