View Single Post
Old 02-19-2016, 03:41 PM   #37
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,676
Karma: 205039118
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
If you installed any python packages after that initial cmake command, you may need to delete your build directory before running the cmake command again.

Mint 17.2 with the system python 3.4.3 is the exact same system I build on.

Quote:
Originally Posted by patrik View Post
Ah, I pointed to /usr/lib/python3.4 instead of /usr/lib/python3.4m.
That's still not a valid library file. If you must specify the library with -DPYTHON_LIBRARY, the correct file will start with "lib" and end in a ".so" extension. On My Mint 17.2 system the python library path would be -DPYTHON_LIBRARY= /usr/lib/x86_64-linux-gnu/libpython34m.so. But you really shouldn't need to specify it manually.

Last edited by DiapDealer; 02-19-2016 at 03:53 PM.
DiapDealer is offline   Reply With Quote