<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Tue, Apr 14, 2015 at 2:19 PM, Rifenbark, Scott M <span dir="ltr"><<a href="mailto:scott.m.rifenbark@intel.com" target="_blank">scott.m.rifenbark@intel.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Ed,<br>
<br>
This worked for me.... Thanks.<br>
<span class="HOEnZb"><font color="#888888"><br>
Scott<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
>-----Original Message-----<br>
>From: Ed Bartosh [mailto:<a href="mailto:ed.bartosh@linux.intel.com">ed.bartosh@linux.intel.com</a>]<br>
>Sent: Tuesday, April 14, 2015 1:46 PM<br>
>To: <a href="mailto:bitbake-devel@lists.openembedded.org">bitbake-devel@lists.openembedded.org</a><br>
>Cc: Rifenbark, Scott M; Ed Bartosh<br>
>Subject: [PATCH] Allow environment variables and ~ in bbconf paths<br>
><br>
>This should allow to use ~, $HOME and other environment variables in bbconf<br>
>paths.<br>
><br>
>Signed-off-by: Ed Bartosh <<a href="mailto:ed.bartosh@linux.intel.com">ed.bartosh@linux.intel.com</a>><br></div></div></blockquote><div><br></div><div>We already have a mechanism by which environment variables flow into the metadata. Is there something wrong with using BB_ENV_EXTRAWHITE to use ${HOME} in this context?</div></div>-- <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>