From: Erwin Rol <mailinglists@erwinrol.com>
To: ptxdist <ptxdist@pengutronix.de>
Subject: [ptxdist] Application Development on Ptxdist based OS's
Date: Wed, 02 Nov 2011 16:11:19 +0100 [thread overview]
Message-ID: <4EB15D97.2050905@erwinrol.com> (raw)
Hey all,
a while back I asked if it was possible to split an ptxdist build in two
parts, one for the (stable) OS and one for the application. On that
question I got some interesting answers that made me wonder;
How do others do their application development on ptxdist?
From origin Ptxdist is a distribution building tool, so it assumes all
applications are finished and combines all parts in a running
distribution. And it does a great job, I really can't complain about that.
But what if the applications are still in development, they need to be
edited, cross-compiled, debugged. And there is where Ptxdist is not so
great, at least that's my experience.
So how do other people do that ?
I read some ppl just don't use Ptxdist at all and just compile their
applications in a different way and "install" them on the finished
Ptxdist OS. But that duplicates the whole cross-chain stuff, like
compiler, libraries and headers.
I have seen other build systems that seem to export some "API" for use
by applications developers. Maybe something like that can be done with
Ptxdist too, for example exporting the sysroot-target directory and use
that to build applications.
Anny other people with wild ideas and nice custom Ptxdist enhancements
that they want to share ?
- Erwin
--
ptxdist mailing list
ptxdist@pengutronix.de
next reply other threads:[~2011-11-02 15:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-02 15:11 Erwin Rol [this message]
2011-11-02 18:21 ` Flavio de Castro Alves Filho
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=4EB15D97.2050905@erwinrol.com \
--to=mailinglists@erwinrol.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