On 29 October 2014 13:18, Martin Hundebøll <mar...@hundeboll.net> wrote:
> I used to use a virtualenv to temporarily set Python 2 as the default >> for the shell in which I ran bitbake commands. That was a while ago >> though, all my current builds are running on Ubuntu 12.04/14.04 server >> instances which I access via ssh from my Arch Linux box. >> > > Using a compatible distro-install is of course the easiest way to get > going. Could also work with a virtual machine. Paul meant the Python tool virtualenv, http://virtualenv.readthedocs.org/en/latest/virtualenv.html. This can be used to create an environment where "python" on the search path is python 2, on a system where /usr/bin/ is python 3. I admit that I'm leaning towards thinking that we just say bitbake requires "python" to be 2.7+ and if your host distribution uses python 3 by default, use virtualenv. The logic being added to the V2 series to generate symlinks and drop them into the bitbake source tree isn't very elegant. Obviously using virtualenv means you need to use /usr/bin/env in the shebangs, so that part of the series is still needed. Ross
-- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
