[Buildroot] svn commit: trunk/buildroot/toolchain/external-toolchain

Bernhard Fischer rep.dot.nop at gmail.com
Tue Jun 17 14:29:37 UTC 2008

On Tue, Jun 17, 2008 at 03:45:04PM +0200, Peter Korsgaard wrote:
>>>>>> "Hamish" == Hamish Moffatt <hamish at cloud.net.au> writes:
> Hamish> I've set this to "$(BR2_STAGING_DIR)/usr" here, which might
> Hamish> be a good default?
> >> 
> >> You think so? I wouldn't expect having buildroot install package stuff
> >> together with the (potentially read only) external toolchain would be
> >> a common setup.
> Hamish> Well I've got one board ("tools", in
> Hamish> local/tools/tools.config) to build the toolchain which I then
> Hamish> use as external toolchain to build several other boards (all
> Hamish> armeb-linux-uclibcgnu). So my toolchain lives in the staging
> Hamish> directory in the same tree.
>So they all put libraries / headers in the same staging_dir? Doesn't
>that give problems with packages detecting optional stuff at compile
>time that might not be available for a specific variant (E.G. one
>variant has expat, and another doesn't - Some configure script checks
>for expat and finds it in staging_dir even though it isn't going to be
>there at runtime).
>The same with the packages offering different versions.
>I think a more common setup would be to install the toolchain
>somewhere common (/opt/<whatever>) and then have multiple boards using
>the same toolchain/c library but potentially different set of
>packages(-versions) and their own staging_dir.

If i understand correctly what you are talking about then this is
exactly the purpose of that PROJECT thing, fwiw.

More information about the buildroot mailing list