Re: [CMake] Visual Studio and Windows Mobile SDKs

Hello, Thank you for the review. I will not be able to apply the changes this month. Right now other things are important for our project. Maybe someone else has time to improve the files. I expect that our project schedule will force us to support wince at the end of august. Some time before that

Re: [CMake] CMake support for Python

Nicholas, We are using this for GDCM: http://gdcm.svn.sourceforge.net/viewvc/gdcm/trunk/CMake/UsePythonTest.cmake?view=markup HTH -Mathieu On Tue, Jul 8, 2008 at 3:17 PM, Nicholas Yue <[EMAIL PROTECTED]> wrote: > Hi, > > I'd like to build and run Python unit test using CMake. > > In the key

Re: [CMake] An example of DEFINE_SYMBOL please

On Monday 07 July 2008 19:59:24 Mehdi Rabah wrote: > Hi, > > I need to set multiple symbols in one of my target of my project. I can't > use add_definitions because I don't want to define those variable for all > my targets, so I tried custom properties. > > set_target_properties( target PROPERTI

Re: [CMake] Building Mac kext from CMake

Hi Sean, Sean McBride wrote: > On 7/9/08 5:06 PM, Tim Schooley said: > >> I have a kernel extension that I would like to build from CMake >> in order to include it in CPack. > > You are very likely the first to try that, and I'd be surprised if it > went smoothly. IIRC, building kexts requires

Re: [CMake] Rpath removed from installed libraries?

O/H Alexander Neundorf ??: On Wednesday 09 July 2008, Georgios Petasis wrote: O/H Alexander Neundorf ??: ... Which dirs are that exactly ? Are they all outside the build dir ? Alex Two are in the build dir, but one is the perl library, in /usr/lib/perl5/

Re: [CMake] Building Mac kext from CMake

Hi Alan, Alan W. Irwin wrote: > On 2008-07-09 12:28-0400 Sean McBride wrote: > >> On 7/9/08 5:06 PM, Tim Schooley said: >> >>> I have a kernel extension that I would like to build from CMake >>> in order to include it in CPack. >> >> You are very likely the first to try that, and I'd be surprised

[CMake] Valgrind arguments

Hey guys, how can i pass valgrind during the MEMCHECK argument ? I need to run valgrind with --trace-children=yes and I can't figure out how to do it. Thanks for any help Milan ___ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/list

Re: [CMake] Valgrind arguments

Milan Dorak wrote: Hey guys, Hi, how can i pass valgrind during the MEMCHECK argument ? I need to run valgrind with --trace-children=yes and I can't figure out how to do it. according to the source code there are 3 variables CTEST_MEMORYCHECK_COMMAND CTEST_MEMORYCHECK_SUPPRESSIONS_FILE C

Re: [CMake] Valgrind arguments

Andreas Schneider wrote: Milan Dorak wrote: Hey guys, Hi, how can i pass valgrind during the MEMCHECK argument ? I need to run valgrind with --trace-children=yes and I can't figure out how to do it. according to the source code there are 3 variables CTEST_MEMORYCHECK_COMMAND CTEST_MEMOR

Re: [CMake] Valgrind arguments

Andreas Schneider wrote: Andreas Schneider wrote: Milan Dorak wrote: Hey guys, Hi, how can i pass valgrind during the MEMCHECK argument ? I need to run valgrind with --trace-children=yes and I can't figure out how to do it. according to the source code there are 3 variables CTEST_MEMOR

Re: [CMake] CMake support for Python

You are missing the enable_testing() + include(CTest) thingy Ref: http://www.cmake.org/Wiki/CMake_Testing_With_CTest HTH -Mathieu On Thu, Jul 10, 2008 at 3:14 PM, Nicholas Yue <[EMAIL PROTECTED]> wrote: > Hi Mathieu, > > Are you able to elaborate on the steps? > > I have a python project which

[CMake] MSVC Qt Integration

I'm trying to get Qt integration to work in visual studio using cmake to generate the project and solution files. So far I've gotten part of the puzzle together using set_target_properties as described in the documentation to set the VS_KEYWORD. There is another piece though, in the solution file

[CMake] MSI Support

Out of curiousity, since MSVC is supported, why no MSI CPack support? -Tom ___ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] MSI Support

On Thu, Jul 10, 2008 at 11:49 AM, Thomas Burdick <[EMAIL PROTECTED]> wrote: > Out of curiousity, since MSVC is supported, why no MSI CPack support? CPack's installers for Windows are built with the NullSoft Installation System, which makes it far simpler to develop installers than to work with MSI

[CMake] FindQt

Hi, it would be great if FindQt (resp. FindQt4) would support a user file extension for QT4_WRAP_UI, e.h. hpp for the ui header. *.hpp is a common C++ header extension as I use it for my code. Thanks, Olaf ___ CMake mailing list CMake@cmake.org http://w

Re: [CMake] Check if a target has been added

Thank you Alexander, the LOCATION solution worked like a charm. Cheers, Félix C. Morency ___ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] MSVC Qt Integration

Is it not possible for Trolltech to make their Qt integration work with project files that they didn't generate? Last time I tried, it seemed more things didn't work than I would have expected. Clint On Thursday 10 July 2008 9:48:43 am Thomas Burdick wrote: > I'm trying to get Qt integration

[CMake] Can I change the extension of a dll?

Hi all, I am trying to compile a python module with cmake. Unfortunately, in python 2.5.2 they have decided that C modules will use the extension .pyd, instead of .dll under windows. So, I have to somehow rename a dll during installation. I currenlty have code like: INSTALL ( TARGETS ${Python

Re: [CMake] Best Practice to determine what type of libraries I am linking to

You are correct that you can't simply test the HDF5_LIBRARIES variables since in windows a .lib is used for both static and shared linking. Since you can get access to this information from a header file you could do a try compile and look at the output, or you could read the contents of the file

Re: [CMake] Can I change the extension of a dll?

This is what I use for my own expat library: #- Use MSVC Naming conventions for Shared Libraries IF (MINGW AND BUILD_SHARED_LIBS) SET_TARGET_PROPERTIES( expat PROPERTIES IMPORT_SUFFIX ".lib" IMPORT_PREFIX "" PREFIX "" ) ENDIF (MINGW AND BUILD_SHARED_LIB

Re: [CMake] Best Practice to determine what type of libraries I am linking to

Funny, that is what I ended up doing with all my support libraries. I create a #define in the configured header and then I do a try-compile to look for the symbol. If the symbol is there then I know it is a dynamic library. For those interested (or for comments) here is the CMake code that