<div dir="ltr">I see that sourcing the SDK environment file (<i>environment-setup-armv7ahf-neon-oe-linux-gnueabi</i>) results in a few QT variables pointing to the machine that generated the SDK (generated through populate_sdk).<div><br></div><div>Towards the end of my environment file I have this line:</div><blockquote style="margin:0px 0px 0px 40px;border:none;padding:0px"><div><br></div><div>if [ -d "$OECORE_NATIVE_SYSROOT/environment-setup.d" ]; then</div><div>  for envfile in $OECORE_NATIVE_SYSROOT/environment-setup.d/*.sh; do</div><div>      . $envfile</div><div>  done</div><div>fi</div></blockquote><div><br></div>The 'environment-setup.d' directory contains '<span class="gmail-il">qt5</span>.sh', which ultimately relies on STAGING_LIBDIR to resolve. These are the variables:<div><br></div><blockquote style="margin:0px 0px 0px 40px;border:none;padding:0px"><div>OE_QMAKE_INCDIR_QT</div><div>QMAKESPEC</div><div>OE_QMAKE_QT_CONFIG</div><div>OE_QMAKE_LIBDIR_QT</div><div><br></div></blockquote>I don't know if this is a mistake on my part or a bug in <span class="gmail-il">meta</span>-<span class="gmail-il">qt5</span>. It may even be harmless, but I am still surprised to find my build host paths in the SDK I am distributing across the team.<div><br></div><div>Can someone please explain what might be going on?</div><div><br></div><div>Much regards,</div><div><br></div><div>Adam</div></div>