RE: [CMake] cmake 2.4.8 RC 4

[Torsten Martinsen]

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 release for 2.4.8 ready for cmake.  This will be the last
release of the 2.4.X branch.  The next release will be 2.6.0.  So,
please make sure you test it if you are interested in a 2.4.8.  Send any
issues to me or the cmake list.  Thanks.

This e-mail and any files sent with it contain information that may be 
privileged or confidential and is the property of the GateHouse Group. This 
information is intended solely for the person to whom it is addressed. If you 
are not the intended recipient, you are not authorized to read, print, retain, 
copy, disseminate, distribute, or use the message or any part thereof. If you 
have received this e-mail in error, please notify the sender immediately, and 
delete all copies of this message. In accordance with GateHouse Security 
Policy, e-mails sent or received may be monitored.
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake

RE: [CMake] cmake 2.4.8 RC 4

[Torsten Martinsen]

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 had to undo it.  I
> don't think it is stable enough for 2.4.8 which is meant to be a
> minor bug fix on 2.4.7.  I can say that that fix should be in 2.6.

Can you tell me what kind of tests failed? I have a team using the patched 
version, and we have found no problems so far.

-Torsten

This e-mail and any files sent with it contain information that may be 
privileged or confidential and is the property of the GateHouse Group. This 
information is intended solely for the person to whom it is addressed. If you 
are not the intended recipient, you are not authorized to read, print, retain, 
copy, disseminate, distribute, or use the message or any part thereof. If you 
have received this e-mail in error, please notify the sender immediately, and 
delete all copies of this message. In accordance with GateHouse Security 
Policy, e-mails sent or received may be monitored.
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake

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

[Torsten Martinsen]

> * 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. This costs, due to the 
high process overhead on Windows.

-Torsten

This e-mail and any files sent with it contain information that may be 
privileged or confidential and is the property of the GateHouse Group. This 
information is intended solely for the person to whom it is addressed. If you 
are not the intended recipient, you are not authorized to read, print, retain, 
copy, disseminate, distribute, or use the message or any part thereof. If you 
have received this e-mail in error, please notify the sender immediately, and 
delete all copies of this message. In accordance with GateHouse Security 
Policy, e-mails sent or received may be monitored.
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake

RE: [CMake] MSVC turn off RelWithDebInfo and MinSizeRel

[Torsten Martinsen]

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


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of David Cole
Sent: 20 December 2007 01:32
To: Jesse Corrington
Cc: cmake@cmake.org
Subject: Re: [CMake] MSVC turn off RelWithDebInfo and MinSizeRel

SET(CMAKE_CONFIGURATION_TYPES "Debug;Release")

in your CMakeLists.txt. (Or just edit that value in CMakeSetup to change it in 
the cache.)

If you do it with a simple set in the CMakeLists.txt then you will not see that 
reflected in the CMakeSetup GUI, but it will be in effect at generation time 
and you should end up with sln/vcproj files with just the two types.

HTH,
David


On 12/19/07, Jesse Corrington <[EMAIL PROTECTED]> 
wrote:
Is there anyway to have CMake not generate these two configurations, and just 
generate the standard release and debug configurations instead? Thanks.


This e-mail and any files sent with it contain information that may be 
privileged or confidential and is the property of the GateHouse Group. This 
information is intended solely for the person to whom it is addressed. If you 
are not the intended recipient, you are not authorized to read, print, retain, 
copy, disseminate, distribute, or use the message or any part thereof. If you 
have received this e-mail in error, please notify the sender immediately, and 
delete all copies of this message. In accordance with GateHouse Security 
Policy, e-mails sent or received may be monitored.
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake

RE: [CMake] MSVC turn off RelWithDebInfo and MinSizeRel

[Torsten Martinsen]

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.)
> SET(CMAKE_CONFIGURATION_TYPES "Debug;Release" CACHE STRING "limited configs" 
> FORCE)

FWIW, this seems to work for me.

-Torsten

This e-mail and any files sent with it contain information that may be 
privileged or confidential and is the property of the GateHouse Group. This 
information is intended solely for the person to whom it is addressed. If you 
are not the intended recipient, you are not authorized to read, print, retain, 
copy, disseminate, distribute, or use the message or any part thereof. If you 
have received this e-mail in error, please notify the sender immediately, and 
delete all copies of this message. In accordance with GateHouse Security 
Policy, e-mails sent or received may be monitored.
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake

RE: [CMake] MSVC turn off RelWithDebInfo and MinSizeRel

[Torsten Martinsen]

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 RelWithDebInfo and MinSizeRel

