View Single Post
Old 12-20-2015, 11:22 AM   #4
eschwartz
Ex-Helpdesk Junkie
eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.
 
eschwartz's Avatar
 
Posts: 19,421
Karma: 85400180
Join Date: Nov 2012
Location: The Beaten Path, USA, Roundworld, This Side of Infinity
Device: Kindle Touch fw5.3.7 (Wifi only)
Then try passing -DPKG_SYSTEM_PYTHON=1 to cmake, and setting all the environment variables to the right locations in src/Resource_Files/python_pkg/python_paths.py

I imagine at some point the makeinstaller logic will be further fleshed out, i.e. it should be attempting to find the location of things using pkg-config cmake find_packages() if not explicitly specified.
But it might work as of now, too.

...

checkinstall does not stop you from needing to install dependencies last I checked... so I really don't see what benefit checkinstall has over an actual *.deb built from the official Debian packaging sources.

Last edited by eschwartz; 12-20-2015 at 02:48 PM.
eschwartz is offline   Reply With Quote