From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [v3, 3/4] barebox: user selection of build output images
Date: Wed, 2 Mar 2016 00:14:15 +0100 [thread overview]
Message-ID: <56D62247.8000500@mind.be> (raw)
In-Reply-To: <20160229083817.GC18059@smipidev>
On 02/29/16 09:38, Pieter Smith wrote:
> On Sat, Feb 27, 2016 at 12:43:40AM +0100, Arnout Vandecappelle wrote:
>> On 01/20/16 23:43, Pieter Smith wrote:
>>> A non-default image can be selected as the barebox build output in the images/
>>> directory. This typically is needed to select the appropriate image generated
>>> by multi-platform support defconfigs (E.g. am335x).
>
> [snip]
>
>> If we deprecate barebox pre-2012.10, then we can simplify this a lot:
>>
>> config BR2_TARGET_BAREBOX_IMAGE_FILE
>> string "Image file path"
>> default "barebox-flash-image"
>> help
>> Name of the built barebox image file in the barebox images directory
>>
>>
>> Even if we don't want to deprecate barebox pre-2012.10, I'd prefer to keep this
>> simple config and do the handling of legacy barebox.bin in the .mk file. For
>> pre-2012.10, you'd have to explicitly set it to barebox.bin instead (which
>> should be mentioned in the help text then).
>
> ACK. Done. I solved this with the above default and help text pointing the user
> to use 'barebox.bin' for older versions. I'm just waiting for Yegor, and then
> I'll repost.
>
> Right now a user-friendly warning is generated if an old config is used and
> this config item has not yet been set.
If you give it a default value, it _will_ be set for old configs.
> I can have the makefile also generate a
> hint for older barebox versions if the image filename isn't found:
> - Do you think the additional complexity is warranted?
Yes, that's worth it.
Regards,
Arnout
>
>> We should find a good way to deal with the images/ part of the path, however.
>> This could e.g. be done in the .mk file, by checking both the top dir and the
>> images dir.
>
> ACK. Done. In v4 I first try the build ./ directory, and then ./images.
>
>> Regards,
>> Arnout
>
> [snip]
>
> - Pieter
>
>
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
next prev parent reply other threads:[~2016-03-01 23:14 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
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 [this message]
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=56D62247.8000500@mind.be \
--to=arnout@mind.be \
--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