]> code.ossystems Code Review - openembedded-core.git/commit
toolchain-scripts.bbclass: add PYTHONHOME variable to environment-setup
authorLaurentiu Palcu <laurentiu.palcu@intel.com>
Tue, 19 Feb 2013 14:15:03 +0000 (16:15 +0200)
committerRichard Purdie <richard.purdie@linuxfoundation.org>
Tue, 19 Feb 2013 22:37:40 +0000 (14:37 -0800)
commite7a21cd69a326ab7e2d0e410db28f24956f61208
treee4a20387f0f68b443f764d7e505e2c2c5620f4cb
parentbb7a913e4a0da450cc85edfe0d8f80bdf4065fad
toolchain-scripts.bbclass: add PYTHONHOME variable to environment-setup

When relocating the SDK, applications using python will search for
python modules in the default location and will fail to start.
The below errors are thrown by gdb, for example:

Could not find platform independent libraries <prefix>
Could not find platform dependent libraries <exec_prefix>
Consider setting $PYTHONHOME to <prefix>[:<exec_prefix>]
ImportError: No module named site

In order to overcome this, add the PYTHONHOME variable to the
environment-setup script for both standalone toolchain and
adt-installer. No need to do that for meta-ide-support environment
script since this toolchain does not get relocated.

[YOCTO #3839]

Signed-off-by: Laurentiu Palcu <laurentiu.palcu@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
meta/classes/toolchain-scripts.bbclass