[Buildroot] [PATCH v4] toolchain-external: Commonize /lib/<tuple> symlinks

Romain Naour romain.naour at gmail.com
Tue Jul 5 15:25:09 UTC 2016


Hi Matt,

Le 05/07/2016 à 17:16, Matt Fornero a écrit :
>> -----Original Message-----
>> From: Romain Naour [mailto:romain.naour at gmail.com]
>> Sent: Monday, July 04, 2016 7:18 AM
>> To: Matt Fornero <Matt.Fornero at mathworks.com>;
>> buildroot at busybox.net
>> Subject: Re: [Buildroot] [PATCH v4] toolchain-external: Commonize
>> /lib/<tuple> symlinks
>>
> [snip]
> 
>> After some discussion with other developers, I suggest you to register
>> the TOOLCHAIN_EXTERNAL_POST_INSTALL_STAGING_HOOKS from
>> BR2_EXTERNAL instead of adding a new configuration option to
>> Buildroot. That way you can customize easily what should be done for
>> your specific toolchain.
>>
>> I'm doing this for my CodeSourcery x86 standard toolchain which require
>> another symlink in staging directory.
>>
> 
> Hi Romain,
> 
> If I understand this correctly, I would simply define a new package in the BR2_EXTERNAL directory that was responsible for creating the symlinks as a _POST_INSTALL_STAGING_HOOKS action, and then enable this package for configurations that used the "custom" Linaro toolchains?

Yes, but the hook should be TOOLCHAIN_EXTERNAL_POST_INSTALL_STAGING_HOOKS in
order to be done during toolchain install.

Best regards,
Romain

> 
> -Matt
> 



More information about the buildroot mailing list