Re: [PATCH 00/49] Rootfs/image generation refactoring (cover letter only)

["David Nyström" <david.nystrom@enea.com>]

On 2014-02-04 16:34, Laurentiu Palcu wrote:
> On Tue, Feb 04, 2014 at 03:49:25PM +0100, David Nyström wrote:
>>
>> Oops, bug on my behalf in above example, but it still fails the same
>> way when using a correct IPK_FEED_URI.
>>
>> IPK_FEED_URIS += " \
>>             all##file:///media/sdb5/repo/build/tmp/deploy/ipk/all \
>> 	   ${MACHINE}##file:///media/sdb5/repo/build/tmp/deploy/ipk/${MACHINE} \
>>
>> ${TARGET_ARCH}##file:///media/sdb5/repo/build/tmp/deploy/ipk/${TARGET_ARCH}
>> \
>> 	   "
> Ok, I succeeded to check this in master. Apparently, I understood this
> wrong. In my tests I was deleting the tmp/ and sstate-cache/ and I was
> not expecting the target packages to be re-built. It turns out that this
> entire process takes place but when the rootfs is created, the provided
> feeds are used... I learned something new today! :)

Yes, if you only run bitbake -c rootfs core-image-minimal, no target 
packages _should_ be built.
It so happens that a few will still be built, for unknown reasons. But 
this should be considered a bug.
native and cross packages will of course be built regardless.

> Regarding the refactored code, indeed, it does not work in this case. It
> always tries to create the index files in the deploy/ipk directory
> before continuing with the rootfs creation. I guess a condition should
> be added in the new code to check for BUILD_IMAGES_FROM_FEEDS and skip
> the index creation step... Shouldn't be hard to fix.

Thanks Laurentiu.

> laurentiu
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>