The force set seemed to work when running the cmake GUI on windows, but didn't 
seem to work when running the command line cmake.exe, which is the way I need 
to do the generation.

Jesse

On Dec 20, 2007 11:35 PM, Torsten Martinsen <[EMAIL PROTECTED]<mailto:[EMAIL 
PROTECTED]>> wrote:
David Cole <mailto:[EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]>> 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.)
> SET(CMAKE_CONFIGURATION_TYPES "Debug;Release" CACHE STRING "limited configs" 
> FORCE)

FWIW, this seems to work for me.

-Torsten

This e-mail and any files sent with it contain information that may be 
privileged or confidential and is the property of the GateHouse Group. This 
information is intended solely for the person to whom it is addressed. If you 
are not the intended recipient, you are not authorized to read, print, retain, 
copy, disseminate, distribute, or use the message or any part thereof. If you 
have received this e-mail in error, please notify the sender immediately, and 
delete all copies of this message. In accordance with GateHouse Security 
Policy, e-mails sent or received may be monitored.
___
CMake mailing list
CMake@cmake.org<mailto:CMake@cmake.org>
http://www.cmake.org/mailman/listinfo/cmake



This e-mail and any files sent with it contain information that may be 
privileged or confidential and is the property of the GateHouse Group. This 
information is intended solely for the person to whom it is addressed. If you 
are not the intended recipient, you are not authorized to read, print, retain, 
copy, disseminate, distribute, or use the message or any part thereof. If you 
have received this e-mail in error, please notify the sender immediately, and 
delete all copies of this message. In accordance with GateHouse Security 
Policy, e-mails sent or received may be monitored.
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake

[CMake] RE: Adding Custom Build Types

[Torsten Martinsen]

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 in which I need to have custom build types in my project. 
CMake provides the below mentioned build types by default:

Debug
Release
RelWithDebInfo
MinSizeRel

Now In my project I don't want these build types. I want custom build types 
like MD, MT, MDd, MTd, ML etc (for Visual Studio 6 and Visual Studio 8 2005 
both). These build types are required to set the appropriate runtime library. 
Is there any provision in CMake through which this can be achieved?


This e-mail and any files sent with it contain information that may be 
privileged or confidential and is the property of the GateHouse Group. This 
information is intended solely for the person to whom it is addressed. If you 
are not the intended recipient, you are not authorized to read, print, retain, 
copy, disseminate, distribute, or use the message or any part thereof. If you 
have received this e-mail in error, please notify the sender immediately, and 
delete all copies of this message. In accordance with GateHouse Security 
Policy, e-mails sent or received may be monitored.
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake

RE: [CMake] VS makefiles

[Torsten Martinsen]

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 of the GateHouse Group. This 
information is intended solely for the person to whom it is addressed. If you 
are not the intended recipient, you are not authorized to read, print, retain, 
copy, disseminate, distribute, or use the message or any part thereof. If you 
have received this e-mail in error, please notify the sender immediately, and 
delete all copies of this message. In accordance with GateHouse Security 
Policy, e-mails sent or received may be monitored.
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake

[CMake] VC7.1 project files and /TP

[Torsten Martinsen]

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" output, but for "Visual Studio 7
.NET 2003" the C files are always compiled with /TP (and in the project
file, "Compile As" is set to "Compile as C Code (/TC)". Looking at
cmLocalVisualStudio7Generator.cxx, it looks as if this is indeed
hardcoded:

if(strcmp(linkLanguage, "C") == 0)
{
flags += " /TC ";
}
if(strcmp(linkLanguage, "CXX") == 0)
{
flags += " /TP ";
}

I have also tried

SET_SOURCE_FILES_PROPERTIES(
   ${C_SOURCE}
   PROPERTIES COMPILE_FLAGS "-TP")

with the same (lack of) result. Any ideas?

-Torsten

This e-mail and any files sent with it contain information that may be 
privileged or confidential and is the property of the GateHouse Group. This 
information is intended solely for the person to whom it is addressed. If you 
are not the intended recipient, you are not authorized to read, print, retain, 
copy, disseminate, distribute, or use the message or any part thereof. If you 
have received this e-mail in error, please notify the sender immediately, and 
delete all copies of this message. In accordance with GateHouse Security 
Policy, e-mails sent or received may be monitored. 
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake

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

[Torsten Martinsen]

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 any files sent with it contain information that may be 
privileged or confidential and is the property of the GateHouse Group. This 
information is intended solely for the person to whom it is addressed. If you 
are not the intended recipient, you are not authorized to read, print, retain, 
copy, disseminate, distribute, or use the message or any part thereof. If you 
have received this e-mail in error, please notify the sender immediately, and 
delete all copies of this message. In accordance with GateHouse Security 
Policy, e-mails sent or received may be monitored. 
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake

