[Buildroot] [PATCH 1/1] uboot: fix custom patch dir legacy handling

[Danomi Manchego]

On Tue, Dec 20, 2016 at 5:56 PM, Thomas Petazzoni
<thomas.petazzoni at free-electrons.com> wrote:
> Hello,
>
> On Tue, 20 Dec 2016 17:55:41 -0500, Danomi Manchego wrote:
>
>> Understood.  It's just that using a custom path for boot loaders and
>> the kernel is the norm for us, not an exception.  In fact, I've never
>> been on a project where we were able to use a main line kernel or
>> uboot.  Sometimes, we'll go through the exercise of making patches
>> against an initial state of a vendor's git repo, but many of out
>> project leaders prefer to just source control everything locally.
>> Under those circumstances, it's nicer to have the local path in the
>> defconfig than in a secondary local.mk or in the .mk file itself.
>
> If your U-Boot / Linux kernel source code is under version control, why
> don't you ask Buildroot to pull it from your Git/SVN/Mercurial/whatever
> repository ?

Perforce integration with Makefiles can be - tricky.  Our current
setup is to use buildroot as the core for our build system, with all
the proprietary apps and customized kernel and bootloader(s) at a
level parallel to buildroot, but built using override source
directories.  So the whole thing (buildroot, proprietary apps, kernel,
linux) are all checked at at once, not on a package by package basis.
We keep a local cache of the package tarballs, so nothing is
downloaded or pulled on-the-fly, buildroot-wise.