View Single Post
Old 12-20-2015, 01:42 PM   #5
DiapDealer
Grand Sorcerer
DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.
 
DiapDealer's Avatar
 
Posts: 28,674
Karma: 205039118
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
Quote:
Originally Posted by eschwartz View Post
Then try passing -DPKG_SYSTEM_PYTHON to cmake, and setting all the environment variables to the right locations in src/Resource_Files/python_pkg/python_paths.py
Has to be -DPKG_SYSTEM_PYTHON=1

There's no need to set any of the variables in python_paths.py as env vars. Those variables get filled when cmake configures it. Many are provided already by the existing cmake build process. The few that might be needed to build the standalone installer can be provided as -D options in the initial cmake command (if cmake can't locate them on its own).

It builds for me with little effort.
The plan IS to flesh it out and make it build for everybody, but that may be a while.

Last edited by DiapDealer; 12-20-2015 at 01:51 PM.
DiapDealer is offline   Reply With Quote