Quote:
Originally Posted by DiapDealer
Please note that there are cmake instuctions that can be used to specify the exact libpython and python include files you want sigil to link against. These are documented in the BuildingOnLinux document(s) in the docs directory.
|
Yeah, but personally I find the need to specify such location a bug. After all, we're using something really standard here.
Quote:
Originally Posted by DiapDealer
I already modified the FindPythonLibs.cmake file to include the two main multi-arch <GNU arch triplet> locations. It wasn't finding ANY of the distro-installed libpythons prior to that. If we can beef up that cmake file to include even more architectures, I'd be happy to incorporate those changes into the original source--when you're ready to make a pull request.
|
I just let cmake do it's work.
https://anonscm.debian.org/cgit/coll...1c77efab8f1d50
I can only do assumptions on why NO_DEFAULT_PATH was used (=> avoiding linking to system python?).
PS. guess we're OT in this 3d, just redirect me somewhere else if you prefer.