From: Jerry Kirk <jkirk865@gmail.com>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Advice on Directory Structure
Date: Tue, 21 Feb 2012 17:58:53 +0000 (UTC) [thread overview]
Message-ID: <loom.20120221T185228-60@post.gmane.org> (raw)
In-Reply-To: <4F43C804.2080404@rsi-elektrotechnik.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
next prev parent reply other threads:[~2012-02-21 17:59 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
2012-02-21 16:36 ` Josef Holzmayr
2012-02-21 17:58 ` Jerry Kirk [this message]
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.20120221T185228-60@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