[Buildroot] Understanding More about applying patches

[Charles Krinke]

Assuming I have the last part correct, the next step is to add a patch
after the configure step but before the build step.

To do this, I need to add the patch to output/build/qt* somehow. So, I
guess my patching question is extending a bit.

Charles

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?
>
> On Sat, Jul 28, 2012 at 9:07 AM, Charles Krinke
> <charles.krinke at gmail.com> wrote:
>> First of all, this is my day to be a "noob" again along with the funny
>> hat and the pocket protector.
>>
>> I am trying to understand a bit more about buildroot as I try to
>> figure out how opengl and Qt fit together for the TI AM3517EVM. I have
>> gotten to the point where I can compile Qt and the "TI Graphics SDK"
>> which builds the opengl libraries outside a buildroot tree but using a
>> buildroot toolchain. At this point, I need to understand a bit about
>> how patching works and I am coming up without understanding in going
>> through the documentation.
>>
>> I can see in a few buildroot/package directories some patches and
>> there are three in package/qt and they are applied. I need to add 3
>> more. What I cannot see is how the existing three are applied.
>>
>> I look through the .mk files for directories with patches and see no
>> mention of applying the patches.
>>
>> Can someone help me understand please how one goes about adding a new
>> patch to a buildroot/package directory after unzipping the package
>> tarball but before the configure step. Perhaps if I understood how to
>> add a patch to an existing package, I can extrapolate a bit to move
>> forward.
>>
>> I see mention of PRE_CONFIGURE_HOOKS & POST_CONFIGURE_HOOKS, but how
>> to use these and if these are the method doesnt quite fit in my
>> Saturday morning noobie mind today.
>>
>> --
>> Charles Krinke
>
>
>
> --
> Charles Krinke



-- 
Charles Krinke