[Buildroot] Best-Practice Suggestions for developing package patches in buildroot
Bryce Schober
bryce.schober at gmail.com
Thu Jan 29 00:04:19 UTC 2015
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.
Thanks,
Bryce Schober
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20150128/2763f24d/attachment.html>
More information about the buildroot
mailing list