[Buildroot] [PATCH 2 of 5] toolchain-external: allow downloading a custom toolchain

Thomas De Schampheleire patrickdepinguin+buildroot at gmail.com
Wed Sep 21 08:22:16 UTC 2011

On Wed, Sep 21, 2011 at 9:58 AM, Thomas Petazzoni
<thomas.petazzoni at free-electrons.com> wrote:
> Le Wed, 21 Sep 2011 08:55:32 +0200,
> Thomas De Schampheleire <patrickdepinguin+buildroot at gmail.com> a écrit :
>> Custom external toolchains currently already have to be extracted by the user.
>> This patch adds support for downloading a custom toolchain in the form of a
>> tarball, which will be extracted by buildroot.
> I like this feature, but I think I'd prefer to clearly separate the
> cases of "local custom toolchain" and "remote custom toolchain".
> So, in the toolchain choice :
>  * All the CodeSourcery toolchains
>  * Local custom toolchain
>  * Remote custom toolchain
> When Local custom toolchain is selected, show :
>  * Path of the toolchain
>  * Prefix of the toolchain
> When Remote custom toolchain is selected, show :
>  * URL of the toolchain tarball (please don't split site and source in
>   the configuration, we don't do that in any other place in Buildroot,
>   and it's really strange for the user to have to split the URL in two
>   parts)
>  * Prefix of the toolchain
> What do you think ?

For me it's fine to keep the distinction, but be aware that the
local/remote naming may be confusing: if a user receives a toolchain
tarball from e.g. a hardware manufacturer and saves it to his disk, I
would call it 'local'. But that user would typically like to use the
'remote' rules so that he does not need to unpack the toolchain

Maybe we should call it 'custom toolchain tarball' versus 'custom
unpacked toolchain' or something alike. The tarball can be either
local (file://something) or remote (http, ftp, scp, ...).

Best regards,

> Thomas
> --
> Thomas Petazzoni, Free Electrons
> Kernel, drivers, real-time and embedded Linux
> development, consulting, training and support.
> http://free-electrons.com
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot

More information about the buildroot mailing list