Re: [CMake] CMake, MKS and VC++

2009/5/7 Philip Lowman > You probably are missing some build flags or libraries in the CMakeLists > that are in the old build system. Try comparing the VC projects generated > by CMake and looking at the compile & link lines vs. your other build > system. You'll inevitably find a difference bet

Re: [CMake] using IMPORTED targets in multiple projects within one CMake tree

Maybe someon from Kitware could comment on this? On Tue, May 5, 2009 at 6:38 PM, wrote: > I saw this too. > IMHO, it's a bug. If it's a feature, I don't see the point. > > I ended defining all my imported targets in the top directory, to be > able to use them wherever I need them. Unfortunately

Re: [CMake] CMake, MKS and VC++

You probably are missing some build flags or libraries in the CMakeLists that are in the old build system. Try comparing the VC projects generated by CMake and looking at the compile & link lines vs. your other build system. You'll inevitably find a difference between the two if you're using the

Re: [CMake] Specify dependency on externally generated shared library

On Wed, May 06, 2009 at 03:53:10PM -0400, Scott Gray wrote: > My problem is that I need to both generate the DLL and declare it as an > imported library so that other programs can depend upon it. I think I'm Maybe I'm missing something, but why do you need to do this? If you are building the li

[CMake] Specify dependency on externally generated shared library

Hello, I've been working for a while to integrate the C/C++ internationalization library ICU with our cmake build process and I've made some pretty good progress, but I'm currently kind of stuck. During part of the ICU bundling process, it takes language resource files (*.res files) and a p

Re: [CMake] foreach() bug?

alexandre.feb...@thomsonreuters.com wrote: foreach(arg ${list}) [snip] The empty element has been discarded by foreach(). Is this the wanted behaviour? If it is, how can I manage empty elements when I need them? The foreach command never even sees the empty arguments. By the time ${list} is

Re: [CMake] CMake & RPM problems

2009/5/6 Florent Lagaye : > Hi, > > Thanks so much, it works now ! I can build an rpm package ! so nice. Nice to ear, I'll will take time to provide a patch in order to make the working change go upstream. > I've got new questions now the I can build the rpm. > >     - How can I embed a freedeskt

Re: [CMake] Qt4 LUpdate and Blanks in the Build Directory Path

Allen Barnett wrote: On Wed, 2009-05-06 at 08:45 -0600, Clinton Stimpson wrote: Clinton Stimpson wrote: Allen Barnett wrote: I (unwisely) created the build directory for a Qt4 project in a path with blanks in the directory names. The QT4_CREATE_TRANSLATION macro in FindQt4.cmake

Re: [CMake] Qt4 LUpdate and Blanks in the Build Directory Path

On Wed, 2009-05-06 at 08:45 -0600, Clinton Stimpson wrote: > Clinton Stimpson wrote: > > Allen Barnett wrote: > >> I (unwisely) created the build directory for a Qt4 project in a path > >> with blanks in the directory names. The QT4_CREATE_TRANSLATION macro in > >> FindQt4.cmake generates a minimal

Re: [CMake] Qt4 LUpdate and Blanks in the Build Directory Path

Clinton Stimpson wrote: Allen Barnett wrote: I (unwisely) created the build directory for a Qt4 project in a path with blanks in the directory names. The QT4_CREATE_TRANSLATION macro in FindQt4.cmake generates a minimal .pro file for the use of lupdate. When the macro writes the _lupdate.pro fil

Re: [CMake] Qt4 LUpdate and Blanks in the Build Directory Path

Allen Barnett wrote: I (unwisely) created the build directory for a Qt4 project in a path with blanks in the directory names. The QT4_CREATE_TRANSLATION macro in FindQt4.cmake generates a minimal .pro file for the use of lupdate. When the macro writes the _lupdate.pro file, it doesn't take into a

[CMake] Qt4 LUpdate and Blanks in the Build Directory Path

I (unwisely) created the build directory for a Qt4 project in a path with blanks in the directory names. The QT4_CREATE_TRANSLATION macro in FindQt4.cmake generates a minimal .pro file for the use of lupdate. When the macro writes the _lupdate.pro file, it doesn't take into account that the source

Re: [CMake] CMake & RPM problems

Hi, Thanks so much, it works now ! I can build an rpm package ! so nice. I've got new questions now the I can build the rpm. - How can I embed a freedesktop file that links to an icon (svg) ? - Where should I put the icon file ? - How can I tell CPack to put instruction to update the i

Re: [CMake] foreach() bug?

Bill, it seems this policy doesn't affect foreach(): macro(test pol) cmake_policy(SET CMP0007 ${pol}) set(list) list(APPEND list A B "" C D) list(LENGTH list len) message("List: ${list} (length=${len})") foreach(arg ${list}) message("List elem: ${arg}") endfore