[CMake] Visual Studio solutions

[Torsten Martinsen]

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
that a developer working on that application 
does not have to load the full solution file. Is this possible?
 
-Torsten

This e-mail and any files sent with it contain information that may be 
privileged or confidential and is the property of the GateHouse Group. This 
information is intended solely for the person to whom it is addressed. If you 
are not the intended recipient, you are not authorized to read, print, retain, 
copy, disseminate, distribute, or use the message or any part thereof. If you 
have received this e-mail in error, please notify the sender immediately, and 
delete all copies of this message. In accordance with GateHouse Security 
Policy, e-mails sent or received may be monitored. 
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake

RE: [CMake] Visual Studio solutions

[Torsten Martinsen]

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 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
>> that a developer working on that application
>> does not have to load the full solution file. Is this possible?
>> 
>> 
> Hello,
> 
> As far as i know, CMake generates a global solution AND a solution per
> project (added with ADD_SUBDIRECTORY).

Not for me, it doesn't.

-Torsten

This e-mail and any files sent with it contain information that may be 
privileged or confidential and is the property of the GateHouse Group. This 
information is intended solely for the person to whom it is addressed. If you 
are not the intended recipient, you are not authorized to read, print, retain, 
copy, disseminate, distribute, or use the message or any part thereof. If you 
have received this e-mail in error, please notify the sender immediately, and 
delete all copies of this message. In accordance with GateHouse Security 
Policy, e-mails sent or received may be monitored. 
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake

RE: [CMake] Visual Studio folders

[Torsten Martinsen]

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 the SOURCE_GROUP command.

On a related note, is it possible to use variables as an argument to the
SOURCE_GROUP command? I.e. something like

SOURCE_GROUP("Generated Header Files"
   FILES
   ${UIC_HEADERS}
)

-Torsten

This e-mail and any files sent with it contain information that may be 
privileged or confidential and is the property of the GateHouse Group. This 
information is intended solely for the person to whom it is addressed. If you 
are not the intended recipient, you are not authorized to read, print, retain, 
copy, disseminate, distribute, or use the message or any part thereof. If you 
have received this e-mail in error, please notify the sender immediately, and 
delete all copies of this message. In accordance with GateHouse Security 
Policy, e-mails sent or received may be monitored. 
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake

RE: [CMake] Post Build Custom Copy Command

[Torsten Martinsen]

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_DIR}/lib/release/mylib.dll
${MYLIBRARY_SOURCE_DIR}/bin/release

-Torsten

This e-mail and any files sent with it contain information that may be 
privileged or confidential and is the property of the GateHouse Group. This 
information is intended solely for the person to whom it is addressed. If you 
are not the intended recipient, you are not authorized to read, print, retain, 
copy, disseminate, distribute, or use the message or any part thereof. If you 
have received this e-mail in error, please notify the sender immediately, and 
delete all copies of this message. In accordance with GateHouse Security 
Policy, e-mails sent or received may be monitored. 
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake

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

[Torsten Martinsen]

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 and any files sent with it contain information that may be 
privileged or confidential and is the property of the GateHouse Group. This 
information is intended solely for the person to whom it is addressed. If you 
are not the intended recipient, you are not authorized to read, print, retain, 
copy, disseminate, distribute, or use the message or any part thereof. If you 
have received this e-mail in error, please notify the sender immediately, and 
delete all copies of this message. In accordance with GateHouse Security 
Policy, e-mails sent or received may be monitored. 
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake

RE: [CMake] Visual Studio solutions

[Torsten Martinsen]

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 application, so
> that a developer working on that application
> does not have to load the full solution file. Is this possible?

Well, it turned out that the reason was simply that I did not have a
"PROJECT" statement in each application's CMakeLists.txt (as Brandon
pointed out).

