From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from plane.gmane.org ([80.91.229.3]) by metis.ext.pengutronix.de with esmtp (Exim 4.72) (envelope-from ) id 1RzsGL-00060m-1A for ptxdist@pengutronix.de; Tue, 21 Feb 2012 17:08:23 +0100 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1RzsGK-0003sv-5N for ptxdist@pengutronix.de; Tue, 21 Feb 2012 17:08:20 +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 ; Tue, 21 Feb 2012 17:08:20 +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 ; Tue, 21 Feb 2012 17:08:20 +0100 From: Jerry Kirk Date: Tue, 21 Feb 2012 16:08:03 +0000 (UTC) Message-ID: References: <4F435CA5.6050909@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 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 Josef Holzmayr writes: > > Any advice would be great to try and avoid painful restructures. > > ~/ptxdist/releases Here I keep the built ptxdist releases > /toolchains The OSELAS.Toolchain things are here > /sources I download all sources to here > (ptxdist setup -> source directories) > /projects/a Every project the gets a symlink to the > /b ptxdist binary it uses, and done. > /c These directories should go into your SCM. > > For the layout of any project directory, you can check out the mini2440 > BSP > (http://www.pengutronix.de/oselas/bsp/pengutronix/mini2440_bsp_en.html), > as it includes a working structure fitting for ptxdist including > examples for the difference board/project/etc. Josef, thanks for your advice just a few followup questions (fgr anyone) 1. Do you still install the cross compilers in /OPT or do you try to include them local to the project? I'm assuming you might wind up with multiple toolchains. 2. In your example of projects/[abc] are you starting from a known BSP and then customizing the config files, adding patches, etc. Is a Project really a build image for the embedded device or just an application? 3. Do you keep the application code seperate in structure (and in code control repository) and just sym-link the directory to the "local_src" direcetory? 4. In general, how much do you try to seperate your code from the starting BSP? -- ptxdist mailing list ptxdist@pengutronix.de