All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hamish Moffatt <hamish@cloud.net.au>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit:	trunk/buildroot/toolchain/external-toolchain
Date: Tue, 17 Jun 2008 20:47:54 +1000	[thread overview]
Message-ID: <20080617104754.GA25850@cloud.net.au> (raw)
In-Reply-To: <87ej6wwmxw.fsf@macbook.be.48ers.dk>

On Tue, Jun 17, 2008 at 09:16:43AM +0200, Peter Korsgaard wrote:
>  Hamish> On Mon, Jun 16, 2008 at 05:22:46AM -0700, jacmet at uclibc.org wrote:
>  >> config BR2_TOOLCHAIN_EXTERNAL_PATH
>  >> string "External toolchain path"
>  >> -	default ""
>  >> +	default "/path/to/staging_dir/usr"
>  >> help
>  >> Path to where the external toolchain is installed.
> 
>  Hamish> I've set this to "$(BR2_STAGING_DIR)/usr" here, which might
>  Hamish> be a good default?
> 
> You think so? I wouldn't expect having buildroot install package stuff
> together with the (potentially read only) external toolchain would be
> a common setup.

Well I've got one board ("tools", in local/tools/tools.config) to build
the toolchain which I then use as external toolchain to build several
other boards (all armeb-linux-uclibcgnu). So my toolchain lives in the
staging directory in the same tree.

This makes for a nice path-independent setup too.. other developers at
my company can check out the tree and build everything (including the
toolchain first) into any path they like.

So if this isn't a common approach then maybe it isn't a good default
after all.

> Don't you have an armeb-linux symlink? For the stuff I compile (arm,
> i386, ppc) there's symlinks from the arm-linux-uclibc-<whatever> to
> arm-linux-<whatever>.

Probably, I'll have to check tomorrow.

thanks
Hamish
-- 
Hamish Moffatt VK3SB <hamish@debian.org> <hamish@cloud.net.au>

  reply	other threads:[~2008-06-17 10:47 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-16 12:22 [Buildroot] svn commit: trunk/buildroot/toolchain/external-toolchain jacmet at uclibc.org
2008-06-16 13:54 ` Bernhard Fischer
2008-06-16 14:07   ` Peter Korsgaard
2008-06-16 15:35     ` Bernhard Fischer
2008-06-17  4:23 ` Hamish Moffatt
2008-06-17  7:16   ` Peter Korsgaard
2008-06-17 10:47     ` Hamish Moffatt [this message]
2008-06-17 13:45       ` Peter Korsgaard
2008-06-17 14:29         ` Bernhard Fischer
2008-06-17 14:55           ` Peter Korsgaard
2008-06-17 15:45             ` Bernhard Fischer
2008-06-18  1:18         ` Hamish Moffatt
2008-06-18  5:03           ` [Buildroot] svncommit: trunk/buildroot/toolchain/external-toolchain Ulf Samuelsson
2008-06-18  7:36           ` [Buildroot] svn commit: trunk/buildroot/toolchain/external-toolchain Peter Korsgaard
2008-06-18  1:05       ` Hamish Moffatt
  -- strict thread matches above, loose matches on Subject: below --
2009-01-12 12:54 laird at uclibc.org
2008-11-03 10:37 jacmet at uclibc.org
2008-11-03 10:32 jacmet at uclibc.org
2008-10-17 10:19 jacmet at uclibc.org
2007-07-17  0:18 sjhill at uclibc.org
2007-04-28 17:10 sjhill at uclibc.org
2007-04-19  2:04 sjhill at uclibc.org

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=20080617104754.GA25850@cloud.net.au \
    --to=hamish@cloud.net.au \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.