With the PROJECT statement, the desired number of .sln files is
generated - however, the generated dependencies are not correct. Manuel
Klimek let me know that he had implemented a patch to fix this
(http://www.cmake.org/Bug/view.php?id=3218). I have updated the patch
for 2.4.7, and I am now deploying the patched version to my group.

I hope this patch will be included in the next version.

-Torsten

This e-mail and any files sent with it contain information that may be 
privileged or confidential and is the property of the GateHouse Group. This 
information is intended solely for the person to whom it is addressed. If you 
are not the intended recipient, you are not authorized to read, print, retain, 
copy, disseminate, distribute, or use the message or any part thereof. If you 
have received this e-mail in error, please notify the sender immediately, and 
delete all copies of this message. In accordance with GateHouse Security 
Policy, e-mails sent or received may be monitored. 
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake

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

[Torsten Martinsen]

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 in the
> same directory like the derived class (somewhere in my sources - and
> not in the build-directory). 
> 
> In case of the moc-file it is not that important. But it would be
> also nice to have the location under the control of the user. 
> 
> Would there be a possibility to use cmake's "ADD_CUSTOM_COMMAND"? I
> appreciate any help of defining such custom commands for ui and moc
> files. I tried it on my own, but I failed...  

As a reference point, here is the macro I use:

# Run Qt UIC on a UI file.
# Arguments:
#1-N   Names of .ui files
MACRO(AIS_UI)
   FOREACH (it ${ARGN})
  GET_FILENAME_COMPONENT(outfile ${it} NAME_WE)
  SET(outhfile ${CMAKE_CURRENT_BINARY_DIR}/${outfile}.h)
  SET(outcppfile ${CMAKE_CURRENT_BINARY_DIR}/${outfile}_uic.cpp)
  ADD_CUSTOM_COMMAND(OUTPUT ${outhfile}
 COMMAND ${QT_UIC_EXECUTABLE} ARGS -o ${outhfile}
${CMAKE_CURRENT_SOURCE_DIR}/${it}
 WORKING_DIRECTORY ${CMAKE_CURRENT_BINARY_DIR}
 MAIN_DEPENDENCY ${it}
 DEPENDS ${it}
  )
  ADD_CUSTOM_COMMAND(OUTPUT ${outcppfile}
 COMMAND ${QT_UIC_EXECUTABLE} ARGS
${CMAKE_CURRENT_SOURCE_DIR}/${it} -impl ${outhfile} -o ${outcppfile}
 WORKING_DIRECTORY ${CMAKE_CURRENT_BINARY_DIR}
 MAIN_DEPENDENCY ${it}
 DEPENDS ${it} ${outhfile})
SET(CPP_SOURCE ${CPP_SOURCE} ${outcppfile})
  AIS_MOC(${outhfile})

  SET(AIS_UIC_SOURCES ${AIS_UIC_SOURCES} ${outcppfile})
  LIST(APPEND AIS_UIC_HEADERS ${outhfile})
   ENDFOREACH (it)
ENDMACRO(AIS_UI)

Note that this also generates the header file out-of-source - therefore
I have this line in another macro:

   INCLUDE_DIRECTORIES(${CMAKE_CURRENT_BINARY_DIR})

(This macro is used in all my projects).

-Torsten

This e-mail and any files sent with it contain information that may be 
privileged or confidential and is the property of the GateHouse Group. This 
information is intended solely for the person to whom it is addressed. If you 
are not the intended recipient, you are not authorized to read, print, retain, 
copy, disseminate, distribute, or use the message or any part thereof. If you 
have received this e-mail in error, please notify the sender immediately, and 
delete all copies of this message. In accordance with GateHouse Security 
Policy, e-mails sent or received may be monitored. 
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake

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

[Torsten Martinsen]

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 
privileged or confidential and is the property of the GateHouse Group. This 
information is intended solely for the person to whom it is addressed. If you 
are not the intended recipient, you are not authorized to read, print, retain, 
copy, disseminate, distribute, or use the message or any part thereof. If you 
have received this e-mail in error, please notify the sender immediately, and 
delete all copies of this message. In accordance with GateHouse Security 
Policy, e-mails sent or received may be monitored. 
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake

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

[Torsten Martinsen]

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 in my source-directory.

Yes.

-Torsten

This e-mail and any files sent with it contain information that may be 
privileged or confidential and is the property of the GateHouse Group. This 
information is intended solely for the person to whom it is addressed. If you 
are not the intended recipient, you are not authorized to read, print, retain, 
copy, disseminate, distribute, or use the message or any part thereof. If you 
have received this e-mail in error, please notify the sender immediately, and 
delete all copies of this message. In accordance with GateHouse Security 
Policy, e-mails sent or received may be monitored. 
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake

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

[Torsten Martinsen]

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-N   Names of headerfiles
MACRO(AIS_MOC)
   FOREACH (it ${ARGN})
  # Make .h filename absolute
  GET_FILENAME_COMPONENT(infile ${it} ABSOLUTE)

  # Build x_moc.cpp filename
  GET_FILENAME_COMPONENT(outfile ${it} NAME_WE)
  SET(outfile ${CMAKE_CURRENT_BINARY_DIR}/${outfile}_moc.cpp)

  # Run MOC
  ADD_CUSTOM_COMMAND(OUTPUT ${outfile}
 COMMAND ${QT_MOC_EXECUTABLE}
ARGS ${infile} -o ${outfile}
 WORKING_DIRECTORY ${CMAKE_CURRENT_BINARY_DIR}
 DEPENDS ${infile}
 COMMENT MOCing ${it})
  LIST(APPEND CPP_SOURCE ${outfile})
  LIST(APPEND AIS_MOC_SOURCES ${outfile})
   ENDFOREACH(it)
ENDMACRO(AIS_MOC)

This e-mail and any files sent with it contain information that may be 
privileged or confidential and is the property of the GateHouse Group. This 
information is intended solely for the person to whom it is addressed. If you 
are not the intended recipient, you are not authorized to read, print, retain, 
copy, disseminate, distribute, or use the message or any part thereof. If you 
have received this e-mail in error, please notify the sender immediately, and 
delete all copies of this message. In accordance with GateHouse Security 
Policy, e-mails sent or received may be monitored. 
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake

RE: [CMake] Visual Studio reload projects

[Torsten Martinsen]

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 to nmake and a good editor like
> emacs.  You'll be a happier person in the long run.

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.

-Torsten

This e-mail and any files sent with it contain information that may be 
privileged or confidential and is the property of the GateHouse Group. This 
information is intended solely for the person to whom it is addressed. If you 
are not the intended recipient, you are not authorized to read, print, retain, 
copy, disseminate, distribute, or use the message or any part thereof. If you 
have received this e-mail in error, please notify the sender immediately, and 
delete all copies of this message. In accordance with GateHouse Security 
Policy, e-mails sent or received may be monitored. 
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake

RE: [CMake] Visual Studio reload projects

[Torsten Martinsen]

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 if you do a command
> line build? msbuild uses the same mechanism the IDE uses, but
> without the IDE (it's a command line tool). It's basically an
> xml based make-replacement, and you can easily open your
> projects in the IDE if you need to, for example for debugging...

Pardon me if I am wrong, but AFAICT MSBuild uses its own project file
format, and not .vcproj files. This would make it pretty hard to use
with CMake...

Are you perhaps thinking of vcbuild?

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

RE: [CMake] CPack

[Torsten Martinsen]

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:
>> CPack Error: Cannot find a sutable ZIP program <- an I is missing in
>> suitable ;) CPack Error: Cannot initialize the generator
> 
> CMake-2.4.7 wants either WinZip or Info-Zip[1]. Since the latter is
> free, I use that.

What is not immediately obvious is that 2.4.7 *requires* zip.exe to
reside in c:/cygwin/bin.

(Bad luck if you do not have a C: drive).

-Torsten

This e-mail and any files sent with it contain information that may be 
privileged or confidential and is the property of the GateHouse Group. This 
information is intended solely for the person to whom it is addressed. If you 
are not the intended recipient, you are not authorized to read, print, retain, 
copy, disseminate, distribute, or use the message or any part thereof. If you 
have received this e-mail in error, please notify the sender immediately, and 
delete all copies of this message. In accordance with GateHouse Security 
Policy, e-mails sent or received may be monitored. 
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake

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

[Torsten Martinsen]

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
 RUNTIME DESTINATION bin)

This, unfortunately, gives the error

FILE INSTALL cannot find file
"C:/user/gh/ais/impl/build/cmake/vc7/ca/$(OutDir)/ca.pdb" to install.

Note that ${CMAKE_CFG_INTDIR} expands to "$(OutDir)" instead of e.g.
"Debug" as I had hoped.
 
-Torsten

This e-mail and any files sent with it contain information that may be 
privileged or confidential and is the property of the GateHouse Group. This 
information is intended solely for the person to whom it is addressed. If you 
are not the intended recipient, you are not authorized to read, print, retain, 
copy, disseminate, distribute, or use the message or any part thereof. If you 
have received this e-mail in error, please notify the sender immediately, and 
delete all copies of this message. In accordance with GateHouse Security 
Policy, e-mails sent or received may be monitored. 
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake

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

[Torsten Martinsen]

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 files sent with it contain information that may be 
privileged or confidential and is the property of the GateHouse Group. This 
information is intended solely for the person to whom it is addressed. If you 
are not the intended recipient, you are not authorized to read, print, retain, 
copy, disseminate, distribute, or use the message or any part thereof. If you 
have received this e-mail in error, please notify the sender immediately, and 
delete all copies of this message. In accordance with GateHouse Security 
Policy, e-mails sent or received may be monitored. 
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake

