[OE-core] Why python-native is not available via '#!/usr/bin/env python'?

Burton, Ross ross.burton at intel.com
Tue Jul 28 19:52:38 UTC 2015


On 28 July 2015 at 17:23, Kucharczyk, Bartlomiej (Nokia - PL/Wroclaw) <
bartlomiej.kucharczyk at nokia.com> wrote:

> Q1. What are the reasons behind that `/usr/bin/env python` refer to the
> host tool instead the native one?
>

Because the use of the built python-native is opt-in for each recipe, and
if you want to use it then the recipe should just inherit pythonnative.
This adjusts PATH so the standard #! works.

You only need to use the python-native binary if you build-depend on
non-standard Python modules which are in your DEPENDS (and so installed
into the native sysroot).  Otherwise we assume that the host Python is
sufficient: it's running bitbake already so it can't be that broken.

Ross
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openembedded.org/pipermail/openembedded-core/attachments/20150728/5a00c93d/attachment-0002.html>


More information about the Openembedded-core mailing list