diff options
| author | Piotr Tworek <tworaz@tworaz.net> | 2019-07-27 10:56:16 +0200 |
|---|---|---|
| committer | Khem Raj <raj.khem@gmail.com> | 2019-07-28 17:11:17 -0700 |
| commit | e5ac325b7974a346b218d1f43b92d06f5b0dd078 (patch) | |
| tree | ebb2cad8f429a9d0d652c1069375e2fc7221b2c4 /meta-python/recipes-devtools/python/python-anyjson.inc | |
| parent | 2bdd4a599558c93385642b17b27d5cce31911dd6 (diff) | |
| download | meta-openembedded-e5ac325b7974a346b218d1f43b92d06f5b0dd078.tar.gz | |
itstool: Don't use hardcoded, absolute path to python3 binary.
Unfortunately itstoll build system produces script file which contains
absolute path to python3 binary used during packaging. In case of OE
this refers to recipe-sysroot-native directory. This obviously make the
resulting script unusable for both target and native builds. This
problem was patched in OE using sed after the script file was installed.
The sed line replaced one absolute path with /usr/bin/python3. This
seems to work fine for target builds but is still not good enough for
native targets.s
The main problem with native builds is we can't mix host and OE provided
python3 when recipe using the tool inherits python3native bbclass. This
bbclass exports _PYTHON_SYSCONFIGDATA_NAME="_sysconfigdata" which is
likely to break host python3.
To make sure itstool is usable on both build host and target replace
/usr/bin/python3 absolute path with /usr/bin/env python3.
Signed-off-by: Piotr Tworek <tworaz@tworaz.net>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Diffstat (limited to 'meta-python/recipes-devtools/python/python-anyjson.inc')
0 files changed, 0 insertions, 0 deletions