From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from hbe.hbelightingsystems.com ([213.239.196.253]) by metis.ext.pengutronix.de with esmtp (Exim 4.72) (envelope-from ) id 1RMqjr-0002C1-Ot for ptxdist@pengutronix.de; Sun, 06 Nov 2011 01:37:51 +0100 Received: from localhost (localhost [127.0.0.1]) by hbe.hbelightingsystems.com (Postfix) with ESMTP id 3E2601E8002 for ; Sun, 6 Nov 2011 01:37:30 +0100 (CET) Received: from hbe.hbelightingsystems.com ([127.0.0.1]) by localhost (hbe.hbelightingsystems.com [127.0.0.1]) (amavisd-new, port 10024) with SMTP id 5xLObslN79Zg for ; Sun, 6 Nov 2011 01:37:29 +0100 (CET) Received: from [192.168.1.4] (ip51ce2bef.speed.planet.nl [81.206.43.239]) (Authenticated sender: erwin@hbelightingsystems.com) by hbe.hbelightingsystems.com (Postfix) with ESMTP id 495ED1E8001 for ; Sun, 6 Nov 2011 01:37:29 +0100 (CET) Message-ID: <4EB5D6C9.7040605@erwinrol.com> Date: Sun, 06 Nov 2011 01:37:29 +0100 From: Erwin Rol MIME-Version: 1.0 References: <4EB44121.2010107@erwinrol.com> <20111105112309.GH20768@pengutronix.de> In-Reply-To: <20111105112309.GH20768@pengutronix.de> Subject: Re: [ptxdist] lndir'ing sysroot-target Reply-To: ptxdist@pengutronix.de List-Id: PTXdist Development Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: ptxdist-bounces@pengutronix.de Errors-To: ptxdist-bounces@pengutronix.de To: ptxdist@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