[Buildroot] Best-Practice Suggestions for developing package patches in buildroot

[Yegor Yefremov]

Hi Bryce,

On Thu, Jan 29, 2015 at 1:04 AM, Bryce Schober <bryce.schober at gmail.com> wrote:
> Buildroot devs,
>
> It would be helpful to get ideas for how best to develop a set of patches
> against a package's upstream source inside of the buildroot context
> (cross-compiler, libraries, etc.).
>
> Do you use something like quilt to manage patches while developing them?
>
> Do you fork the upstream repository a switch the package to use the fork,
> then back out your modifications into patches?
>
> Do you just copy the full commands generated by buildroot and use re-use
> them outside of buildroot's high-level make commands?
>
> For package problems that can be reproduced & fixed outside of the full
> buildroot sysroot it's much less of a problem. I'm interested specifically
> in development workflows that would be helpful for packages that have
> problems that require the buildroot sysroot to reproduce and fix.

Please read Section 8.6.11 "Using Buildroot during development"
(http://nightly.buildroot.org/manual.html#_advanced_usage). It will
give you a good idea, how to work on upstream code.
<pkg1>_OVERRIDE_SRCDIR is the keyword.

Yegor