<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 12/01/2014 03:04 PM, Qiang Yu wrote:<br>
</div>
<blockquote
cite="mid:CAKGbVbvV5Hio1xbyEaf1Kk_jOMnGys0Disr66ej9zuO+YY3RFg@mail.gmail.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<div dir="ltr">What about <span
style="font-family:arial,sans-serif;font-size:13px">MACHINE_FEATURES
and IMAGE_FEATURES?</span>
<div><span style="font-family:arial,sans-serif;font-size:13px"><br>
</span></div>
</div>
</blockquote>
<br>
IMAGE_FEATURES is OK.<br>
MACHINE_FEATURES is like DISTRO_FEATURES. Things are not ensured to
work correctly if you change it in the same build directory.<br>
<br>
If I were you, I would jut let builds to share sstate and downloads
and use different build directories for each combination of 'machine
+ distro + feature'.<br>
E.g.<br>
build-qemux86-64-poky-systemd-pam<br>
build-qemux86-64-poky-systemd<br>
build-qemux86-64-poky-sysvinit-pam<br>
....<br>
<br>
This would ensure a clean upgrade path.<br>
<br>
//Chen Qi<br>
<br>
<blockquote
cite="mid:CAKGbVbvV5Hio1xbyEaf1Kk_jOMnGys0Disr66ej9zuO+YY3RFg@mail.gmail.com"
type="cite">
<div class="gmail_extra"><br>
<div class="gmail_quote">On Mon, Dec 1, 2014 at 1:28 PM, ChenQi
<span dir="ltr"><<a moz-do-not-send="true"
href="mailto:Qi.Chen@windriver.com" target="_blank">Qi.Chen@windriver.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"><span class="">
<div>On 12/01/2014 12:45 PM, Qiang Yu wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<blockquote class="gmail_quote"
style="margin:0px 0px 0px
0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<div><br>
It's possible that you are using (or might
use) different layer configurations for
different builds.<br>
One build might have a bbappend file that
another build doesn't need. </div>
</div>
</blockquote>
<div>Yes, you are right. I use different
conf/bblayers.conf for different SOC. But
within the same SOC's different output</div>
<div>(board image, SDK), I just change MACHINE
and SDKMACHINE. Is it safe to build all
outputs of the same SOC</div>
<div>in one build dir?</div>
</div>
</div>
</div>
</blockquote>
<br>
</span> Yes.<span class=""><br>
<br>
<blockquote type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<div>Â </div>
<blockquote class="gmail_quote"
style="margin:0px 0px 0px
0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<div> Also, different builds may have
different DISTRO_FEATURES.<br>
Thus, having different deploy directories
is better. Otherwise, your package feeds
might be broken. And you would suffer
trying to maintain it.<br>
</div>
</div>
</blockquote>
<div>You mean I can't build two output with
different DISTRO_FEATURES in the same build
dir.</div>
<div>Any other config var? What about MACHINE
and SDKMACHINE?</div>
<div>Â </div>
</div>
</div>
</div>
</blockquote>
<br>
</span> Yocto doesn't ensure that changing distro features
in the same build directory works.<br>
It might work, but it's also possible that it doesn't.<br>
<br>
Changing MACHINE and SDKMACHINE is OK.<br>
<br>
//Chen Qi<br>
</div>
</blockquote>
</div>
<br>
</div>
</blockquote>
<br>
</body>
</html>