While working on a single package, I need to be able to tweak a variable in the new recipe, change the MACHINE in local.conf, etc. I'd like to be able to rapidly test my changes, but some of these changes trigger a long list of dependencies for various commands. While working on a new linux kernel recipe, I found it rebuilding a number of things that were either -native (can I force it to use the system version rather than building one) or seemed unrelated to the process at hand.

Are there some best practices for iterative recipe development that speed things along?

Thanks,

--
Darren Hart
Yocto Linux Kernel
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

Reply via email to