RE: [CMake] Macro command

[Torsten Martinsen]

[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 contain information that may be 
privileged or confidential and is the property of the GateHouse Group. This 
information is intended solely for the person to whom it is addressed. If you 
are not the intended recipient, you are not authorized to read, print, retain, 
copy, disseminate, distribute, or use the message or any part thereof. If you 
have received this e-mail in error, please notify the sender immediately, and 
delete all copies of this message. In accordance with GateHouse Security 
Policy, e-mails sent or received may be monitored. 
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake

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

[Torsten Martinsen]

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 this. 

http://www.cmake.org/Wiki/CMake_FAQ#How_can_I_extend_the_build_modes_wit
h_a_custom_made_one_.3F

> Also, does cmake have an idea of platforms, or does it assume Win32?

CMake does not assume anything about Win32 or any other platform.

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

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

[Torsten Martinsen]

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 visual studio environment,
> which would call the make as an external build tool.

I would recommend to set up CMake to generate .vcproj files, and use
those both for the IDE and for command-line builds (using vcbuild.exe or
devenv.exe).

-Torsten

This e-mail and any files sent with it contain information that may be 
privileged or confidential and is the property of the GateHouse Group. This 
information is intended solely for the person to whom it is addressed. If you 
are not the intended recipient, you are not authorized to read, print, retain, 
copy, disseminate, distribute, or use the message or any part thereof. If you 
have received this e-mail in error, please notify the sender immediately, and 
delete all copies of this message. In accordance with GateHouse Security 
Policy, e-mails sent or received may be monitored.
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake

RE: [CMake] Compiling without linking

[Torsten Martinsen]

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 you are trying to do, i.e. why you think that you
need to explicitly split up the steps of compiling and linking.

-Torsten

This e-mail and any files sent with it contain information that may be 
privileged or confidential and is the property of the GateHouse Group. This 
information is intended solely for the person to whom it is addressed. If you 
are not the intended recipient, you are not authorized to read, print, retain, 
copy, disseminate, distribute, or use the message or any part thereof. If you 
have received this e-mail in error, please notify the sender immediately, and 
delete all copies of this message. In accordance with GateHouse Security 
Policy, e-mails sent or received may be monitored.
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake

RE: [CMake] Compiling without linking

[Torsten Martinsen]

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.

-Torsten

This e-mail and any files sent with it contain information that may be 
privileged or confidential and is the property of the GateHouse Group. This 
information is intended solely for the person to whom it is addressed. If you 
are not the intended recipient, you are not authorized to read, print, retain, 
copy, disseminate, distribute, or use the message or any part thereof. If you 
have received this e-mail in error, please notify the sender immediately, and 
delete all copies of this message. In accordance with GateHouse Security 
Policy, e-mails sent or received may be monitored.
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake

[CMake] Running unit test executable

[Torsten Martinsen]

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 simplified and would
not actually compile, but never mind that):

PROJECT(tcsv)

SET(CPP_SOURCE
   tcsvreader.cpp
   tcsvwriter.cpp
   tcsvreadermeta.cpp
)

ADD_EXECUTABLE(tcsv
   ${CPP_SOURCE})

GET_TARGET_PROPERTY(TEST_EXE tcsv LOCATION)

ADD_CUSTOM_COMMAND(
   OUTPUT ${CMAKE_CURRENT_BINARY_DIR}/phony.txt
   COMMAND ${TEST_EXE}
   DEPENDS tcsv)

Given this CMakeLists.txt, I would expect the generated .vcproj file to
have a Post-Build Event that runs tcvs.exe. No such event is generated,
however.

Any pointers?

-Torsten

This e-mail and any files sent with it contain information that may be 
privileged or confidential and is the property of the GateHouse Group. This 
information is intended solely for the person to whom it is addressed. If you 
are not the intended recipient, you are not authorized to read, print, retain, 
copy, disseminate, distribute, or use the message or any part thereof. If you 
have received this e-mail in error, please notify the sender immediately, and 
delete all copies of this message. In accordance with GateHouse Security 
Policy, e-mails sent or received may be monitored.
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake

RE: [CMake] Running unit test executable

[Torsten Martinsen]

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 CMake ignores my ADD_CUSTOM_COMMAND().

-Torsten

This e-mail and any files sent with it contain information that may be 
privileged or confidential and is the property of the GateHouse Group. This 
information is intended solely for the person to whom it is addressed. If you 
are not the intended recipient, you are not authorized to read, print, retain, 
copy, disseminate, distribute, or use the message or any part thereof. If you 
have received this e-mail in error, please notify the sender immediately, and 
delete all copies of this message. In accordance with GateHouse Security 
Policy, e-mails sent or received may be monitored.
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake

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

[Torsten Martinsen]

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/build/cmake/vc7/ca/$(OutDir)/ca.exe", so that is
> also no good.

For future reference, I ended up with this solution:

   # First, build the full name of the EXE.
   INSTALL(CODE "SET(PDB_FULL_PATH
${CMAKE_CURRENT_BINARY_DIR}/\${${project}_BUILD_NAME_\${CMAKE_INSTALL_CO
NFIG_NAME}})")
   # Then, replace .exe with .pdb.
   INSTALL(CODE "STRING(REPLACE .exe .pdb PDB_FULL_PATH
\${PDB_FULL_PATH})")
   # Finally, get it installed.
   INSTALL(CODE "FILE(INSTALL DESTINATION
\"\${CMAKE_INSTALL_PREFIX}/\${CMAKE_INSTALL_CONFIG_NAME}\" TYPE
EXECUTABLE FILES \${PDB_FULL_PATH})")

The trick is to postpone evaluation of the CPack variables until CPack
runs. Not pretty, but it works.

-Torsten

This e-mail and any files sent with it contain information that may be 
privileged or confidential and is the property of the GateHouse Group. This 
information is intended solely for the person to whom it is addressed. If you 
are not the intended recipient, you are not authorized to read, print, retain, 
copy, disseminate, distribute, or use the message or any part thereof. If you 
have received this e-mail in error, please notify the sender immediately, and 
delete all copies of this message. In accordance with GateHouse Security 
Policy, e-mails sent or received may be monitored.
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake

RE: [CMake] Native Pathsupport under Windows

[Torsten Martinsen]

[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 to get backslashes instead of slashes as
> paths?

FILE(TO_NATIVE_PATH ...)

-Torsten

This e-mail and any files sent with it contain information that may be 
privileged or confidential and is the property of the GateHouse Group. This 
information is intended solely for the person to whom it is addressed. If you 
are not the intended recipient, you are not authorized to read, print, retain, 
copy, disseminate, distribute, or use the message or any part thereof. If you 
have received this e-mail in error, please notify the sender immediately, and 
delete all copies of this message. In accordance with GateHouse Security 
Policy, e-mails sent or received may be monitored.
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake

RE: [CMake] Native Pathsupport under Windows

[Torsten Martinsen]

[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+${RESULT}\\test.h ${RESULT}\\image.h
> VERBATIM)

To copy files, use "${CMAKE_COMMAND} -E copy".

-Torsten

This e-mail and any files sent with it contain information that may be 
privileged or confidential and is the property of the GateHouse Group. This 
information is intended solely for the person to whom it is addressed. If you 
are not the intended recipient, you are not authorized to read, print, retain, 
copy, disseminate, distribute, or use the message or any part thereof. If you 
have received this e-mail in error, please notify the sender immediately, and 
delete all copies of this message. In accordance with GateHouse Security 
Policy, e-mails sent or received may be monitored.
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake

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

[Torsten Martinsen]

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 added too.

That, unfortunately,  doesn't happen with vanilla CMake 2.4.7. I have
applied the patch from bug 3218: http://cmake.org/Bug/view.php?id=3218,
and that makes it work for me.

-Torsten

This e-mail and any files sent with it contain information that may be 
privileged or confidential and is the property of the GateHouse Group. This 
information is intended solely for the person to whom it is addressed. If you 
are not the intended recipient, you are not authorized to read, print, retain, 
copy, disseminate, distribute, or use the message or any part thereof. If you 
have received this e-mail in error, please notify the sender immediately, and 
delete all copies of this message. In accordance with GateHouse Security 
Policy, e-mails sent or received may be monitored.
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake

RE: [CMake] disabling the cache

[Torsten Martinsen]

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 reload the project,
and the automatic detection of whether the project file has changed only works
sometimes. I find that an effective workaround is to invoke Alt-F T and then 
Alt-F J Enter :-)

-Torsten

This e-mail and any files sent with it contain information that may be 
privileged or confidential and is the property of the GateHouse Group. This 
information is intended solely for the person to whom it is addressed. If you 
are not the intended recipient, you are not authorized to read, print, retain, 
copy, disseminate, distribute, or use the message or any part thereof. If you 
have received this e-mail in error, please notify the sender immediately, and 
delete all copies of this message. In accordance with GateHouse Security 
Policy, e-mails sent or received may be monitored.
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake

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

[Torsten Martinsen]

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 
TARGET_LINK_LIBRARIES() does not work, and I cannot use CMAKE_BUILD_TYPE at 
configure time.

