From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] B2_EXTERNAL and patches
Date: Fri, 12 Dec 2014 10:06:53 +0100 [thread overview]
Message-ID: <20141212100653.54e396c9@free-electrons.com> (raw)
In-Reply-To: <trinity-73676462-8b93-436d-9361-468b01882a1f-1418374738886@3capp-gmx-bs63>
Dear Peter Kuemmel,
On Fri, 12 Dec 2014 09:58:58 +0100, Peter Kuemmel wrote:
> I would like use one minimal patched Builroot release in one branch for multiple projects,
> so is it also possible to maintain different patches for a packages in different external folders?
> Or could the selecition of patches be controlled by a configuration file?
> (the different pachtes are necessary because of differenr kernel versions)
You want to have a look at BR2_GLOBAL_PATCH_DIR.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-12-12 9:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-12 8:58 [Buildroot] B2_EXTERNAL and patches Peter Kuemmel
2014-12-12 9:06 ` Thomas Petazzoni [this message]
2014-12-12 9:15 ` Peter Kümmel
2014-12-12 9:11 ` Jeremy Rosen
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=20141212100653.54e396c9@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--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