From mboxrd@z Thu Jan  1 00:00:00 1970
From: Yegor Yefremov <yegorslists@googlemail.com>
Date: Thu, 29 Jan 2015 08:46:22 +0100
Subject: [Buildroot] Best-Practice Suggestions for developing package
 patches in buildroot
In-Reply-To: <CAJpxd069iQi27WrZ+LuzM_dEZxFHot4aDHTtkcgJnNBU1QSHgA@mail.gmail.com>
References: <CAJpxd069iQi27WrZ+LuzM_dEZxFHot4aDHTtkcgJnNBU1QSHgA@mail.gmail.com>
Message-ID: <CAGm1_ku6SdP2jbM8K71ykv2pwBz7e7LtDw1bVFqmZ+YwpFOGDw@mail.gmail.com>
List-Id: <buildroot.busybox.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: buildroot@busybox.net

Hi Bryce,

On Thu, Jan 29, 2015 at 1:04 AM, Bryce Schober <bryce.schober@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