From: Jerry Kirk <jkirk865@gmail.com>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Advice on Directory Structure
Date: Tue, 21 Feb 2012 16:08:03 +0000 (UTC) [thread overview]
Message-ID: <loom.20120221T170128-547@post.gmane.org> (raw)
In-Reply-To: <4F435CA5.6050909@rsi-elektrotechnik.de>
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.
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
next prev parent reply other threads:[~2012-02-21 16:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-20 22:21 Jerry Kirk
2012-02-21 8:58 ` Josef Holzmayr
2012-02-21 16:08 ` Jerry Kirk [this message]
2012-02-21 16:36 ` Josef Holzmayr
2012-02-21 17:58 ` Jerry Kirk
2012-02-21 9:39 ` Alexander Dahl
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=loom.20120221T170128-547@post.gmane.org \
--to=jkirk865@gmail.com \
--cc=ptxdist@pengutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox