<div dir="ltr">I agree, there are a ton of build dir and project management tools, without information about the use cases satisfied and why it's superior to alternatives, much less why you think it belongs in oe-core as opposed to all the other tools folks use, which would imply tactit approval as the official method, particularly going into scripts instead of contrib, I doubt this is going anywhere.<br></div><br><div class="gmail_quote"><div dir="ltr">On Mon, May 21, 2018 at 12:04 PM Alexander Kanavin <<a href="mailto:alexander.kanavin@linux.intel.com">alexander.kanavin@linux.intel.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 05/21/2018 06:55 PM, Jens Rehsack wrote:<br>
> Move scripts/bashrc from meta-jens/scripts to oe-core to share user-friendly<br>
> oe builddir management with community. Using this script will help manage<br>
> multiple BSPs and targets like perl developers using perlbrew.<br>
<br>
Please explain in detail what this does, and why is it superior to <br>
existing tools. What are the typical usage scenarios? Where and how this <br>
should be documented and tested? It is not a good idea to just add <br>
something into scripts/, as no one will know or use it, and so it will <br>
just quietly bitrot.<br>
<br>
> +__oe_check_py () {<br>
> + # Make sure we're not using python v3.x. This check can't go into<br>
> + # sanity.bbclass because bitbake's source code doesn't even pass<br>
> + # parsing stage when used with python v3, so we catch it here so we<br>
> + # can offer a meaningful error message.<br>
> + py_v3_check=`/usr/bin/env python --version 2>&1 | grep "Python 3"`<br>
> + if [ "$py_v3_check" != "" ]; then<br>
> + echo >&2 "Bitbake is not compatible with python v3"<br>
> + echo >&2 "Please set up python v2 as your default python interpreter"<br>
> + return 1<br>
> + fi<br>
<br>
Bitbake has in fact been compatible with Python 3.x for several <br>
releases. The above check is not particularly useful, as /usr/bin/python <br>
nearly always points to a 2.x version.<br>
<br>
Alex<br>
-- <br>
_______________________________________________<br>
Openembedded-core mailing list<br>
<a href="mailto:Openembedded-core@lists.openembedded.org" target="_blank">Openembedded-core@lists.openembedded.org</a><br>
<a href="http://lists.openembedded.org/mailman/listinfo/openembedded-core" rel="noreferrer" target="_blank">http://lists.openembedded.org/mailman/listinfo/openembedded-core</a><br>
</blockquote></div><br clear="all"><br>-- <br><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr">Christopher Larson<br>kergoth at gmail dot com<br>Founder - BitBake, OpenEmbedded, OpenZaurus<br>Senior Software Engineer, Mentor Graphics</div></div></div></div>