>From: Darren Hart >Sent: Saturday, November 20, 2010 7:14 AM > >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.
That's interesting. Did you build from scratch or incrementally? Ideally only recipes being changed will be rebuilt in incremental way. > >Are there some best practices for iterative recipe development that >speed things along? > "bitbake -k" is one method if you're sure the dependency doesn't change. But if you change MACHINE, I think a whole rebuild except -native will be required as it's the fundamental bit for target recipes. Thanks Kevin _______________________________________________ yocto mailing list [email protected] https://lists.yoctoproject.org/listinfo/yocto
