From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bryce Schober Date: Wed, 28 Jan 2015 16:04:19 -0800 Subject: [Buildroot] Best-Practice Suggestions for developing package patches in buildroot Message-ID: List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net 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: