RE: [CMake] VS makefiles

Steven Van Ingelgem <> wrote: > Hi, > > > I was wondering why there are no VS makefiles? (run like nmake -f > project.mak). You want the "NMake Makefiles" generator. -Torsten This e-mail and any files sent with it contain information that may be privileged or confidential and is the property o

[CMake] RE: Adding Custom Build Types

Search the mailing list archives. This was discussed some weeks ago. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Malhotra, Anupam Sent: 15 January 2008 06:37 To: cmake@cmake.org Subject: [CMake] Adding Custom Build Types Hi I have a requirement

RE: [CMake] MSVC turn off RelWithDebInfo and MinSizeRel

Actually, I always use the command line. So I haven't tried it from the GUI. From: Jesse Corrington [mailto:[EMAIL PROTECTED] Sent: 21 December 2007 20:06 To: Torsten Martinsen Cc: David Cole; cmake@cmake.org Subject: Re: [CMake] MSVC turn off RelWithDebInf

RE: [CMake] MSVC turn off RelWithDebInfo and MinSizeRel

David Cole wrote: > I will see if I can find / figure out what I did to make this work -- > I know I've done it before to eliminate all but one config type... > > How about this in the CMakeLists.txt file instead? (Force it into the > cache rather than using a simple set

RE: [CMake] MSVC turn off RelWithDebInfo and MinSizeRel

Unfortunately, this does not work. I just tried adding SET(CMAKE_CONFIGURATION_TYPES "Debug;RelWithDebInfo") at the top of my CMakeLists.txt, then deleted my build tree and ran cmake. The generated project files still contain Debug, Release, MinSizeRel and RelWithDebInfo. -Torsten

RE: [CMake] Compilation speed with CMake/NMake combination, making it faster?

> * We're using an NMake build tree, is NMake particularly > slow? Do any of the other makes work more efficiently? Be aware that nmake builds are much slower than using devenv, as nmake starts a cl.exe process for every single file, whereas devenv calls cl.exe with several source files.

RE: [CMake] cmake 2.4.8 RC 4

Bill Hoffman <mailto:[EMAIL PROTECTED]> wrote: > Torsten Martinsen wrote: >> Could we please get the patch for bug 3218 into this release? >> > > I am not sure. The last time I applied that patch or a similar one > lots of tests failed and there was trouble so I ha

RE: [CMake] cmake 2.4.8 RC 4

Could we please get the patch for bug 3218 into this release? -Torsten From: [EMAIL PROTECTED] [EMAIL PROTECTED] On Behalf Of Bill Hoffman [EMAIL PROTECTED] Sent: 05 December 2007 23:13 To: cmake@cmake.org Subject: [CMake] cmake 2.4.8 RC 4 I have a beta r

RE: [CMake] cross compiling

The CVS version does, yes. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Josef Karthauser Sent: 30 November 2007 09:54 To: Jesse Corrington; Salvatore Iovene Cc: cmake@cmake.org; [EMAIL PROTECTED] Subject: RE: [CMake] cross compiling Did I miss so

RE: [CMake] Choosing between debug and release variants of third-party libraries

Bill Hoffman wrote: > The module FindQt4.cmake handles debug and release qtmain already. > See Modules/FindQt4.cmake and Modules/UseQt4.cmake for more > information. Indeed, that module *defines* QT_QTCORE_LIBRARY_RELEASE, QT_QTCORE_LIBRARY_DEBUG, etc. But that does no

RE: [CMake] Choosing between debug and release variants of third-party libraries

Philip Lowman wrote: > So you can't do something like this? > > FIND_LIBRARY(qtmain_release qtmain >PATHS "C:/lang/qt/3.3.4r/lib" NO_DEFAULT_PATH) > FIND_LIBRARY(qtmain_debug qtmain >PATHS "C:/lang/qt/3.3.4/lib" NO_DEFAULT_PATH) > > # declare your targets. >

RE: [CMake] Choosing between debug and release variants of third-party libraries

Philip Lowman <mailto:[EMAIL PROTECTED]> wrote: > Torsten Martinsen wrote: >> I'm sure this is a FAQ, but I cannot find the answer anywhere. >> >> Using VS 2003, given that I have a third-party library with debug >> and release variants: >> >>

[CMake] Choosing between debug and release variants of third-party libraries

I'm sure this is a FAQ, but I cannot find the answer anywhere. Using VS 2003, given that I have a third-party library with debug and release variants: /path/to/lib/release/lib.lib /path/to/lib/debug/lib.lib how do I get CMake to link with the correct variant? Using an absolute path in

RE: [CMake] disabling the cache

Jesper Eskilson <> wrote: > The first problem is that the Visual Studio generator fails to > properly rerun CMake when CMakeLists.txt. It reruns CMake, but the > modified projects files are not reloaded before continuing with the > build. Unfortunately, there is no way of forcing Visual Studio to

RE: [CMake] Adding a project to a solution.

Josef Karthauser <> wrote: >> Each project statement should map to a .sln file that contains any >> necessary .vcproj files. > > I've got that. However, the .sln file doesn't appear to reference the > .vcproj files for objects specified in the target_link_libraries. I > would expect these to get

RE: [CMake] Native Pathsupport under Windows

[EMAIL PROTECTED] <> wrote: >> FILE(TO_NATIVE_PATH ...) > > When I do a FILE(TO_NATIVE_PATH ${CMAKE_CURRENT_BINARY_DIR} RESULT) > and then use ${RESULT} I get the whole again with slashes. > So I can't use that with custom_command: > ADD_CUSTOM_COMMAND(... > COMMAND copy ${RESULT}\\image.h+${RESUL

RE: [CMake] Native Pathsupport under Windows

[EMAIL PROTECTED] <> wrote: > I need to use under windows the buildin commands of the shell. But > when I run these commands they doesn't work correctly, because the > windows commands doen't like the slashes (/). It seems to me that > they want to get backslashes (\). > 1. Is there a possiblity

RE: [CMake] Adding .pdb files to CPack (Visual Studio 7 generator)

Torsten Martinsen <> wrote: > Hendrik Sattler <> wrote: > >> Did you try using the LOCATION property of the TARGET stripping the >> extension and using that? > > Not until now, but: The LOCATION property expands to e.g. > "C:/user/gh/ais/impl/buil

RE: [CMake] Running unit test executable

Torsten Martinsen <> wrote: > I am trying to get CMake to run my CppUnit tests automatically after > building from within Visual Studio .NET 2003. Update: I tried with the latest snapshot (cmake version 2.5-20071009) as well as with the NMake configuration, but it still looks as if C

[CMake] Running unit test executable

I am trying to get CMake to run my CppUnit tests automatically after building from within Visual Studio .NET 2003. Looking at http://www.cmake.org/Wiki/CMake_FAQ#How_do_I_generate_an_executable.2C_t hen_use_the_executable_to_generate_a_file.3F, I thought this would do the trick (the example is sim

RE: [CMake] Compiling without linking

Baptiste Derongs <> wrote: > Actually I have a file that contains a lot of functions, call this > file global.c. > Next I have multiple files, call them f1.c, f2.c, ... > > And each f*.c has to be compiled with global.c. Make a static library containing global.c, then link each application to it.

RE: [CMake] Compiling without linking

Baptiste Derongs <> wrote: > The point is that I want a MakeFile that creates only the .o file, > doesnt try to get binary. Next that same Makefile (and other ones) > need the .o file to make other binaries. Instead of focussing on how to do this small step, you should probably explain what it is

RE: [CMake] Building both make files and visual studio files.

Josef Karthauser <> wrote: > Hello again, > > I'm wondering what the best way to going about producing make files > and visual studio files at the same time is. I want to use nmake to > build my tree, but want visual studio project files so that the > developers can continue to with within the vi

RE: [CMake] Confikgurations and Platforms in Visual Studio 8

Josef Karthauser <> wrote: > I'm looking at cmake as a potential solution to some build problems > I'm having. Am I right in thinking that cmake only allows for four > hard-coded configuration labels, DEBUG/RELEASE/etc? Where should I > look to add to these, as we've got more configurations than

RE: [CMake] Macro command

[EMAIL PROTECTED] <> wrote: > I want to write a macro for a local used command. > > Is it possibly to use CMAKE_CURRENT_BINARY_DIR in the macro? Yes. > Where does it point to? To the current binary directory of the called > CMakeLists.txt Yes. -Torsten This e-mail and any files sent with it

RE: [CMake] Adding .pdb files to CPack (Visual Studio 7 generator)

Hendrik Sattler <> wrote: > Did you try using the LOCATION property of the TARGET stripping the > extension and using that? Not until now, but: The LOCATION property expands to e.g. "C:/user/gh/ais/impl/build/cmake/vc7/ca/$(OutDir)/ca.exe", so that is also no good. -Torsten This e-mail and any

[CMake] Adding .pdb files to CPack (Visual Studio 7 generator)

