[Buildroot] [PATCH] targets: move target options to their own sub-menu

[Thomas De Schampheleire]

On Fri, Aug 16, 2013 at 12:24 PM, Thomas De Schampheleire
<patrickdepinguin+buildroot at gmail.com> wrote:
> On Fri, Aug 16, 2013 at 8:39 AM, Yann E. MORIN <yann.morin.1998 at free.fr> wrote:
>> Thomas, Arnout, All,
>>
>> On Friday 16 August 2013 08:30:43 Thomas De Schampheleire wrote:
>>> On Fri, Aug 16, 2013 at 1:10 AM, Arnout Vandecappelle <arnout at mind.be> wrote:
>>> > On 15/08/13 22:28, Yann E. MORIN wrote:
>>> >>
>> I would even put the kernel before the packages, and bootloaders before
>> kernel. Ie. I'd use the boot-time order of things:
>>     (Target options)
>>     Build options
>>     Toolchain
>>     System configuration
>>     Bootloaders
>>     Kernel
>>     Packages selection
>>     Filesystem images
>>     Host Utilities
>>     Legacy config options
>>
>> Bizzarely enough, moving bootloaders before kernel seems odd... :-/
>
>
> I can follow this boot-time order strategy, but I concur with the
> bootloader oddity.

[sorry, accidentally hit send button]

Here is a slightly different viewpoint: some users will never touch
the bootloader. However, creating a kernel and rootfs (possibly
attached to the kernel) is very common. This can result in the
following order:

(Target options)
Build options
Toolchain
System configuration
Kernel
Package selection for the target
Filesystem images
Bootloaders
Host Utilities
Legacy config options


By the way: isn't it more logical to put 'Bootloaders' in singular
(Bootloader), since one typically builds only one bootloader, just as
one only builds one kernel...

Best regards,
Thomas