From mboxrd@z Thu Jan  1 00:00:00 1970
Return-path: <ptxdist-bounces@pengutronix.de>
Received: from hbe.hbelightingsystems.com ([213.239.196.253])
	by metis.ext.pengutronix.de with esmtp (Exim 4.72)
	(envelope-from <mailinglists@erwinrol.com>) id 1RMPiR-00032l-DY
	for ptxdist@pengutronix.de; Fri, 04 Nov 2011 20:46:16 +0100
Received: from localhost (localhost [127.0.0.1])
	by hbe.hbelightingsystems.com (Postfix) with ESMTP id E79CB1E8002
	for <ptxdist@pengutronix.de>; Fri,  4 Nov 2011 20:46:14 +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 NByDBZ3ZxqvO for <ptxdist@pengutronix.de>;
	Fri,  4 Nov 2011 20:46:14 +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 2EB961E8001
	for <ptxdist@pengutronix.de>; Fri,  4 Nov 2011 20:46:14 +0100 (CET)
Message-ID: <4EB44121.2010107@erwinrol.com>
Date: Fri, 04 Nov 2011 20:46:41 +0100
From: Erwin Rol <mailinglists@erwinrol.com>
MIME-Version: 1.0
Subject: [ptxdist] lndir'ing sysroot-target
Reply-To: ptxdist@pengutronix.de
List-Id: PTXdist Development Mailing List <ptxdist.pengutronix.de>
List-Unsubscribe: <http://metis.pengutronix.de/cgi-bin/mailman/options/ptxdist>, 
	<mailto:ptxdist-request@pengutronix.de?subject=unsubscribe>
List-Archive: <http://metis.pengutronix.de/pipermail/ptxdist>
List-Post: <mailto:ptxdist@pengutronix.de>
List-Help: <mailto:ptxdist-request@pengutronix.de?subject=help>
List-Subscribe: <http://metis.pengutronix.de/cgi-bin/mailman/listinfo/ptxdist>, 
	<mailto:ptxdist-request@pengutronix.de?subject=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 <ptxdist@pengutronix.de>

Hallo all,

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 ?

- Erwin

-- 
ptxdist mailing list
ptxdist@pengutronix.de