In a macro, I succesfully use INSTALL( TARGETS ${project} RUNTIME DESTINATION bin) to add my .exe file to the list of files included by CPack. I also want the .pdb file, so I tried INSTALL( FILES ${CMAKE_CURRENT_BINARY_DIR}/${CMAKE_CFG_INTDIR}/${project}.pdb

RE: [CMake] CPack

Hendrik Sattler <> wrote: > Zitat von [EMAIL PROTECTED]: >> I want to use the CPACK generator, but the tutorial >> http://www.cmake.org/Wiki/CMake:Packaging_With_CPack is not quite >> good. Perhaps somebody knows a better site. >> >> When I run make with make package, then I get following error:

RE: [CMake] Visual Studio reload projects

Manuel Klimek <> wrote: > On 8/30/07, Torsten Martinsen <[EMAIL PROTECTED]> wrote: >> I, too, use Emacs. However, do not be oblivious to the fact that an >> nmake build can take around five times longer than an IDE build. > > why do you use nmake and not msbuild

RE: [CMake] Visual Studio reload projects

gga <> wrote: > KSpam wrote: >> I agree that this is a Visual Studio issue; however, I am wondering >> if anyone knows a workaround. I am not a Windows developer, but I >> figured that someone on this list would have found a reasonable >> solution. >> > > Sure. Don't use Visual Studio. Stick

RE: RE: [CMake] Location of ui and moc generated files (qt)

Maik Keller wrote: > Thanks Torsten. I just tested it, and it seems to work with > CMAKE_CURRENT_SOURCE_DIR. Would it be possible to provide me with > your implementation of the AIS_MOC macro as well? Here it is: # Run Qt MOC on a C++ header file. # Arguments: #1

RE: [CMake] Location of ui and moc generated files (qt)

Maik Keller wrote: > Thank you Torsten! > If I would exchange CMAKE_CURRENT_BINARY_DIR for > CMAKE_CURRENT_SOURCE_DIR in your macro and if I would also add > CMAKE_CURRENT_SOURCE_DIR to my include directories, then it should > work the way as I need the generated files i

RE: [CMake] Feature Request: FILE (GLOB files "*.c" EXCEPT main.ctest.c)

Alexandru Ciobanu <> wrote: > Hi, Alex! > > What I understood from you message is that: > set ( src a1.c a2.c ) > add_executable ( cool ${src} ) > *will* detect when a3.c is added. No, it won't. -Torsten This e-mail and any files sent with it contain information that may be privilege

RE: [CMake] Location of ui and moc generated files (qt)

Maik Keller <> wrote: > Hi Alex, > > I prefer to use the class, which is contained in the automatically > generated ui-header file, as a base class for an extended > implementation of the widget. Therefore I have to include the header > of that class. So it would be nice to locate the base class

RE: [CMake] Visual Studio solutions

I wrote: > when I use the "Visual Studio 7 .NET 2003" generator, CMake generates > one .vcproj file for each library/application, > and one .sln file that contains all the .vcproj files, with > appropriate dependencies. So far so good. > > What I would like in addition is a .sln file for each ap

RE: [CMake] Get Windows Registry Key!!!! Doesn't work!!!

Berardino la Torre wrote: > I'm trying to read an installation path from the windows registry: > > SET(FBXSDK_ROOT_PATH > [HKEY_LOCAL_MACHINE\\SOFTWARE\\FBX\\File SDK 2006.11.1;Install_Dir] > CACHE PATH "FBX") Where did you see documented that this is supposed to work? -Torsten This e-mail

RE: [CMake] Post Build Custom Copy Command

Prashanth Udupa wrote: > Since copy does not accept file names of the form D:/SomeFolder/SomOtherFolder/ and only of the form D:\SomeFolder\SomOtherFolder\, > the copy command is failing. How can I make this post build command work? Use COMMAND ${CMAKE_COMMAND} -E copy ${MYLIBRARY_SOURCE_DI

RE: [CMake] Visual Studio solutions

Sylvain Benner <mailto:[EMAIL PROTECTED]> wrote: > Torsten Martinsen a écrit : >> Hi, >> >> when I use the "Visual Studio 7 .NET 2003" generator, CMake generates >> one .vcproj file for each library/application, >> and one .sln file that co

RE: [CMake] Visual Studio folders

On 7/24/07, Brandon Van Every wrote: >> How can I emulate "Add folder" MSVS functionality with CMake? I want to be >> able to add a folder without adding another executable or anything like >> that. > > Are you looking for something that shows up in the MSVS Solution > Explorer? Perhaps you want

[CMake] Visual Studio solutions

Hi, when I use the "Visual Studio 7 .NET 2003" generator, CMake generates one .vcproj file for each library/application, and one .sln file that contains all the .vcproj files, with appropriate dependencies. So far so good. What I would like in addition is a .sln file for each application, so th

RE: [CMake] VC7.1 project files and /TP

Bill Hoffman wrote: > SET_SOURCE_FILES_PROPERTIES( ${C_SOURCE} PROPERTIES LANGUAGE CXX) > > It should work in 2.4.7, but the docs for 2.4.7 have not been updated > to include this, but the code has it. Thanks, that seems to work perfectly. -Torsten This e-mail and an

[CMake] VC7.1 project files and /TP

Hi, I have a library that contains both C++ and C files. For various reasons, the C files must be compiled as C++. In my CMakeLists.txt file I have IF(OPT_DEST_VISUALSTUDIO) ADD_DEFINITIONS(-TP) ENDIF(OPT_DEST_VISUALSTUDIO) This works fine for "NMake Makefiles" outpu