Skip to contentSkip to conversation

Buildroot cleanup

RFC PATCH New angus salkeld 3 participants 3 messages Sep 8, 2009 – Sep 9, 2009

lore
Share & tools
lore
#0 lore raw

cover Buildroot cleanup

Quoted 12 lines

Sven> Hi,

Quoted 5 lines · angus salkeld
Quoted 5 lines

Another suggestion would be to completely separate out the toolchain into a new package "buildcross.git" that only builds the cross toolchain and then buildroot always uses the external toolchain. It would make buildroot's toolchain setup simpler (one toolchain mode). And make sharing toolchains more obvious.

Sven> I like that idea. Can't really judge if it would be a success, but it Sven> seems like a nice solution that has the potential to simplify things.

Quoted 9 lines

I have been thinking about it myself. *REALLY* supporting toolchains for all the different architectures / variants, uclibc and (e)glibc and following up on compiler bugs takes quite some effort (and noone seems willing to do it for buildroot), so maybe the best long term solution is simply to deprecate the toolchain building stuff and just recommend crosstool-ng instead?

This would make BR less selfcontained / one-stop-shop though.

Well you could treat crosstool-ng as just another package that is available to build.
So if you select crosstool-ng, buildroot automatically sets up the correct external toolchain options.

Regards
Angus Salkeld

#1 lore raw

cover Buildroot cleanup

Le Wed, 09 Sep 2009 09:51:32 +1200,
"angus salkeld" <[email protected]> a ?crit :

Quoted 4 lines

Well you could treat crosstool-ng as just another package that is available to build.
So if you select crosstool-ng, buildroot automatically sets up the correct external toolchain options.

That's my long term plan. Introduce a new toolchain type in Buildroot:
Crosstool-NG toolchain. Just like for uClibc today, Buildroot would produce/tune the Crosstool-NG configuration before running the Crosstool-NG compilation process. We could have this in parallel to the internal building system for toolchains for a while, and then when we're satisfied, switch to Crosstool-NG completely by removing the old mechanism.

Sincerly,

Thomas

Signature · 4 lines
Thomas Petazzoni, Free Electrons
Kernel, drivers and embedded Linux development,
consulting, training and support.
http://free-electrons.com
#2 lore raw

cover Buildroot cleanup

In reply to angus salkeld
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

"angus" == angus salkeld <[email protected]> writes:

Hi,

Quoted 2 lines
Quoted 2 lines

This would make BR less selfcontained / one-stop-shop though.

angus> Well you could treat crosstool-ng as just another package that angus> is available to build. So if you select crosstool-ng, buildroot angus> automatically sets up the correct external toolchain options.

Yes, that sounds like a nice idea. I'll take a closer look at crosstool-ng in the near future to see how easy this would be..

Signature · 1 line
Bye, Peter Korsgaard