[CMake] FindPythonLibs

[Karl Merkley]

I'm linking an app with the python library and I have a requirement  
to link with the shared library not the static library.  It appears  
that FindPythonLibs has no way of specifying shared vs. static.   The  
shared lib actually is installed in /usr/lib.  The static lib resides  
in /usr/lib/python2.4/config (which is where FindPythonLibs goes  
looking for it).   Any ideas on how to resolve this issue so that  
automatic builds don't have to have a tweak to the CMakeCache.txt?


 Karl


-
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] cmake compile on 64-bit SUSE

[George McConnell]

I was able to get this to compile successfully after pointing to the 32-bit
ncurses-devel kit.

node:/tmp/cmake-2.4.6 # rpm -qa | grep ncurses.*.32*
ncurses-32bit-9-200407011229
ncurses-devel-32bit-9-200407011229

Specifically, after bootstrapping I changed the following line in
CMakeCache.txt:

CURSES_LIBRARY:FILEPATH=/usr/lib64/libncurses.so

to

CURSES_LIBRARY:FILEPATH=/usr/lib/libncurses.so

On 2/20/07, Bill Hoffman <[EMAIL PROTECTED]> wrote:


George McConnell wrote:
> I need cmake to compile a 64-bit application. Can the 32-bit version
> do that?
It should be able to.  You just have to set CXXFLAGS and CFLAGS with 64
bit options or CC and CXX with 64 bit compilers before you run cmake or
ccmake, and it should be fine.  You should not need a 64 bit cmake to
build a 64 bit app.

-Bill


___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Visual Studio and Reloading Projects

[Bill Hoffman]

Bill Napier wrote:
We're currently using CMake to build a very modular project.  We have 
lots of little projects that generate little libraries that end up 
getting linked together into one application.  It's really nice on 
UNIX when you change a CMakeLists.txt, CMake rebuilds everything and 
it just works.
 
We also build the same application under Widnows using Visual Studio 
2005. The Visual Studio Generator does the same thing that UNIX one 
does when a CMakeLists.txt changes: it re-generates all the VS project 
files.  The problem is if you do this while Visual Studio is open, 
you'll get a dialog box prompting you to reload every project in your 
solution.  We have close to 50 projects and this is a lot of reloading.
 
Currently, our process is to close the solution in Visual Studio and 
force CMake to run.  But of course you don't always remember to do 
that... 
 
So my (kind of off-topic) question is: How can I make this process 
less painful?  Does anyone know of any MSVC plugins that will 
auto-reload changed projects?  Or is there a configuration option I'm 
missing somewhere?


This has been a problem with VS from the start.   VS 2003 does the right 
thing once, it will only ask for one reload and then reload all.  But 
after one reload it stops working  VS 2005 went back to prior 
behavior of asking to load every single project.  Basically, if you do a 
CVS update, you should shut down VS and rerun cmake from the 
outside  It would be great if someone knew how to fix this...


-Bill

___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake