[Buildroot] Can't use output/host/ as "SDK" with external toolchain
Peter Korsgaard
jacmet at uclibc.org
Wed Jan 11 23:03:22 UTC 2012
>>>>> "Bryce" == Bryce Schober <bryce.schober at gmail.com> writes:
Hi,
Bryce> I just tried that, and I get the same results. Both the binutils
Bryce> symbolic links and ext-toolchain-wrapper still use absolute
Bryce> paths. These patches don't touch the logic used to assemble a
Bryce> full sysroot with the compiler and buildroot host outputs in the
Bryce> same place.
Bryce> It seems that the current importing and wrapping of any type of
Bryce> external toolchain would have to be fundamentally re-worked in
Bryce> order to be relocatable.
Sorry, I haven't read the entire thread, but are you aware of the
discussions we had at the Buildroot developers day in October?
Thomas made a nice summary of it:
http://lists.busybox.net/pipermail/buildroot/2011-November/047229.html
Bryce> It seems that two things would need to change:
Bryce> 1. Any symbolic links created would have to have any absolute paths converted
Bryce> to relative.
Bryce> 2. Any paths used in the ext-toolchain-wrapper would have to be relative, and
Bryce> the wrapper itself would have to determine the path to itself in order to
Bryce> correctly exec the programs it wraps.
Other things need to be fixed as well (as listed in the summary):
- Host tools
- .la files / cmake / qmake configuraiton
- pkg-config
- ..
So it's a fairly major change.
--
Bye, Peter Korsgaard
More information about the buildroot
mailing list