Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Pieter Smith <pieter@boesman.nl>
To: buildroot@busybox.net
Subject: [Buildroot] [v3, 2/4] barebox: adds option to build secondary config
Date: Mon, 29 Feb 2016 09:01:58 +0100	[thread overview]
Message-ID: <20160229080158.GB18059@smipidev> (raw)
In-Reply-To: <56D0DF3B.1060305@mind.be>

On Sat, Feb 27, 2016 at 12:26:51AM +0100, Arnout Vandecappelle wrote:
> On 01/20/16 23:43, Pieter Smith wrote:
> > Support selection of secondary config, but version, source URL and patches are
> > shared with barebox bootloader build.

[snip]

>  So, if you remove the choice, then this config should stay and be called
> something like "build second Barebox configuration", with the help text from
> BR2_TARGET_BAREBOX_TWO_CONFIGS.
> 
>  And if the option of keeping barebox and just adding barebox-2 works out, then
> this can also go into a separate Config.in file in the barebox-2 directory,
> which is source'd from here.
> 
>  Also, it should be a menuconfig instead, since there are 5 entries.

ACK. Done. I also feel that each bootloader in the bootloader menu should be a
menuconfig item. Right now I find it hard to see the boundaries between
different bootloaders when options are used. But I won't try to solve the world
in a single patch series. ;-)

> > +
> > +if BR2_TARGET_BAREBOX_2
> > +
> > +choice
> > +	prompt "Type of configuration"
> > +	default BR2_TARGET_BAREBOX_2_USE_DEFCONFIG
> > +
> > +config BR2_TARGET_BAREBOX_2_USE_DEFCONFIG
> > +	bool "Using a defconfig"
> > +
> > +config BR2_TARGET_BAREBOX_2_USE_CUSTOM_CONFIG
> > +	bool "Using a custom config file"
> > +
> > +endchoice
> > +
> > +config BR2_TARGET_BAREBOX_2_BOARD_DEFCONFIG
> > +	string "Board defconfig"
> > +	depends on BR2_TARGET_BAREBOX_2_USE_DEFCONFIG
> > +	help
> > +	  Name of the board for which Barebox should be built, without
> > +	  the _defconfig suffix.
> > +
> > +
> 
>  Spurious line here.

Oops. Thanks.

>  Regards,
>  Arnout

[snip]

- Pieter

  reply	other threads:[~2016-02-29  8:01 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-20 22:43 [Buildroot] [v3, 0/4] Supporting building a second Barebox config Pieter Smith
2016-01-20 22:43 ` [Buildroot] [v3, 1/4] barebox: prepare for secondary config build Pieter Smith
2016-02-22 11:03   ` Yegor Yefremov
2016-02-26 23:17   ` Arnout Vandecappelle
2016-02-28  8:12     ` Pieter Smith
2016-02-29  7:47       ` Pieter Smith
2016-03-01 23:08         ` Arnout Vandecappelle
2016-03-02  7:50           ` Pieter Smith
2016-03-02 18:12             ` Arnout Vandecappelle
2016-03-02 21:32               ` Pieter Smith
2016-03-05 13:16                 ` Pieter Smith
2016-03-06 21:16                   ` Arnout Vandecappelle
2016-03-07 18:31                     ` Pieter Smith
2016-02-29  7:57     ` Pieter Smith
2016-01-20 22:43 ` [Buildroot] [v3, 2/4] barebox: adds option to build secondary config Pieter Smith
2016-02-22 11:03   ` Yegor Yefremov
2016-02-26 23:26   ` Arnout Vandecappelle
2016-02-29  8:01     ` Pieter Smith [this message]
2016-01-20 22:43 ` [Buildroot] [v3, 3/4] barebox: user selection of build output images Pieter Smith
2016-02-22 11:03   ` Yegor Yefremov
2016-02-26 23:43   ` Arnout Vandecappelle
2016-02-29  8:38     ` Pieter Smith
2016-03-01 23:14       ` Arnout Vandecappelle
2016-03-02  7:54         ` Pieter Smith
2016-03-02 18:18           ` Arnout Vandecappelle
2016-03-02 21:40             ` Pieter Smith
2016-03-06 23:03               ` Arnout Vandecappelle
2016-01-20 22:43 ` [Buildroot] [v3, 4/4] beaglebone: adds barebox bootloader defconfig Pieter Smith
2016-02-22 11:04   ` Yegor Yefremov
2016-02-26 23:47   ` Arnout Vandecappelle
2016-02-26 23:48     ` Arnout Vandecappelle
2016-02-29  8:44     ` Pieter Smith
2016-03-01 23:15       ` Arnout Vandecappelle
2016-03-02  7:55         ` Pieter Smith
2016-02-16 11:55 ` [Buildroot] [v3, 0/4] Supporting building a second Barebox config Yegor Yefremov
2016-02-16 18:55   ` Pieter Smith
2016-02-16 21:27     ` Yegor Yefremov
2016-02-21 17:25       ` Pieter Smith

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160229080158.GB18059@smipidev \
    --to=pieter@boesman.nl \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox