<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Jun 5, 2013 at 5:07 PM, Denys Dmytriyenko <span dir="ltr"><<a href="mailto:denis@denix.org" target="_blank">denis@denix.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">On Wed, Jun 05, 2013 at 02:43:07PM -0300, Otavio Salvador wrote:<br>
> On Wed, Jun 5, 2013 at 2:23 PM, Nicolas Dechesne <<br>
> <a href="mailto:nicolas.dechesne@linaro.org">nicolas.dechesne@linaro.org</a>> wrote:<br>
><br>
> ><br>
> ><br>
> ><br>
> > On Wed, Jun 5, 2013 at 7:19 PM, Saul Wold <<a href="mailto:sgw@linux.intel.com">sgw@linux.intel.com</a>> wrote:<br>
> ><br>
> >> On 06/05/2013 10:12 AM, Otavio Salvador wrote:<br>
> >><br>
> >>><br>
> >>><br>
> >>><br>
> >>> On Wed, Jun 5, 2013 at 1:58 PM, Saul Wold <<a href="mailto:sgw@linux.intel.com">sgw@linux.intel.com</a><br>
> >>> <mailto:<a href="mailto:sgw@linux.intel.com">sgw@linux.intel.com</a>>> wrote:<br>
> >>><br>
> >>> On 06/05/2013 09:32 AM, Nicolas Dechesne wrote:<br>
> >>><br>
> >>><br>
> >>> On Wed, Jun 5, 2013 at 6:30 PM, Saul Wold <<a href="mailto:sgw@linux.intel.com">sgw@linux.intel.com</a><br>
> >>> <mailto:<a href="mailto:sgw@linux.intel.com">sgw@linux.intel.com</a>><br>
> >>> <mailto:<a href="mailto:sgw@linux.intel.com">sgw@linux.intel.com</a> <mailto:<a href="mailto:sgw@linux.intel.com">sgw@linux.intel.com</a>>>><br>
> >>> wrote:<br>
> >>><br>
> >>> You could just directly put the nativesdk-libx11 in place<br>
> >>> of the<br>
> >>> variable, no need to have the variable there.<br>
> >>><br>
> >>><br>
> >>> yes, that's what I had initially, but found it was less easy to<br>
> >>> read...<br>
> >>> with X11DEPENDS it's more 'obvious' that there is something<br>
> >>> special..<br>
> >>> that said, i can make the change if that's really needed.<br>
> >>><br>
> >>> We do use the X11DEPENDS elsewhere when there are multiple<br>
> >>> dependencies, but I also found cases where we just include the<br>
> >>> dependency directly in the test. I was trying pick a direction:<br>
> >>> single entry no X11DEPENDS, multiple entries use X11DEPENDS.<br>
> >>><br>
> >>> Comments, flames, ...<br>
> >>><br>
> >>><br>
> >>> Yes; I sent this patch in Febuary:<br>
</div></div>> >>> <a href="http://patchwork.openembedded." target="_blank">http://patchwork.openembedded.</a>**org/patch/44759/<<a href="http://patchwork.openembedded.org/patch/44759/" target="_blank">http://patchwork.openembedded.org/patch/44759/</a>><br>
<div class="im">> >>><br>
> >>> Please use this one instead of the recent one.<br>
> >>><br>
> >>><br>
> >> Well reading back on that, it looks like I was waiting for an<br>
> >> EXTRA_OECONF or related change to the autoconf scripts.<br>
> >><br>
> >> Sau!<br>
> ><br>
> ><br>
> > hmm. ok, sorry Otavio, i missed the other patch. I will check on my side<br>
> > too about EXTRA_OECONF.<br>
> ><br>
><br>
> Nicolas, don't worry. It is normal to end redoing some stuff.<br>
><br>
> Last time I checked it had no support in Qt build system; I am not sure if<br>
> it uses or not the host headers (in case they exist) but it needs testing<br>
> to be sure.<br>
<br>
</div>I can confirm that it does not link against host X11 when built w/o that<br>
dependency and nativesdk has no x11 libs/headers. As I previously mentioned,<br>
we've been using this fix for over 6 months on several releases built on<br>
different machines w/o problems...<br></blockquote><div><br></div><div style>In this case the patch can be merged 'as is'. </div></div><div><br></div>-- <br>Otavio Salvador O.S. Systems<br>
<a href="http://www.ossystems.com.br" target="_blank">http://www.ossystems.com.br</a> <a href="http://projetos.ossystems.com.br" target="_blank">http://projetos.ossystems.com.br</a><br>Mobile: +55 (53) 9981-7854 Mobile: +1 (347) 903-9750<br>
</div></div>