All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/toolchain: export-toolchain uClibc
Date: Tue, 23 Dec 2008 11:25:42 +0100	[thread overview]
Message-ID: <87fxkf6vdl.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <20081221171134.7BAB176ABE@busybox.osuosl.org> (ulf@uclibc.org's message of "Sun\, 21 Dec 2008 17\:11\:34 +0000 \(UTC\)")

>>>>> "ulf" == ulf  <ulf@uclibc.org> writes:

 ulf> Author: ulf
 ulf> Date: 2008-12-21 17:11:33 +0000 (Sun, 21 Dec 2008)
 ulf> New Revision: 24480

 ulf> Log:
 ulf> Allow creating a script for external use of Buildroot toolchain

 ulf> Added:
 ulf>    trunk/buildroot/toolchain/export-toolchain/
 ulf>    trunk/buildroot/toolchain/export-toolchain/Config.in
 ulf>    trunk/buildroot/toolchain/export-toolchain/Makefile.in

That seems very specific - What's wrong with the currently documented
way of adding build_$ARCH/staging_dir/usr/bin to the path? Where's the
documentation of this thing?

 ulf> Modified:
 ulf>    trunk/buildroot/toolchain/Config.in
 ulf>    trunk/buildroot/toolchain/Makefile.in
 ulf>    trunk/buildroot/toolchain/uClibc/Config.in

 ulf> +++ trunk/buildroot/toolchain/Makefile.in	2008-12-21 17:11:33 UTC (rev 24480)
 ulf> @@ -47,3 +47,5 @@
 ulf>  # gcc has a bunch of needed stuff....
 ulf>  include toolchain/gcc/Makefile.in
 
 ulf> +include toolchain/export-toolchain/Makefile.in
 ulf> +

This seems to break the build as the dependencies target isn't
executed before the other toolchain stuff - I've disabled it in
r24519.

 ulf> +config BR2_EXPORT_TOOLCHAIN
 ulf> +	bool "Create script exporting toolchain to home directory"
 ulf> +	default n
 ulf> +	help
 ulf> +	  This will generate a batchfile which, if run
 ulf> +	  will add the Buildroot toolchain to the user PATH
 ulf> +	  The file is called "$(ARCH)-uclibc-gcc-$(GCC_VERSION).sh"
 ulf> +

Batchfile? shell script? I take it that you need to source the file
for the changes to take effect?

 ulf> +~/$(GCC_SCRIPT): cross_compiler

I'm not sure ~ in make targets are a good idea.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2008-12-23 10:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-21 17:11 [Buildroot] svn commit: trunk/buildroot/toolchain: export-toolchain uClibc ulf at uclibc.org
2008-12-23 10:25 ` Peter Korsgaard [this message]
2009-01-02 20:37   ` Peter Korsgaard
2009-01-02 21:52     ` Ulf Samuelsson
2009-01-02 22:20       ` Peter Korsgaard
2009-01-02 22:23   ` Ulf Samuelsson
  -- strict thread matches above, loose matches on Subject: below --
2009-01-02 20:31 jacmet 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=87fxkf6vdl.fsf@macbook.be.48ers.dk \
    --to=jacmet@uclibc.org \
    --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.