[Buildroot] Understanding More about applying patches

Charles Krinke charles.krinke at gmail.com
Sat Jul 28 18:27:30 UTC 2012


Thank you both. I think I get enough to move forward.

Charles
On Jul 28, 2012 10:32 AM, "Samuel Martin" <s.martin49 at gmail.com> wrote:

> Hi Charles,
>
> 2012/7/28 Charles Krinke <charles.krinke at gmail.com>:
> > Assuming I have the last part correct, the next step is to add a patch
> > after the configure step but before the build step.
> You have nothing to do here, this is automatically handled by the
> package infrastructure,
> unless the package uses handwritten *.mk file.
>
> >
> > To do this, I need to add the patch to output/build/qt* somehow. So, I
> > guess my patching question is extending a bit.
> The only thing to do is put the patch in the package directory:
> package/<packagename>/<packagename>-<some_description>.patch
>
> >
> > On Sat, Jul 28, 2012 at 9:55 AM, Charles Krinke
> > <charles.krinke at gmail.com> wrote:
> >> Doing a bit of research and trying to answer at least part of my own
> >> question, I can see in pkg-gentargets.mk a statement applying patches
> >> and it looks like if I prefix the patches with the name of the
> >> package, "qt-" in this  case, then buildroot should automagically
> >> apply the patches I am trying to add. Is this correct?
> Yes, it is.
>
>
> BTW, here is a bunch of the doc refactoring (still in progress)
> talking about patch integration:
>
> https://github.com/tSed/buildroot/blob/sma/docs/docs/manual/patch-policy.txt
>
> Any feedback is welcome.
>
>
> Cheers,
>
> --
> Sam
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20120728/fb1cc506/attachment.html>


More information about the buildroot mailing list