From: William Wagner <will_wagner@carallon.com>
To: buildroot@busybox.net
Subject: [Buildroot] On strip and debugging symbols
Date: Wed, 23 Jun 2010 10:47:13 +0100 [thread overview]
Message-ID: <4C21D821.10000@carallon.com> (raw)
In-Reply-To: <20100623104613.78fe0d97@surf>
On 23/06/2010 09:46, Thomas Petazzoni wrote:
>
> As mentionned before, adding $(STAGING_DIR)/usr/bin to the path is just
> wrong. The possible solutions to this are :
>
> * Install the toolchain outside of $(STAGING_DIR) and then re-use what
> we do for external toolchains, and then tell people to not add
> $(STAGING_DIR)/usr/bin to their PATH, but rather the location where
> the toolchain was installed. This has the added benefit that
> $(STAGING_DIR) would not contain binaries compiled for the host,
> mixed with binaries compiled for the target.
>
>
I think that long term making sure that target and host binaries do not
end up in the same folder is a good idea. Creating a new folder for host
tools and putting toolchain in there seems like quite a clear way of
doing things, but would obviously cause a lot of disruption as people
learnt the new way of doing things.
Will
prev parent reply other threads:[~2010-06-23 9:47 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-21 23:25 [Buildroot] sdl demo app install problem H Hartley Sweeten
2010-06-21 23:32 ` Peter Hüwe
2010-06-21 23:41 ` H Hartley Sweeten
2010-06-21 23:47 ` Peter Hüwe
2010-06-21 23:59 ` H Hartley Sweeten
2010-06-22 1:05 ` H Hartley Sweeten
2010-06-22 1:18 ` Peter Hüwe
2010-06-22 6:54 ` Thomas Petazzoni
2010-06-22 14:41 ` Peter Korsgaard
2010-06-22 15:39 ` H Hartley Sweeten
2010-06-22 20:32 ` Peter Korsgaard
2010-06-23 7:12 ` [Buildroot] On strip and debugging symbols Thomas Petazzoni
2010-06-23 7:40 ` Peter Korsgaard
2010-06-23 8:46 ` Thomas Petazzoni
2010-06-23 9:36 ` Peter Korsgaard
2010-06-23 9:51 ` Thomas Petazzoni
2010-06-23 10:02 ` Peter Korsgaard
2010-06-23 11:12 ` Thomas Petazzoni
2010-06-23 11:24 ` Peter Korsgaard
2010-06-23 9:47 ` William Wagner [this message]
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=4C21D821.10000@carallon.com \
--to=will_wagner@carallon.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