From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Adding a patch in a different directory
Date: Fri, 15 Mar 2013 11:01:29 +0100 [thread overview]
Message-ID: <20130315110129.2454684f@skate> (raw)
In-Reply-To: <CAHt8ZCMY=kbSmCg8r7BWFZ1GFuXutRjBDov+wWCa_ZGMncUMtg@mail.gmail.com>
Dear Simon Dawson,
On Fri, 15 Mar 2013 07:30:56 +0000, Simon Dawson wrote:
> On 15 March 2013 00:50, Charles Manning <cdhmanning@gmail.com> wrote:
> > What I would like to do is get buildroot to use the patch in foo/patches.
> >
> > Any ideas how to achieve this?
>
> I submitted a patch a while ago to add support for custom package patches:
>
> http://patchwork.ozlabs.org/patch/222260/
>
> The patch has not been accepted as of this writing, but you can
> achieve your goal by adding something like the following to your
> local.mk
We discussed this at the Buildroot Developers Meeting, and we agreed on
a model for patches, that would apply to both "internal" patches and
"external" patches.
The report of the meeting contains:
"""
Change of the patch logic
* For the patches stored in the package directory, if
package/<pkg>/<version>/ does exist, apply
package/<pkg>/<version>/*.patch, otherwise, apply
package/<pkg>/*.patch
* For the patches stored in the global patches directory, if
$(GLOBAL_PATCH_DIR)/<pkg>/<version>/ does exist, apply
$(GLOBAL_PATCH_DIR)/<pkg>/<version>/*.patch, otherwise, apply
$(GLOBAL_PATCH_DIR)/<pkg>/*.patch
"""
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-03-15 10:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-15 0:50 [Buildroot] Adding a patch in a different directory Charles Manning
2013-03-15 7:30 ` Simon Dawson
2013-03-15 10:01 ` Thomas Petazzoni [this message]
2013-03-15 10:15 ` Simon Dawson
2013-03-15 10:54 ` Thomas Petazzoni
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=20130315110129.2454684f@skate \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.