From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/4] Supporting a second Barebox build to build the MLO/SPL
Date: Tue, 27 Oct 2015 21:18:25 +0100 [thread overview]
Message-ID: <562FDC11.3080109@mind.be> (raw)
In-Reply-To: <20151027172130.GA15385@smipidev>
On 27-10-15 18:21, Pieter Smith wrote:
> What are your thoughts on this?
Thinking out of the box here: would it be possible to keep a single barebox
package and do everything twice (or more) in the _CMDS, with different output
directories?
Granted, that will be a bit tricky w.r.t. the kconfig infra.
Regards,
Arnout
--
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:[~2015-10-27 20:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-25 19:33 [Buildroot] [PATCH 0/4] Supporting a second Barebox build to build the MLO/SPL Pieter Smith
2015-10-25 19:33 ` [Buildroot] [PATCH 1/4] barebox: prepare for x-loader build Pieter Smith
2015-10-25 19:33 ` [Buildroot] [PATCH 2/4] barebox: adds option to build x-loader Pieter Smith
2015-10-25 19:33 ` [Buildroot] [PATCH 3/4] barebox: user selection of build output images Pieter Smith
2015-10-25 19:33 ` [Buildroot] [PATCH 4/4] beaglebone: adds barebox bootloader defconfig Pieter Smith
2015-10-26 3:57 ` [Buildroot] [PATCH 0/4] Supporting a second Barebox build to build the MLO/SPL Thomas Petazzoni
2015-10-26 21:27 ` Pieter Smith
2015-10-27 17:21 ` Pieter Smith
2015-10-27 20:18 ` Arnout Vandecappelle [this message]
2015-11-02 21:38 ` 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=562FDC11.3080109@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