From: Ulf Samuelsson <ulf.samuelsson@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/toolchain: export-toolchain uClibc
Date: Fri, 02 Jan 2009 23:23:25 +0100 [thread overview]
Message-ID: <1230935005.8886.13.camel@linux-yrgm.site> (raw)
In-Reply-To: <87fxkf6vdl.fsf@macbook.be.48ers.dk>
tis 2008-12-23 klockan 11:25 +0100 skrev Peter Korsgaard:
> >>>>> "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?
Sorry about the late answer.
Have had a disk crash and did not install the account
for reading buildroot mail until after the holidays.
Adding a path is manual and error prone.
This is more productive since you can with a single
click create something that works.
You can of course also have several toolchains,
and select which you want at a specific time.
>
> 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.
What exactly is broken?
"Seems do" != "does".
Have you tested and found that you cannot build a toolchain or what??
>
> 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?
Exactly.
>
> ulf> +~/$(GCC_SCRIPT): cross_compiler
>
> I'm not sure ~ in make targets are a good idea.
>
If you want to have a script file in your top directory, why not?
It is a possibility to fix so that it gets built in a subdirectory
to ~ as well or by defining a BUILDROOT_<XXX> shell variable
and install it in $(BUILDROOT_XXX)/?$(GCC_SCRIPT).
/Ulf
next prev parent reply other threads:[~2009-01-02 22:23 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
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 [this message]
-- 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=1230935005.8886.13.camel@linux-yrgm.site \
--to=ulf.samuelsson@atmel.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