-Torsten

This e-mail and any files sent with it contain information that may be 
privileged or confidential and is the property of the GateHouse Group. This 
information is intended solely for the person to whom it is addressed. If you 
are not the intended recipient, you are not authorized to read, print, retain, 
copy, disseminate, distribute, or use the message or any part thereof. If you 
have received this e-mail in error, please notify the sender immediately, and 
delete all copies of this message. In accordance with GateHouse Security 
Policy, e-mails sent or received may be monitored.
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake

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

[Torsten Martinsen]

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:
>>
>> /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 TARGET_LINK_LIBRARIES() does not work, and I cannot
>> use CMAKE_BUILD_TYPE at configure time.
>
> #  TARGET_LINK_LIBRARIES: Link a target to given libraries.
>
>   TARGET_LINK_LIBRARIES(target library1
>  library2
> ...)

That's what I tried, but the third-party libraries are located outside my build 
tree, so I need to use absolute paths, which as I said does not work:

It is impossible to order the linker search path in such a way that 
libraries specified as full paths will be picked by the linker.
Directories and libraries involved are:
Directory: c:/lang/Qt/3.3.4/lib contains:
Library: c:\lang\qt\3.3.4r/lib/qtmain.lib

Directory: c:/lang/qt/3.3.4r/lib contains:
Library: C:\lang\Qt\3.3.4/lib/qtmain.lib

-Torsten

This e-mail and any files sent with it contain information that may be 
privileged or confidential and is the property of the GateHouse Group. This 
information is intended solely for the person to whom it is addressed. If you 
are not the intended recipient, you are not authorized to read, print, retain, 
copy, disseminate, distribute, or use the message or any part thereof. If you 
have received this e-mail in error, please notify the sender immediately, and 
delete all copies of this message. In accordance with GateHouse Security 
Policy, e-mails sent or received may be monitored.
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake

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

[Torsten Martinsen]

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.
>
> TARGET_LINK_LIBRARIES(foo release ${qtmain_release})
> TARGET_LINK_LIBRARIES(food debug ${qtmain_debug})
>
> If something like that doesn't work I would file a bug for sure.

No, I cannot, because CMake still tells me

It is impossible to order the linker search path in such a way that 
libraries specified as full paths will be picked by the linker.
Directories and libraries involved are:
Directory: c:/lang/Qt/3.3.4/lib contains:
Library: C:/lang/qt/3.3.4r/lib/qtmain.lib

Directory: c:/lang/qt/3.3.4/lib contains:
Library: C:/lang/qt/3.3.4r/lib/qtmain.lib

Directory: c:/lang/qt/3.3.4r/lib contains:
Library: C:/lang/qt/3.3.4/lib/qtmain.lib

-Torsten

This e-mail and any files sent with it contain information that may be 
privileged or confidential and is the property of the GateHouse Group. This 
information is intended solely for the person to whom it is addressed. If you 
are not the intended recipient, you are not authorized to read, print, retain, 
copy, disseminate, distribute, or use the message or any part thereof. If you 
have received this e-mail in error, please notify the sender immediately, and 
delete all copies of this message. In accordance with GateHouse Security 
Policy, e-mails sent or received may be monitored.
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake

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

[Torsten Martinsen]

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 not solve the problem of how to *use* those variables in 
TARGET_LINK_LIBRARIES()
without getting the 'It is impossible to order the linker search path in such a 
way that libraries
specified as full paths will be picked by the linker' error.

Am I doing something wrong, or is this a bug?

-Torsten

This e-mail and any files sent with it contain information that may be 
privileged or confidential and is the property of the GateHouse Group. This 
information is intended solely for the person to whom it is addressed. If you 
are not the intended recipient, you are not authorized to read, print, retain, 
copy, disseminate, distribute, or use the message or any part thereof. If you 
have received this e-mail in error, please notify the sender immediately, and 
delete all copies of this message. In accordance with GateHouse Security 
Policy, e-mails sent or received may be monitored.
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake

RE: [CMake] cross compiling

[Torsten Martinsen]

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 something?  Does cmake support cross compiling now?


This e-mail and any files sent with it contain information that may be 
privileged or confidential and is the property of the GateHouse Group. This 
information is intended solely for the person to whom it is addressed. If you 
are not the intended recipient, you are not authorized to read, print, retain, 
copy, disseminate, distribute, or use the message or any part thereof. If you 
have received this e-mail in error, please notify the sender immediately, and 
delete all copies of this message. In accordance with GateHouse Security 
Policy, e-mails sent or received may be monitored.
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake