[yocto] When to create a new build directory for yocto?

Qiang Yu yuq825 at gmail.com
Mon Dec 1 00:13:08 PST 2014


Hi Chen Qi,

Thank you very much. Your advice is valuable.

Regards,
Qiang

On Mon, Dec 1, 2014 at 3:31 PM, ChenQi <Qi.Chen at windriver.com> wrote:

>  Hi Qiang,
>
> If you are just doing some development, you could use the same build
> directory for almost all builds with just a few exceptions.
> (After all, you could clean up the tmp dir and do a rebuild any time you
> like ...)
>
> But if you are maintaining products, you'd better separate build
> directories.
>
> Regards,
> Chen Qi
>
>
> On 12/01/2014 03:04 PM, Qiang Yu wrote:
>
> What about MACHINE_FEATURES and IMAGE_FEATURES?
>
>
> On Mon, Dec 1, 2014 at 1:28 PM, ChenQi <Qi.Chen at windriver.com> wrote:
>
>>  On 12/01/2014 12:45 PM, Qiang Yu wrote:
>>
>>
>>> It's possible that you are using (or might use) different layer
>>> configurations for different builds.
>>> One build might have a bbappend file that another build doesn't need.
>>>
>> Yes, you are right. I use different conf/bblayers.conf for different SOC.
>> But within the same SOC's different output
>> (board image, SDK), I just change MACHINE and SDKMACHINE. Is it safe to
>> build all outputs of the same SOC
>> in one build dir?
>>
>>
>>  Yes.
>>
>>
>>
>>>  Also, different builds may have different DISTRO_FEATURES.
>>> Thus, having different deploy directories is better. Otherwise, your
>>> package feeds might be broken. And you would suffer trying to maintain it.
>>>
>> You mean I can't build two output with different DISTRO_FEATURES in the
>> same build dir.
>> Any other config var? What about MACHINE and SDKMACHINE?
>>
>>
>>
>>  Yocto doesn't ensure that changing distro features in the same build
>> directory works.
>> It might work, but it's also possible that it doesn't.
>>
>> Changing MACHINE and SDKMACHINE is OK.
>>
>> //Chen Qi
>>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20141201/961c67e3/attachment.html>


More information about the yocto mailing list