On 03/10/12 14:27, James Abernathy wrote:
On Wed, Oct 3, 2012 at 9:21 AM, Burton, Ross <ross.bur...@intel.com <mailto:ross.bur...@intel.com>>wrote:On 3 October 2012 14:05, James Abernathy <jfaberna...@gmail.com <mailto:jfaberna...@gmail.com>> wrote: > Now I see a bunch of patches pushed to Denzil branch and I want to test > them. My build directory is untouched since the successful build before. > What do I do to rebuild my project to include the latest patches. I've > tried things like "bitbake -c cleansstate core-image-cdv-media" before the > new "bitbake core-image-cdv-media" and I've tried just rebaking by itself. > Something always fails. I've learned that to really test I have to > completely delete my build directory saving only my local.conf and > bblayer.conf. Just git pull ; bitbake should work -- all of the packages that changed will rebuild without any problems. That's the theory, and everyone who works against oe-core/poky master does this ever day (including me). Can you give an example of something that fails? The most recent patch update to Denzil included some Cedartrail BSP updates to the CDV PVR driver. I was traveling last week and I was out of date on my poky and meta-intel by at least that long. Monday was the pull. So when the rebuild happened, I got a cdv-pvr driver configuration error. I didn't look into why because of my experience of this taking longer than a completerebuild. So I deleted the build directory and did the rebuild. And I didn't get the error on the rebuild. Everything still worksfine for me on that BSP. Jim A Ross
I also use this work flow. If something goes wrong with a particular package then I will -c cleansstate failed-package and then start the build again. This usually fixes it.
Regards,
_______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
-- Jack Mitchell (j...@embed.me.uk) Embedded Systems Engineer http://www.embed.me.uk -- _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
