Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Future...TOOLCHAIN builds..
Date: Mon, 7 Nov 2011 16:35:57 +0100	[thread overview]
Message-ID: <20111107163557.27aaa627@skate> (raw)
In-Reply-To: <1531E53627F1F749B4FE809BF2A4EB6702C39314@WETMEX10.loepfe.com>

Hello Noel,

Le Mon, 7 Nov 2011 16:07:35 +0100,
"Vellemans, Noel" <Noel.Vellemans@visionBMS.com> a ?crit :

> While following the discussions on the buildroot mailing list, I saw
> that for the next releases the CROSSTOOL-NG toolchain will be used as
> default, so a started to experiment with the CROSSTOOL-NG buildroot
> toolchain (this morning).

Great! It's really nice to have feedback on this.

> Until now.. U used the buildroot to generate a 'cross-toolchain', even
> 'worse'; I used buildroot to generate 2 toolchains. 
> 	A) One running on LINUX 
> 	B) One running on top of CYGWIN (for the less Linux-minded
> colleagues)

Do you use Buildroot only to build a toolchain ?

> 1) Will this also be possible for the CROSSTOOL-NG toolchain that is
> build with buildroot?

If you build only a toolchain, then crosstool-NG is a very good
replacement for Buildroot.

If you build a toolchain and then use Buildroot to build an embedded
Linux build system, then you can build your toolchain with crosstool-NG
separately, and then use it as an external toolchain in Buildroot, or
you can instruct Buildroot to use crosstool-NG has a backed to build
the toolchain.

Note that we intend to do in 2012.02 is move the crosstool-NG backend
as the default, not to remove the Buildroot code to build toolchain,
which will still be offered as an alternate choice. However, on the
long run, if everything works fine, we might drop the Buildroot code to
build the toolchain.

> 2) Another question that pops-up when building a CROSSTOOL-NG toolchain,
> is that I'm not able to select a toolchain with ARM-VECTOR-floating
> point support is this correct? 

In Target Options -> Floating Point, you can choose between hardware
floating point and software floating point. There are patches being
discussed/reviewed to add a choice between the hard and softfp ABI to
pass floating-point arguments. And I'm sure than Yann, crosstool-NG's
maintainer, is definitely interested by patches improving things in
that area.

> NOTE: Of the record, the buildroot-CYGWIN-toolchain build was working
> until some weeks ago (for me), in the current git-tree this is not
> working anymore ( build troubles into mpc/mpfr and gmp), without looking
> to much in detail (I think) it has to do with  'another' way of naming
> libs 'libxxxxx' on Linux vs 'cygxxxxxxx' on cygwin!

Buildroot has never supported officially Cygwin, and nobody tests this.
I think crosstool-NG has better support for this, but Yann might
comment on this.

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2011-11-07 15:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-07 15:07 [Buildroot] Future...TOOLCHAIN builds Vellemans, Noel
2011-11-07 15:35 ` Thomas Petazzoni [this message]
2011-11-08 23:46   ` Yann E. MORIN
2011-11-09  8:13     ` Thomas Petazzoni
2011-11-08 23:38 ` Yann E. MORIN
     [not found] <mailman.1400.1320692517.2942.buildroot@busybox.net>
2011-11-08  7:14 ` Vellemans, Noel
2011-11-08 16:44   ` Peter Korsgaard
  -- strict thread matches above, loose matches on Subject: below --
2011-11-08 13:33 Vellemans, Noel

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=20111107163557.27aaa627@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