From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mediacenter.hi.pengutronix.de ([2001:6f8:1178:2::65]) by metis.ext.pengutronix.de with esmtp (Exim 4.72) (envelope-from ) id 1RMeL7-0002gd-AT for ptxdist@pengutronix.de; Sat, 05 Nov 2011 12:23:09 +0100 Received: from mol by mediacenter.hi.pengutronix.de with local (Exim 4.72) (envelope-from ) id 1RMeL7-0001nv-9E for ptxdist@pengutronix.de; Sat, 05 Nov 2011 12:23:09 +0100 Date: Sat, 5 Nov 2011 12:23:09 +0100 From: Michael Olbrich Message-ID: <20111105112309.GH20768@pengutronix.de> References: <4EB44121.2010107@erwinrol.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <4EB44121.2010107@erwinrol.com> 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-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: ptxdist-bounces@pengutronix.de Errors-To: ptxdist-bounces@pengutronix.de To: ptxdist@pengutronix.de 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. 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