From mboxrd@z Thu Jan  1 00:00:00 1970
Return-path: <ptxdist-bounces@pengutronix.de>
Received: from plane.gmane.org ([80.91.229.3])
	by metis.ext.pengutronix.de with esmtp (Exim 4.72)
	(envelope-from <gcepd-ptxdist@m.gmane.org>) id 1RztzT-0002DQ-Nm
	for ptxdist@pengutronix.de; Tue, 21 Feb 2012 18:59:08 +0100
Received: from list by plane.gmane.org with local (Exim 4.69)
	(envelope-from <gcepd-ptxdist@m.gmane.org>) id 1RztzT-0006Nl-4p
	for ptxdist@pengutronix.de; Tue, 21 Feb 2012 18:59:03 +0100
Received: from h96-60-251-119.cncrtn.dsl.dynamic.tds.net ([96.60.251.119])
	by main.gmane.org with esmtp (Gmexim 0.1 (Debian))
	id 1AlnuQ-0007hv-00
	for <ptxdist@pengutronix.de>; Tue, 21 Feb 2012 18:59:03 +0100
Received: from jkirk865 by h96-60-251-119.cncrtn.dsl.dynamic.tds.net with
	local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00
	for <ptxdist@pengutronix.de>; Tue, 21 Feb 2012 18:59:03 +0100
From: Jerry Kirk <jkirk865@gmail.com>
Date: Tue, 21 Feb 2012 17:58:53 +0000 (UTC)
Message-ID: <loom.20120221T185228-60@post.gmane.org>
References: <loom.20120220T231704-130@post.gmane.org>
	<4F435CA5.6050909@rsi-elektrotechnik.de>
	<loom.20120221T170128-547@post.gmane.org>
	<4F43C804.2080404@rsi-elektrotechnik.de>
Mime-Version: 1.0
Subject: Re: [ptxdist] Advice on Directory Structure
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-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

Josef Holzmayr <holzmayr@...> writes:

<! SNIP !> read the thread for context...

> See 3) for one.. at least for me, the BSP I start off evolves into the 
> thing I want to have, including the code.
> 
> FWIW, this is the easiest way to view a ptxdist project: its basically 
> an application including everything you need to run it. It can in turn 
> contain several platforms to build for different targets, and the same 
> holds true for software configurations.
> 
> Might of course be I use it all in a way not intended, but it works well 
> for me :)

Thanks again Josef that really clears some tings up for me. One last (for now) 
question. I am planning on one piece of hardware that supports two products. 
Each p[roduct will share all the low level Linux stuff but will have two 
different top-level applications. 

Is that type of organization best served by two PTXDist software config files 
and only one platform file?  It seems that splitting them into 
separate "~/projects/[ab]" would cause a lot of code/patch/config duplication.


-- 
ptxdist mailing list
ptxdist@pengutronix.de