]> code.ossystems Code Review - openembedded-core.git/commit
toolchain-scripts.bbclass:add PYTHONHOME variable to environment-setup
authorHongxu Jia <hongxu.jia@windriver.com>
Mon, 11 Mar 2013 06:10:27 +0000 (14:10 +0800)
committerRoss Burton <ross.burton@intel.com>
Tue, 23 Apr 2013 09:38:44 +0000 (10:38 +0100)
commit15454b99e3cbeaf2e411f1e374b512a19a72995a
tree1a82c5534c066eb88bffa5344f22407e525dc331
parent55c6f1318fe62f7cec37776853cf8bef82a55f89
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.

Cherry-pick commit db0a02492c2a53c1917b753bcf21c4ee7c0ecf59

[YOCTO #3839]

Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com>
meta/classes/toolchain-scripts.bbclass