From: Orcan O. <oge...@gm...> - 2012-07-08 06:31:45
|
On Fri, Jul 6, 2012 at 5:36 PM, wrote: > On Fri, 6 Jul 2012, Orcan Ogetbil wrote: >> >> Then we should search for Python.h I guess. > > I agree, searching for Python.h should work in all cases (at least on > Linux, I have no idea on OS X or Windows). > >> Or maybe there is already a proper python detection script around for >> cmake that we can utilize. >> This sounds like a common issue. > > I actually thought of that too and did a web search for it earlier, but > couldn't find anything that looked right to me, but then that might be > because of my lack of experience with cmake. > I found that there is a standard Cmake module /usr/share/cmake/Modules/FindPythonLibs.cmake that comes with my cmake installation. A little search revealed that this script has been around for a while (I saw a record as early as 2005), so I switched to using this module instead of pkgconfig. Please try out. > > P.S: with regards to your Fedora package: > Does your Fedora Muse binary actually find the Muse libs (the ones in > %{_libdir}/muse-%{version}/modules/) at runtime? > Yes that's the idea. > I had to add '-DCMAKE_SKIP_RPATH=0' as cmake parameter in the %build > section as the %{cmake} macro on Centos disables RPATHs and therefore > the Muse binary isn't be able to find it's libs at runtime. > Hmm, insteresting. We also provide a cmake option to build muse as a single large binary, hence eliminating the need for rpath. This is enabled by passing -DMODULES_BUILD_STATIC=1 to cmake. It used to work just as good. I didn't test it lately though. Cheers, Orcan |