Re: [ptxdist] Advice on Directory Structure

[Josef Holzmayr <holzmayr@rsi-elektrotechnik.de>]

Howdy!

Am 21.02.2012 17:08, schrieb Jerry Kirk:
> Josef Holzmayr<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.

Yes, I install them there. The toolchains are behaving well and sticking 
to their own directories, so no problems. I personally see nothing bad 
in using /opt for that. (think data deduplication when you have multiple 
developers on the machine)

> 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?

Yes, for me a project is the complete BSP including all sources, 
patches, applications etc. i need to build the final image.

> 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?

I haven't had the need to seperate the applications out of the project, 
because my apps(*sic*) are usually highly project specific. Hence, I 
view the project altogether as the thing i keep in SCM.

> 4. In general, how much do you try to seperate your code from the starting BSP?

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 :)

Greetz
_____________________________________________________________
Josef Holzmayr
Dipl-Ing. (FH)
Entwicklung Embedded Devices / Software

Tel.: +49 8444 9204-48>
Fax:  +49 8444 9204-50
holzmayr@rsi-elektrotechnik.de

R-S-I Elektrotechnik GmbH & Co. KG
Woelkestrasse 11
D-85301 Schweitenkirchen
www.rsi-elektrotechnik.de
_____________________________________________________________
Amtsgericht Ingolstadt - GmbH: HRB 191328 - KG: HRA 170363
Geschäftsführer: Dr.-Ing. Michael Sorg, Dipl.-Ing. Franz Sorg
USt-IdNr.: DE 128592548


-- 
ptxdist mailing list
ptxdist@pengutronix.de