mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] General Ptxdist usecase question
Date: Fri, 28 Oct 2011 11:29:26 +0200	[thread overview]
Message-ID: <20111028092926.GB12223@pengutronix.de> (raw)
In-Reply-To: <4EAA6602.9040105@erwinrol.com>

On Fri, Oct 28, 2011 at 10:21:22AM +0200, Erwin Rol wrote:
> The projects I use Ptxdist for have grown in size over the last few
> years, they now include mono, gtkwebkit, boost, clutter, gtk3 and
> all the Xorg stuff. That means it now takes more than 2 hours to
> compile it from scratch. The machine is not the fastest (only 4 core
> 3GHz) but even if it was twice as fast it would still compile over
> and hour.
> 
> So I am looking for a way to prevent a full rebuild on every project
> release. There seem to be some features in Ptxdist that should allow
> this, but I could not really figure out how to use them.
> 
> What I would like to do is this;
> 
> 1) Build an OS with all the Xorg, mono, gtk, etc. stuff and version that.

This is stable, right? Fix PTXdist version, no option changes etc.?

> 2) build my own applications.
> 3) combine the results from step 1 and 2 into an image for flashing
> 4) goto 2
> 
> Is it possible to do this with Ptxdist and if so, how ?

Take a look at the PROJECT_CREATE_DEVPKGS/PROJECT_USE_DEVPKGS options. With
PROJECT_CREATE_DEVPKGS you get <pkg>->version>-<hash>-dev.tar.gz for most
packages. This is the content of <PKG>_PKGDIR.
With PROJECT_USE_DEVPKGS you can specify a folder contain such archives. If
a matching archive is found, the stages up to install are skipped and the
archive is extracted instead. The hash makes sure the sub-options used to
create the archive are the correct ones.
Note: You cannot use your own packages dir. That introduces really strange
circular dependencies.

Michael

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

-- 
ptxdist mailing list
ptxdist@pengutronix.de

  parent reply	other threads:[~2011-10-28  9:29 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-28  8:21 Erwin Rol
2011-10-28  8:38 ` Bart De Vos
2011-10-28  8:46   ` Erwin Rol
2011-10-28  9:26     ` Bart De Vos
2011-10-28  9:33   ` Michael Olbrich
2011-10-28  9:37     ` Bart De Vos
2011-10-28  9:45       ` Michael Olbrich
2011-10-28  9:48         ` Bart De Vos
2011-10-28  9:29 ` Michael Olbrich [this message]
2011-10-28 10:05   ` Erwin Rol
2011-10-28 10:32     ` Michael Olbrich
2011-11-02 19:03       ` Flavio de Castro Alves Filho

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=20111028092926.GB12223@pengutronix.de \
    --to=m.olbrich@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