<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Mar 25, 2015 at 12:28 PM, Mark Asselstine <span dir="ltr"><<a href="mailto:mark.asselstine@windriver.com" target="_blank">mark.asselstine@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 id=":bi" class="a3s" style="overflow:hidden">My first attempt I had tried "libdir" and it doesn't seem to have the needed<br>
effect. I was hesitant to use other variables (such as those that libdir is<br>
derived from) as that would fork how -native and target builds would be<br>
handled. I had found other instances (meta/classes/package.bbclass) that<br>
seemed to use vardeps on expanded variables. At any rate I will circle back,<br>
your comment was not entirely unexpected, just the push that is needed for me<br>
to look more closely. I will follow up in a bit.<br></div></blockquote><div><br></div><div>package.bbclass has variables containing / functions returning lists of variable names. libdir isn't a list of variable names, it's a path.</div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div id=":bi" class="a3s" style="overflow:hidden"><span class="">
> Second, if libdir is used in do_configure, then changing<br>
> it will already cause do_configure to be re-run, as bitbake tracks variable<br>
> references. Only references which can't be tracked by bitbake need to be<br>
> listed explicitly.<br>
<br>
</span>The observed behavior definitely supports the view that this is a case where<br>
it can't be tracked. It is definitely a different usage than you would find<br>
normally.<br>
<br>
do_configure () {<br>
...<br>
perl ./Configure ${EXTRA_OECONF} shared --prefix=$useprefix \<br>
--openssldir=${libdir}/ssl --libdir=`basename ${libdir}` $target<br>
}</div></blockquote></div><br><br>Nope, this is exactly what bitbake knows how to track, a standard variable reference; ${libdir}. It knows that do_configure uses libdir already. It's only when the variable name is determined programmatically at runtime in python that bitbake isn't able to track the reference (e.g. d.getVar(foo + "bar", True)).<br>-- <br><div class="gmail_signature">Christopher Larson<br>clarson at kergoth dot com<br>Founder - BitBake, OpenEmbedded, OpenZaurus<br>Maintainer - Tslib<br>Senior Software Engineer, Mentor Graphics</div>
</div></div>