From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Installation of package files in staging and target
Date: Tue, 12 Jul 2011 13:51:40 +0200 [thread overview]
Message-ID: <20110712135140.4d2bd314@skate> (raw)
In-Reply-To: <1310468114.2189.8.camel@dublxciaranr1.verifone.com>
Le Tue, 12 Jul 2011 11:55:12 +0100,
Quotient Remainder <quotientvremainder@gmail.com> a ?crit :
> I'm a little behind in tracking the changes with toolchain movements
> from a few months back but I was of the understanding that the current
> install scheme still allows the staging directory to be treated as a
> kind of mini SDK and so if I build a system using Buildroot I can tar
> up the staging dir and give it to application developers as an
> interface. Is this still the case? If so, wouldn't putting
> executable programs into the staging dir be a bad thing?
Why would it be bad ? The binaries for the target are not inside
host/usr/bin, but inside host/usr/<tuple>/sysroot/usr/bin, so even if
the user adds host/usr/bin to its path to get access to the SDK, the
target binaries won't be visible.
It's true however that this would enlarge the size of the SDK.
Regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2011-07-12 11:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-11 22:01 [Buildroot] Installation of package files in staging and target Thomas Petazzoni
2011-07-11 22:22 ` Yann E. MORIN
2011-07-12 10:55 ` Quotient Remainder
2011-07-12 11:51 ` Thomas Petazzoni [this message]
2011-07-12 15:23 ` Quotient Remainder
2011-07-12 17:39 ` Yann E. MORIN
2011-07-12 19:48 ` Quotient Remainder
2011-07-12 20:46 ` Yann E. MORIN
2011-07-12 21:45 ` Quotient Remainder
2011-07-13 12:54 ` Quotient Remainder
2011-07-14 16:30 ` Quotient Remainder
2011-07-15 15:19 ` Alper YILDIRIM
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=20110712135140.4d2bd314@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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