[yocto] local file update vs rebuild

Takashi Matsuzawa tmatsuzawa at xevo.com
Wed Aug 2 04:03:08 PDT 2017


Hello.

Thank you for your comment.


I want to double check.


xxxx = image name

yyyy = recipe within xxxx


Then, I am not sure if doing below will rebuild yyyy from scratch.


$ bitbake xxxx -c cleansstate

$ bitbake xxxx


Especially, I am doing things like below within my yyyy.


SRC_URI += "file://src/*;subdir=local"


I want to be sure that, if I make modification to the local files (referred to as file://... path within SRC_URI variable of xxxx recipe), the changes are reflected to the final image.

(Not explicitly specifying -c cleansstate to xxxx).

________________________________
From: Khem Raj <raj.khem at gmail.com>
Sent: Tuesday, August 1, 2017 3:42 AM
To: Takashi Matsuzawa; yocto at yoctoproject.org
Subject: Re: [yocto] local file update vs rebuild



On 7/31/17 4:39 AM, Takashi Matsuzawa wrote:
> Hello.
> I am uncertain about do_clean behavior with local files.
>
>
> Say, I have local files referred by my recipe, and I have made changes to the files referred.
> (Note, there is no change in my xxxx.bb file itself.)
>
>
>> SRC_URI += "file://src/*;subdir=local"
>
>
> What makes those changed files reflected to the build?
> Do I need do_cleanall?  do_cleansstate or maybe do_clean is enough?
>
>
> According to the document
>
>
>> do_clean
>> do_unpack task forward (i.e. do_unpack, do_configure, do_compile, do_install, and do_package).
>> if no changes have been made and the recipe is rebuilt after cleaning, output files are simply restored from the sstate cache.
>
>
> I want to avoid doing do_cleanall often, and I would like to tell bitbake that my recipe needs rebuild at the same time not rebuilding others.
> But at the same time I want to avoid building my single explicity.
> I just want to build the image name as target.

I think ccleansstate should be good.

>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20170802/4eec96eb/attachment.html>


More information about the yocto mailing list