mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Erwin Rol <mailinglists@erwinrol.com>
To: bart.devos@eia.be
Cc: ptxdist@pengutronix.de
Subject: Re: [ptxdist] General Ptxdist usecase question
Date: Fri, 28 Oct 2011 10:46:44 +0200	[thread overview]
Message-ID: <4EAA6BF4.5020107@erwinrol.com> (raw)
In-Reply-To: <4EAA69E8.1080504@eia.be>

Hallo Bart,

On 28-10-2011 10:38, Bart De Vos wrote:
> Hello,
>
> We have some kind of similar setup in which we split our root file
> system and the customers filesystem. In runtime the customers filesystem
> is mounted on a fixed point (/opt). Off-course we have designed this
> separation from the start, we have 2 separated filesystems. For the
> second filesystem you can use just another ptxdist configfile. I don't
> know whether you can merge 2 file system images together with ptxdist.
> But for this purpose a simple script can automate this.

That would be an option too. I could easily deal with 2 filesystems. But 
how do you build the second (user) project? It seems you need to 
duplicate almost all settings in the second config file. And that is 
very error prone in my eyes.

> Another approach can be to support a list of configfiles in stead of
> only one. This will give you a single image file which was what you 'v
> been asking for in the first place.

Shouldn't it already be possible to do something like this;

OS project create ptxdistconfig and platformconfig

Than in the user project include the OS ptxdistconfig and platformconfig.

But how to tell the user project not to rebuild everything again. That's 
my main problem.

- Erwin


> Are there any plans to support a list of configfiles?
>
> Kind regards,
> Bart.
>
> On 10/28/2011 10:21 AM, Erwin Rol wrote:
>> Hey all,
>>
>> 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.
>> 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 ?
>>
>> TIA,
>>
>> Erwin
>>
>>
>>
>>
>>
>


-- 
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2011-10-28  8:46 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 [this message]
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
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=4EAA6BF4.5020107@erwinrol.com \
    --to=mailinglists@erwinrol.com \
    --cc=bart.devos@eia.be \
    --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