[coreboot] Does the coreboot build system support external patches?

[Martin Roth]

coreboot uses the site-local directory to allow users to extend the
coreboot build outside of the regular coreboot coreboot files.
Create the coreboot/site-local directory, and add Makefile.inc and Kconfig
files.  Both of these files will get picked up by coreboot.

To run steps at the start of the build, you can create a target that does
whatever is needed, then calls the 'all:' target to do the build.
At the end of the build, you can hook into the 'build_complete::' target to
run whatever finalization steps are needed.

Martin

On Thu, Feb 1, 2018 at 10:53 AM, Jay Talbott <
JayTalbott at sysproconsulting.com> wrote:

> I got this question from a client yesterday that I didn’t know how to
> answer because I focus primarily on the porting effort (getting coreboot to
> build and boot for their hardware) and let the client figure out how they
> want to manage the resulting code base once the porting effort is complete.
> So I offered to inquire of the coreboot community to see if anybody can
> provide an answer for my client.
>
>
>
> Below is the inquiry that I received:
>
>
>
> I’m looking at how best to structure our coreboot repositories.  Does the
> coreboot build system support the concept of external patches? With
> buildroot you can keep your changes is a directory tree separate from the
> FOSS tree. Then during the build step your patches get applied and compiled
> using another separate build tree.
>
>
>
> Thanks,
>
>
>
> - Jay
>
>
>
> Jay Talbott
> Principal Consulting Engineer
> SysPro Consulting, LLC
> 3057 E. Muirfield St.
> Gilbert, AZ 85298
> (480) 704-8045
> (480) 445-9895 (FAX)
> JayTalbott at sysproconsulting.com
>
> http://www.sysproconsulting.com
>
>
>
> --
> coreboot mailing list: coreboot at coreboot.org
> https://mail.coreboot.org/mailman/listinfo/coreboot
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.coreboot.org/pipermail/coreboot/attachments/20180201/28fa36d9/attachment.html>