From: Erwin Rol <mailinglists@erwinrol.com>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] lndir'ing sysroot-target
Date: Sun, 06 Nov 2011 01:37:29 +0100 [thread overview]
Message-ID: <4EB5D6C9.7040605@erwinrol.com> (raw)
In-Reply-To: <20111105112309.GH20768@pengutronix.de>
On 5-11-2011 12:23, Michael Olbrich wrote:
> Hi,
>
> On Fri, Nov 04, 2011 at 08:46:41PM +0100, Erwin Rol wrote:
>> in my search to find a way to split ptxdist into an OS build and
>> application build process I tried the following.
>>
>> 1) create and build an ptxdist project with everything the OS needs
>> like glib, gtk, dbus, cairo, etc.
>> 2) create an ptxdist project with applications. And don't have any
>> "select"s to OS parts like gtk or cairo in the .in files of the
>> applications.
>> 3) lndir sysroot-target from the OS build into the sysroot-target of
>> the application build.
>> 4) build the application images.
>>
>>
>> That way I was able to build my applications apart from the OS, but
>> still use ptxdist to build.
>>
>> Would this be a feature that others are interested in ?
>>
>> And any ideas or warnings on what could go wrong ?
>
> Something like that already exists. With "build type" == "production" you
> can put the build in some global location. Then with "use pre-built
> production release" reuse it and add packages without dependencies on the
> core system like you suggested.
> Both sources are then used to create the images. I think it's even possible
> to combine that with collections.
> "built on top of another platform" is a variation of this where you use a
> different local platform in the same BSP build, e.g. a generic ARMv5 core
> platform + several variants with extra local packages.
>
> This works well enough if the base platform is stable. However, because of
> the missing dependencies you should rebuilt everything when it changes.
>
Is that really the same. When I understand you correctly the Production
build only builds part of the system and the "use pre-built" creates the
final images out of the two parts.
That is not the same as generating an OS image that runs and works fine.
And than use a second ptxdist project to create applications that you
can be installed on that OS.
Or did I misunderstand something?
- Erwin
PS: is there any documentation on how those mentioned feature should
work, cause the "Help" in ptxdist isn't really helpful.
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2011-11-06 0:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-04 19:46 Erwin Rol
2011-11-05 10:04 ` Robert Schwebel
2011-11-05 11:23 ` Michael Olbrich
2011-11-06 0:37 ` Erwin Rol [this message]
2011-11-06 10:33 ` Michael Olbrich
2011-11-06 13:16 ` Erwin Rol
2011-11-06 14:40 ` Michael Olbrich
2011-11-06 19:10 ` Jon Ringle
2011-11-07 10:15 ` Erwin Rol
2011-11-07 10:49 ` Michael Olbrich
2011-11-07 13:48 ` Jon Ringle
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=4EB5D6C9.7040605@erwinrol.com \
--to=mailinglists@erwinrol.com \
--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