[cmake-developers] [CMake 0011884]: The target of qt4_add_dbus_interface should automatically depend on its generation.
The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=11884
==
Reported By:Stephen Kelly
Assigned To:
==
Project:CMake
Issue ID: 11884
Category: (No Category)
Reproducibility:have not tried
Severity: minor
Priority: normal
Status: new
==
Date Submitted: 2011-02-21 10:21 EST
Last Modified: 2011-02-21 10:21 EST
==
Summary:The target of qt4_add_dbus_interface should
automatically depend on its generation.
Description:
If you use qt4_generate_dbus_interface() to generate an xml file, you may have a
qt4_add_dbus_interfaces() within the same project to consume the dbus interface.
In that case you must ensure that the xml file is generated before they are
consumed.
You can do that by creating a custom target which encapsulates the dependencies.
macro(my_generate_dbus_interface _header _customName )
qt4_generate_dbus_interface(${_header} ${_customName} ${ARGN} )
add_custom_target(xml_target_${_header} DEPENDS ${_customName})
add_dependencies(dbus_interfaces_xml xml_target_${_header} )
endmacro()
Then use my_generate_dbus_interface instead of qt4_generate_dbus_interface.
However, this should not be necessary. qt4_add_dbus_interfaces could depend on
the xml file existing. Or maybe there's an even better solution.
==
Issue History
Date ModifiedUsername FieldChange
==
2011-02-21 10:21 Stephen Kelly New Issue
==
___
cmake-developers mailing list
cmake-developers@cmake.org
http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
[cmake-developers] [CMake 0011885]: Unclear licensing of Utilities/cmlibarchive/build/windows/{mvcpp, wccpp}.nt
The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=11885
==
Reported By:Modestas Vainius
Assigned To:
==
Project:CMake
Issue ID: 11885
Category: CMake
Reproducibility:always
Severity: major
Priority: high
Status: new
==
Date Submitted: 2011-02-21 15:40 EST
Last Modified: 2011-02-21 15:40 EST
==
Summary:Unclear licensing of
Utilities/cmlibarchive/build/windows/{mvcpp,wccpp}.nt
Description:
Headers of those files state:
#/* FILE: wccpp.nt
# *
# * Copyright (c) 2008
# * TouchNet Information Systems, Inc.
# * All Rights Reserved
# *
# * This program is an unpublished copyright work of TouchNet Information
# * Systems, Inc. of Lenexa, KS. The program, all information disclosed
# * and the matter shown and described hereon or herewith are confidential
# * and proprietary to TouchNet Information Systems, Inc.
# *
# **
# *
# * $LastChangedBy: kientzle $
# * $Locker: $
# * $ProjectName: $
# * $ProjectRevision: $
# * $LastChangedRevision: 29 $
# * $LastChangedDate: 2008-05-05 18:10:33 -0400 (Mon, 05 May 2008) $
# * $State$
# * $RCSfile$
# * $Source$
# *
# * Change Log:
# * $Log: $
# *
# */
So licensing looks really dubious to me (confidential and proprietary, huh?). I
would like to get some clarification.
While Debian packages use external libarchive and these files are MS-Windows
specific anyway, this issue would still require me to clean up (i.e. dfsg) the
upstream tarball before upload to Debian archive. I would really like to avoid
this procedure if possible.
In the long term, it seems wrong that you ship cmake external dependencies
inside the cmake tarball. IMO, it would make sense to ship external dependencies
bundle in its own tarball if you absolutely have to.
The bug was originally reported at https://bugs.debian.org/614390.
==
Issue History
Date ModifiedUsername FieldChange
==
2011-02-21 15:40 Modestas VainiusNew Issue
==
___
cmake-developers mailing list
cmake-developers@cmake.org
http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
Re: [CMake] Cross-compiling: Cmake compiler and ABI check don´t work / TRY_COMPILE and EXECUTABLE_SUFFIX problem
On Mon, Feb 21, 2011 at 2:14 AM, Schmid Alexander a.sch...@de.ccv.eu wrote:
On Friday 18 February 2011, Schmid Alexander wrote:
Hi,
of course, I´d like to have you think further about it, so here you go...
;-)
This is the toolchain file I use.
The specialty about is that I want to use the ARMCC as compiler and an
SDK-provided linker tool for linking.
# this one is important
SET( CMAKE_SYSTEM_NAME Generic )
# this one not so much
SET( CMAKE_SYSTEM_VERSION 1 )
#
---
-- # setup local variables used
#
---
--
SET( SDK1_ROOT $ENV{PROJ_ROOT}\\tools\\Sdk1 )
message( STATUS The SDK1 can be found at ${SDK1_ROOT} )
SET( SDK1_INCLUDE ${SDK1_ROOT}/include )
STRING( REPLACE \\ / SDK1_INCLUDE ${SDK1_INCLUDE} )
SET( SDK1_LIB ${SDK1_ROOT}/lib )
STRING( REPLACE \\ / SDK1_LIB ${SDK1_LIB} )
SET( SDK2_ROOT $ENV{PROJ_ROOT}\\tools\\Sdk2 )
message( STATUS The SDK2 can be found at ${SDK2_ROOT} )
SET( SDK2_INCLUDE ${SDK2_ROOT}/include )
STRING( REPLACE \\ / SDK2_INCLUDE ${SDK2_INCLUDE} )
SET( SDK2_LIB ${SDK2_ROOT}/lib )
STRING( REPLACE \\ / SDK2_LIB ${SDK2_LIB} )
SET( RVCT40_BIN $ENV{RVCT40BIN} )
message( STATUS The ARM Tools can be found at ${RVCT40_BIN} )
Does it work if you replace the all the $ENV{}s with hardcoded paths ?
Please try that and let me know if it works then, so we can figure out a
solution.
Alex
Hi Alex,
replacing doesn´t work.
I also did some further investigation and it led me to a different problem,
that may be the reason for all this.
I think that the TRY_COMPILE macro of Cmake does not respect the
CMAKE_EXECUTABLE_SUFFIX that I have set to .out.
So the TRY_COMPILE does not find the correctly built output file and further
processing fails.
Here´s the output of CMAKE:
-- Check for working CXX compiler:
C:/Programme/ARM/RVCT/Programs/4.0/436/multi1/win_32-pentium/armcc.exe
-- Check for working CXX compiler:
C:/Programme/ARM/RVCT/Programs/4.0/436/multi1/win_32-pentium/armcc.exe --
works
-- Detecting CXX compiler ABI info
CMake Error: Could not COPY_FILE.
OutputFile: ''
copyFile:
'D:/proj/build/test2/CMakeFiles/CMakeDetermineCompilerABI_CXX.bin'
Unable to find executable for try_compile: tried
D:/proj/build/test2/CMakeFiles/CMakeTmp/cmTryCompileExec and D:/proj/build
/test2/CMakeFiles/CMakeTmp/Debug/cmTryCompileExec and
D:/proj/build/test2/CMakeFiles/CMakeTmp/Development/cmTryCompileExec.
-- Suffix is:
-- Output is:
As you can see, I manually added the last to MESSAGEs to the
CmakeDetermineCompilerAbi.cmake that was shipped with Cmake 2.8.3.
When I add the line
SET( CMAKE_EXECUTABLE_SUFFIX .out )
In that file, the ABI check seems to work. So the big question is how to make
Cmake use the CMAKE_EXECUTABLE_SUFFIX that was given in the toolchain file?
Regards,
Alex
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
CMAKE_EXECUTABLE_SUFFIX is not intended to be settable... That's
completely unexpected from the CMake development team's point of view.
I'm not surprised that it doesn't work.
Why do you need to set it?
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Cross-compiling: Cmake compiler and ABI check don´t work / TRY_COMPILE and EXECUTABLE_SUFFIX problem
-Ursprüngliche Nachricht-
Von: David Cole [mailto:david.c...@kitware.com]
Gesendet: Montag, 21. Februar 2011 13:41
An: Schmid Alexander
Cc: a.neundorf-w...@gmx.net; cmake@cmake.org
Betreff: Re: [CMake] Cross-compiling: Cmake compiler and ABI check don´t work
/
TRY_COMPILE and EXECUTABLE_SUFFIX problem
On Mon, Feb 21, 2011 at 2:14 AM, Schmid Alexander a.sch...@de.ccv.eu
wrote:
On Friday 18 February 2011, Schmid Alexander wrote:
Hi,
of course, I´d like to have you think further about it, so here you go...
;-)
This is the toolchain file I use.
The specialty about is that I want to use the ARMCC as compiler and an
SDK-provided linker tool for linking.
# this one is important
SET( CMAKE_SYSTEM_NAME Generic )
# this one not so much
SET( CMAKE_SYSTEM_VERSION 1 )
#
---
-- # setup local variables used
#
---
--
SET( SDK1_ROOT $ENV{PROJ_ROOT}\\tools\\Sdk1 )
message( STATUS The SDK1 can be found at ${SDK1_ROOT} )
SET( SDK1_INCLUDE ${SDK1_ROOT}/include )
STRING( REPLACE \\ / SDK1_INCLUDE ${SDK1_INCLUDE} )
SET( SDK1_LIB ${SDK1_ROOT}/lib )
STRING( REPLACE \\ / SDK1_LIB ${SDK1_LIB} )
SET( SDK2_ROOT $ENV{PROJ_ROOT}\\tools\\Sdk2 )
message( STATUS The SDK2 can be found at ${SDK2_ROOT} )
SET( SDK2_INCLUDE ${SDK2_ROOT}/include )
STRING( REPLACE \\ / SDK2_INCLUDE ${SDK2_INCLUDE} )
SET( SDK2_LIB ${SDK2_ROOT}/lib )
STRING( REPLACE \\ / SDK2_LIB ${SDK2_LIB} )
SET( RVCT40_BIN $ENV{RVCT40BIN} )
message( STATUS The ARM Tools can be found at ${RVCT40_BIN} )
Does it work if you replace the all the $ENV{}s with hardcoded paths ?
Please try that and let me know if it works then, so we can figure out a
solution.
Alex
Hi Alex,
replacing doesn´t work.
I also did some further investigation and it led me to a different problem,
that may
be the reason for all this.
I think that the TRY_COMPILE macro of Cmake does not respect the
CMAKE_EXECUTABLE_SUFFIX that I have set to .out.
So the TRY_COMPILE does not find the correctly built output file and further
processing fails.
Here´s the output of CMAKE:
-- Check for working CXX compiler:
C:/Programme/ARM/RVCT/Programs/4.0/436/multi1/win_32-pentium/armcc.exe
-- Check for working CXX compiler:
C:/Programme/ARM/RVCT/Programs/4.0/436/multi1/win_32-pentium/armcc.exe --
works
-- Detecting CXX compiler ABI info
CMake Error: Could not COPY_FILE.
OutputFile: ''
copyFile:
'D:/proj/build/test2/CMakeFiles/CMakeDetermineCompilerABI_CXX.bin'
Unable to find executable for try_compile: tried
D:/proj/build/test2/CMakeFiles/CMakeTmp/cmTryCompileExec and D:/proj/build
/test2/CMakeFiles/CMakeTmp/Debug/cmTryCompileExec and
D:/proj/build/test2/CMakeFiles/CMakeTmp/Development/cmTryCompileExec.
-- Suffix is:
-- Output is:
As you can see, I manually added the last to MESSAGEs to the
CmakeDetermineCompilerAbi.cmake that was shipped with Cmake 2.8.3.
When I add the line
SET( CMAKE_EXECUTABLE_SUFFIX .out )
In that file, the ABI check seems to work. So the big question is how to
make
Cmake use the CMAKE_EXECUTABLE_SUFFIX that was given in the toolchain
file?
Regards,
Alex
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
CMAKE_EXECUTABLE_SUFFIX is not intended to be settable... That's
completely unexpected from the CMake development team's point of view.
I'm not surprised that it doesn't work.
Why do you need to set it?
Hi David,
thanks for participating!
I did some tests and from my point of view you are right - I do not have to set
it at all.
But, nevertheless, the problem stays.
The crosscompiling toolchain produces binary files with .out suffix, and for me
it seems that the the TRY_COMPILE macro does not recognize this file as the
result of the building step.
Can you please give me some help what I can do to get it working?
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
[CMake] Setting global make variable from CMake,
Hi All, Could somebody help me how to provide own predefined make varibable from cmake configuration? Such a variable should be avaliable in the context of all generated makefiles. I would like to receive output in a way: in master Makefile: export MY_OWN_DEBUG_VAR=3 MY_OWN_DEBUG_VAR should be predefined inside cmake, of passed to cmake via -DMY_OWN_DEBUG_VAR=3 passing throu make macro is not a sollution. Thanks a lot for help Lukasz -- Lukasz Tasz ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
[CMake] EXTERNALPROJECT_ADD and AlwaysCreate
Dear All, I'm trying to use the ExternalProject functionality. I'm under Microsoft Windows 7 and using Microsoft Visual Studio 2010 with CMake 2.8.4. It's a simple test, trying to compile some classes that need ITK, so I have an: EXTERNALPROJECT_ADD( ITK-ext GIT_REPOSITORY http://itk.org/ITK.git; GIT_TAG v3.20.0 CMAKE_ARGS -DBUILD_SHARED_LIBS:BOOL=ON -DBUILD_TESTING:BOOL=OFF -DBUILD_EXAMPLES:BOOL=OFF -DITK_USE_OPTIMIZED_REGISTRATION_METHODS:BOOL=ON -DITK_USE_REVIEW:BOOL=ON INSTALL_COMMAND UPDATE_COMMAND ) My problem is that it works fine the first time (download and compile ITK and my project). But every time after, when I build, it tries to download ITK again, which I do not want (only the first time is enough). The output of visual studio is: 1-- Build started: Project: ITK-ext, Configuration: Debug x64 -- 1Build started 21/02/2011 14:31:54. 1InitializeBuildStatus: 1 Creating x64\Debug\ITK-ext\ITK-ext.unsuccessfulbuild because AlwaysCreate was specified. 1CustomBuild: 1 Creating directories for 'ITK-ext' 1 Performing download step (git clone) for 'ITK-ext' ... I thought that the UPDATE_COMMAND would solve this but it does not. Can I deactivate this AlwaysCreate? Thanks, Yves ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Setting global make variable from CMake,
2011/2/21 Łukasz Tasz luk...@tasz.eu: Hi All, Could somebody help me how to provide own predefined make varibable from cmake configuration? Such a variable should be avaliable in the context of all generated makefiles. Since the makefiles are generated by CMake WHY do you need to define a make var? What do you want to do ? CMake was not designed to let you decide generator specifics things. I would like to receive output in a way: in master Makefile: export MY_OWN_DEBUG_VAR=3 MY_OWN_DEBUG_VAR should be predefined inside cmake, of passed to cmake via -DMY_OWN_DEBUG_VAR=3 passing throu make macro is not a sollution. What is your use case? -- Erk Membre de l'April - « promouvoir et défendre le logiciel libre » - http://www.april.org ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Setting global make variable from CMake,
2011/2/21 Eric Noulard eric.noul...@gmail.com: Since the makefiles are generated by CMake WHY do you need to define a make var? What do you want to do ? CMake was not designed to let you decide generator specifics things. That's cool, I really like it, and in most cases it works fine e.g CMAKE_VERBOSE_MAKE, Developer can modifiy GCC flags etc. What is your use case? In my case I'm making integration with ccache, and distcc, and as you know all of them are tuned only via ENV_VARS. Depending on CMAKE_BUILD_TYPE, compiler version, OS I would like to prepare correct DISTCC_HOSTS variable etc. That is why in my mind setting global make variable is a solution, at least my brain wouled generate such a makefile:) Another solution that poped up in my mind is to register this variable before calling compiler/linker, Do you know such a call can be configured? for example: export MYVARIABVLE=test; cd dir; compiler_call Thanks a lot for help -- Lukasz Tasz ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Installing cmake-2.8.4-Darwin-universal.dmg
On Sun, 20 Feb 2011 09:43:10 +1100, Andrew Maclean said: I am attempting to install this on Snow Leopard. The installation seems to work Ok but fails at the Install Command Line Tools stage, with the message: Failed create symlink installation may be incomplete: /usr/bin/ccmake ... and so forth for all the command line tools. Clearly this is a permissions issue. The installer actually does ask for my password and the gui seems to be successfully installed in the Apps folder, so I suspect sudo rights are not being propagated to the symlink creation stage. This has failed for as long as I can remember. It might be this: http://public.kitware.com/Bug/view.php?id=10938 So how do I get the Command Lines stuff installed? (Aside from manually creating them.) What I do is add /Applications/CMake.app/Contents/bin to my PATH. If you do this, you'll also need to remember to rename the installed CMake every time (to remove the version number): http://public.kitware.com/Bug/view.php?id=11693 -- Sean McBride, B. Eng s...@rogue-research.com Rogue Researchwww.rogue-research.com Mac Software Developer Montréal, Québec, Canada ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Setting global make variable from CMake,
2011/2/21 Łukasz Tasz luk...@tasz.eu: 2011/2/21 Eric Noulard eric.noul...@gmail.com: What is your use case? In my case I'm making integration with ccache, and distcc, and as you know all of them are tuned only via ENV_VARS. Depending on CMAKE_BUILD_TYPE, compiler version, OS I would like to prepare correct DISTCC_HOSTS variable etc. Ok I see. That is why in my mind setting global make variable is a solution, at least my brain wouled generate such a makefile:) Another solution that poped up in my mind is to register this variable before calling compiler/linker, Do you know such a call can be configured? for example: export MYVARIABVLE=test; cd dir; compiler_call I don't think there is an easy way to do that from within CMake. You would need some way to set env var before launching the compile rule the only way I see would be to craft a compile script for each case. -- Erk Membre de l'April - « promouvoir et défendre le logiciel libre » - http://www.april.org ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Setting global make variable from CMake,
On 02/21/2011 04:35 PM, Eric Noulard wrote: 2011/2/21 Łukasz Tasz luk...@tasz.eu: 2011/2/21 Eric Noulard eric.noul...@gmail.com: What is your use case? In my case I'm making integration with ccache, and distcc, and as you know all of them are tuned only via ENV_VARS. Depending on CMAKE_BUILD_TYPE, compiler version, OS I would like to prepare correct DISTCC_HOSTS variable etc. Ok I see. That is why in my mind setting global make variable is a solution, at least my brain wouled generate such a makefile:) Another solution that poped up in my mind is to register this variable before calling compiler/linker, Do you know such a call can be configured? for example: export MYVARIABVLE=test; cd dir; compiler_call I don't think there is an easy way to do that from within CMake. You would need some way to set env var before launching the compile rule the only way I see would be to craft a compile script for each case. You could experiment with the RULE_LAUNCH_COMPILE and RULE_LAUNCH_LINK properties... However, that would only work for Makefile-based generators. Michael ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Setting global make variable from CMake,
2011/2/21 Michael Wild them...@gmail.com: Do you know such a call can be configured? for example: export MYVARIABVLE=test; cd dir; compiler_call I don't think there is an easy way to do that from within CMake. You would need some way to set env var before launching the compile rule the only way I see would be to craft a compile script for each case. You could experiment with the RULE_LAUNCH_COMPILE and RULE_LAUNCH_LINK properties... However, that would only work for Makefile-based generators. I didn't even know those properties existed :-] Thank you Michael. -- Erk Membre de l'April - « promouvoir et défendre le logiciel libre » - http://www.april.org ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Solution folders
David Cole skrev 2011-02-20 17:55: Those properties were first introduced in v2.8.3, that's why it didn't do anything for 2.8.2... Now next fun stuff. Since not everybody use VS2008 Pro (the express version doesn't support solution folders :( ) I need to make this an option: OPTION(BUILD_USE_SOLUTION_FOLDERS Enable grouping of projects in VS OFF) SET_PROPERTY(GLOBAL PROPERTY USE_FOLDERS BUILD_USE_SOLUTION_FOLDERS) But this doesn't work!! Whatever I set BUILD_USE_SOLUTION_FOLDERS to, ON or OFF, no solution folders are generated, period!! WTF !? /Rob ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Solution folders
Use:
SET_PROPERTY(GLOBAL PROPERTY USE_FOLDERS ${BUILD_USE_SOLUTION_FOLDERS})
On Mon, Feb 21, 2011 at 11:20 AM, Robert Bielik
robert.bie...@xponaut.se wrote:
David Cole skrev 2011-02-20 17:55:
Those properties were first introduced in v2.8.3, that's why it didn't
do anything for 2.8.2...
Now next fun stuff. Since not everybody use VS2008 Pro (the express version
doesn't support solution folders :( ) I need to make this
an option:
OPTION(BUILD_USE_SOLUTION_FOLDERS Enable grouping of projects in VS OFF)
SET_PROPERTY(GLOBAL PROPERTY USE_FOLDERS BUILD_USE_SOLUTION_FOLDERS)
But this doesn't work!! Whatever I set BUILD_USE_SOLUTION_FOLDERS to, ON or
OFF, no solution folders are generated, period!! WTF !?
/Rob
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Solution folders
Robert Bielik skrev 2011-02-21 17:20: Now next fun stuff. Since not everybody use VS2008 Pro (the express version doesn't support solution folders :( ) I need to make this an option: OPTION(BUILD_USE_SOLUTION_FOLDERS Enable grouping of projects in VS OFF) SET_PROPERTY(GLOBAL PROPERTY USE_FOLDERS BUILD_USE_SOLUTION_FOLDERS) But this doesn't work!! Whatever I set BUILD_USE_SOLUTION_FOLDERS to, ON or OFF, no solution folders are generated, period!! WTF !? Was a bit fast there, hasn't been my day today... this works: OPTION(BUILD_USE_SOLUTION_FOLDERS Enable grouping of projects in VS OFF) IF(BUILD_USE_SOLUTION_FOLDERS) SET_PROPERTY(GLOBAL PROPERTY USE_FOLDERS ON) ELSEIF(BUILD_USE_SOLUTION_FOLDERS) SET_PROPERTY(GLOBAL PROPERTY USE_FOLDERS OFF) ENDIF(BUILD_USE_SOLUTION_FOLDERS) /Rob ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Solution folders
David Cole skrev 2011-02-21 17:28:
SET_PROPERTY(GLOBAL PROPERTY USE_FOLDERS ${BUILD_USE_SOLUTION_FOLDERS})
ARGH! Of course. Thank you.
/Rob
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Gyp VS CMake
On Mon, Feb 21, 2011 at 1:29 AM, Jesper Eskilson jesper.eskil...@iar.comwrote: On 02/19/2011 06:27 PM, Michael Wild wrote: On 02/19/2011 06:16 PM, Jed Brown wrote: On Fri, Feb 18, 2011 at 17:16, Michael Wildthem...@gmail.com wrote: Well, cl.exe for one doesn't do this trick. This means, you'll have to put it in your build system, and once you've done that, why should you use the compiler then? Especially, since you'll want to be consistent across platforms. You can use LD_PRELOAD (DLL injection on Windows) to pick up the dependencies. That has the advantage of automatically working for any compiler or other custom command, for any source language. Tup does this. Tup was already discussed on this list quite some time ago. Using LD_PRELOAD to do those things makes my skin crawl. You need to intercept system calls AND C-library functions and have to hope that the compiler isn't doing some crazy stuff you haven't considered... LD_PRELOAD isn't that bad of a hack, actually. Intercepting open(), read(), and possibly mmap() should cover most cases. So cl.exe /showincludes doesn't work? According to this, it is available. http://www.conifersystems.com/2008/10/09/dependencies-from-showincludes/ ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] 2.8.4 order of tests
One more detail, this seems to be a problem only on non windows (non-make) - windows VS machines ran the tests in correct declaration order. Allen Bug reported: http://public.kitware.com/Bug/view.php?id=11877 On Fri, Feb 18, 2011 at 10:30 AM, David Cole david.c...@kitware.com wrote: Yup. ctest -N and ctest without -N differ in test ordering. Congratulations! You've reported the first regression bug in CMake 2.8.4! :-) I suspect the change for this bug [ http://public.kitware.com/Bug/view.php?id=11561 ] has introduced this issue. I'll make a new issue that we can hopefully address fairly soon. Thanks, David ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Gyp VS CMake
On 2/21/2011 12:16 PM, j s wrote: LD_PRELOAD isn't that bad of a hack, actually. Intercepting open(), read(), and possibly mmap() should cover most cases. So cl.exe /showincludes doesn't work? According to this, it is available. http://www.conifersystems.com/2008/10/09/dependencies-from-showincludes/ Although slower that what we have. I did write a depend system once that used cl.exe. It basically ran the cpp over the code (cl -E) , and grepped out all the #line information. It has the advantage of not using an system tricks, and all of the compilers we support can be made to print out #line numbers with a cpp output. We don't have any free cycles to work on this at Kitware right now. -Bill ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] 2.8.4 order of tests
This should be fixed already in CMake's 'next' branch. If you can try a nightly installer, or build yourself from 'next', let me know if there is still any problem. Fix will be in 2.8.5 when it comes out in a few months. Thanks, David On Mon, Feb 21, 2011 at 12:39 PM, Allen D Byrne b...@hdfgroup.org wrote: One more detail, this seems to be a problem only on non windows (non-make) - windows VS machines ran the tests in correct declaration order. Allen Bug reported: http://public.kitware.com/Bug/view.php?id=11877 On Fri, Feb 18, 2011 at 10:30 AM, David Cole david.c...@kitware.com wrote: Yup. ctest -N and ctest without -N differ in test ordering. Congratulations! You've reported the first regression bug in CMake 2.8.4! :-) I suspect the change for this bug [ http://public.kitware.com/Bug/view.php?id=11561 ] has introduced this issue. I'll make a new issue that we can hopefully address fairly soon. Thanks, David ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
[CMake] Fortran good and bad
First off, I just upgraded to cmake 2.8.4 (from 2.8.2) and the visual studio + intel fortran support is much much better. Thank you whoever fixed it up. Projects generate correctly and build out of the box (Intel Fortran 10.x + visual studio 2008) - previously I had to generate nmake makefiles first and then switch to visual studio once the fortran compiler was detected. Thanks to the success of the above, I tried to generate a project using the visual studio 2010 generator and intel fortran composer 11.something. It failed with the attached output. Something simple I expect. Can anyone see what's gone wrong from the following == Determining if the Fortran compiler works failed with the following output: Change Dir: D:/cmakebuild/super3/CMakeFiles/CMakeTmp Run Build Command:C:\Windows\Microsoft.NET\Framework\v4.0.30319\MSBuild.exe cmTryCompileExec.vcxproj /p:Configuration=Debug Microsoft (R) Build Engine Version 4.0.30319.1 [Microsoft .NET Framework, Version 4.0.30319.1] Copyright (C) Microsoft Corporation 2007. All rights reserved. Build started 21/02/2011 20:26:17. Project D:\cmakebuild\super3\CMakeFiles\CMakeTmp\cmTryCompileExec.vcxproj on node 1 (default targets). InitializeBuildStatus: Creating cmTryCompileExec.dir\Debug\cmTryCompileExec.unsuccessfulbuild because AlwaysCreate was specified. ManifestResourceCompile: C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\bin\rc.exe /nologo /focmTryCompileExec.dir\Debug\cmTryCompileExec.exe.embed.manifest.res cmTryCompileExec.dir\Debug\cmTryCompileExec_manifest.rc Link: C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\bin\x86_amd64\link.exe /ERRORREPORT:QUEUE /OUT:D:\cmakebuild\super3\CMakeFiles\CMakeTmp\Debug\cmTryCompileExec.exe /VERSION:0.0 /INCREMENTAL /NOLOGO /MANIFEST /ManifestFile:cmTryCompileExec.dir\Debug\cmTryCompileExec.exe.intermediate.manifest /MANIFESTUAC:level='asInvoker' uiAccess='false' /PDB:D:\cmakebuild\super3\CMakeFiles\CMakeTmp\Debug\cmTryCompileExec.pdb /SUBSYSTEM:CONSOLE /TLBID:1 /DYNAMICBASE /NXCOMPAT /IMPLIB:D:/cmakebuild/super3/CMakeFiles/CMakeTmp/Debug/cmTryCompileExec.lib /MACHINE:X64 cmTryCompileExec.dir\Debug\cmTryCompileExec.exe.embed.manifest.res LINK : error LNK2001: unresolved external symbol mainCRTStartup [D:\cmakebuild\super3\CMakeFiles\CMakeTmp\cmTryCompileExec.vcxproj] D:\cmakebuild\super3\CMakeFiles\CMakeTmp\Debug\cmTryCompileExec.exe : fatal error LNK1120: 1 unresolved externals [D:\cmakebuild\super3\CMakeFiles\CMakeTmp\cmTryCompileExec.vcxproj] Done Building Project D:\cmakebuild\super3\CMakeFiles\CMakeTmp\cmTryCompileExec.vcxproj (default targets) -- FAILED. Build FAILED. D:\cmakebuild\super3\CMakeFiles\CMakeTmp\cmTryCompileExec.vcxproj (default target) (1) - (Link target) - LINK : error LNK2001: unresolved external symbol mainCRTStartup [D:\cmakebuild\super3\CMakeFiles\CMakeTmp\cmTryCompileExec.vcxproj] D:\cmakebuild\super3\CMakeFiles\CMakeTmp\Debug\cmTryCompileExec.exe : fatal error LNK1120: 1 unresolved externals [D:\cmakebuild\super3\CMakeFiles\CMakeTmp\cmTryCompileExec.vcxproj] 0 Warning(s) 2 Error(s) Time Elapsed 00:00:00.39 ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Cross-compiling: Cmake compiler and ABI check don´t work / TRY_COMPILE and EXECUTABLE_SUFFIX problem
On Monday 21 February 2011, Schmid Alexander wrote:
...
I did some tests and from my point of view you are right - I do not have to
set it at all. But, nevertheless, the problem stays.
The crosscompiling toolchain produces binary files with .out suffix, and
for me it seems that the the TRY_COMPILE macro does not recognize this file
as the result of the building step. Can you please give me some help what I
can do to get it working?
This suffix should be set by the platform file.
Modules/CMakeSystemSpecificInformation.cmake includes
CMakeGenericSystem.cmake, which sets it to . That's what you see.
Then it includes Platform/${CMAKE_SYSTEM_NAME}, which is
Platform/Generic.cmake. This file does not change the suffix, so it stays
empty for you.
If you need a different suffix, you probably have to come up with a name for
your platform and provide a platform file for it, which sets the name.
Alex
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Installing cmake-2.8.4-Darwin-universal.dmg
Hi Sean, Thanks for the link, After reading the link below, I think I will write a little script to delete the symlinks and see if the install works, if not then I will write another script to create them. Alternatively after reading your second paragraph it may be better to rename the installation to /Applications/CMake.app and manually create the symlinks. The for future installations all I would need to do is to do the installation but DO NOT create the symlinks then rename the installation to CMake.app. I generally don't keep side by side versions of CMake. With respect to PATH, I have noticed that in some cases the PATH is ignored in Macs but /usr/local/bin is not, hence the need for symlinks. Thanks for the help. Andrew On Tue, Feb 22, 2011 at 2:25 AM, Sean McBride s...@rogue-research.comwrote: On Sun, 20 Feb 2011 09:43:10 +1100, Andrew Maclean said: I am attempting to install this on Snow Leopard. The installation seems to work Ok but fails at the Install Command Line Tools stage, with the message: Failed create symlink installation may be incomplete: /usr/bin/ccmake ... and so forth for all the command line tools. Clearly this is a permissions issue. The installer actually does ask for my password and the gui seems to be successfully installed in the Apps folder, so I suspect sudo rights are not being propagated to the symlink creation stage. This has failed for as long as I can remember. It might be this: http://public.kitware.com/Bug/view.php?id=10938 So how do I get the Command Lines stuff installed? (Aside from manually creating them.) What I do is add /Applications/CMake.app/Contents/bin to my PATH. If you do this, you'll also need to remember to rename the installed CMake every time (to remove the version number): http://public.kitware.com/Bug/view.php?id=11693 -- Sean McBride, B. Eng s...@rogue-research.com Rogue Researchwww.rogue-research.com Mac Software Developer Montréal, Québec, Canada -- ___ Andrew J. P. Maclean Australian Centre for Field Robotics (ACFR) The Rose Street Building J04 The University of Sydney 2006 NSW AUSTRALIA Ph: +61 2 9351 3283 Fax: +61 2 9351 7474 URL: http://www.acfr.usyd.edu.au/ ___ ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Installing cmake-2.8.4-Darwin-universal.dmg
There was a bug where we were discussing keeping or ditching the version number that gets appended to the CMake.app package. There are good reasons both to keep it and to remove it. You may want to add your thoughts to the bug. http://public.kitware.com/Bug/view.php?id=11693 ___ Mike Jackson www.bluequartz.net Principal Software Engineer mike.jack...@bluequartz.net BlueQuartz Software Dayton, Ohio On Feb 21, 2011, at 5:02 PM, Andrew Maclean wrote: Hi Sean, Thanks for the link, After reading the link below, I think I will write a little script to delete the symlinks and see if the install works, if not then I will write another script to create them. Alternatively after reading your second paragraph it may be better to rename the installation to /Applications/CMake.app and manually create the symlinks. The for future installations all I would need to do is to do the installation but DO NOT create the symlinks then rename the installation to CMake.app. I generally don't keep side by side versions of CMake. With respect to PATH, I have noticed that in some cases the PATH is ignored in Macs but /usr/local/bin is not, hence the need for symlinks. Thanks for the help. Andrew On Tue, Feb 22, 2011 at 2:25 AM, Sean McBride s...@rogue-research.com wrote: On Sun, 20 Feb 2011 09:43:10 +1100, Andrew Maclean said: I am attempting to install this on Snow Leopard. The installation seems to work Ok but fails at the Install Command Line Tools stage, with the message: Failed create symlink installation may be incomplete: /usr/bin/ccmake ... and so forth for all the command line tools. Clearly this is a permissions issue. The installer actually does ask for my password and the gui seems to be successfully installed in the Apps folder, so I suspect sudo rights are not being propagated to the symlink creation stage. This has failed for as long as I can remember. It might be this: http://public.kitware.com/Bug/view.php?id=10938 So how do I get the Command Lines stuff installed? (Aside from manually creating them.) What I do is add /Applications/CMake.app/Contents/bin to my PATH. If you do this, you'll also need to remember to rename the installed CMake every time (to remove the version number): http://public.kitware.com/Bug/view.php?id=11693 -- Sean McBride, B. Eng s...@rogue-research.com Rogue Researchwww.rogue-research.com Mac Software Developer Montréal, Québec, Canada -- ___ Andrew J. P. Maclean Australian Centre for Field Robotics (ACFR) The Rose Street Building J04 The University of Sydney 2006 NSW AUSTRALIA Ph: +61 2 9351 3283 Fax: +61 2 9351 7474 URL: http://www.acfr.usyd.edu.au/ ___ ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Fortran good and bad
On 2/21/2011 2:33 PM, Biddiscombe, John A. wrote: First off, I just upgraded to cmake 2.8.4 (from 2.8.2) and the visual studio + intel fortran support is much much better. Thank you whoever fixed it up. Projects generate correctly and build out of the box (Intel Fortran 10.x + visual studio 2008) - previously I had to generate nmake makefiles first and then switch to visual studio once the fortran compiler was detected. Thanks to the success of the above, I tried to generate a project using the visual studio 2010 generator and intel fortran composer 11.something. It failed with the attached output. Something simple I expect. Can anyone see what's gone wrong from the following Kitware has not had the funding or access to a Fortran compiler that works with VS 2010. So, that has not yet been implemented. -Bill ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Fortran good and bad
BIll, Kitware has not had the funding or access to a Fortran compiler that works with VS 2010. So, that has not yet been implemented. I've got two projects that are using fortran heavily, so I may have a go at fixing up the generator. If I were to spend a few days improving the fortran support for VS2010 - which classes should I concentrate on? (It's been a while since I looked at the cmake source, so I can't quite remember how it all fits together, should I be looking at cmVisualStudio10TargetGenerator, or cmGlobalVisualStudio10Generator/cmGlobalVisualStudio10Win64Generator or one of the base classes?) Thanks in advance for any pointers JB ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
[Cmake-commits] CMake branch, next, updated. v2.8.4-938-ga1fb47d
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project CMake. The branch, next has been updated via a1fb47d8d7ed0bdb40ed3e4f878bb888d54869be (commit) via 1ca15f85f10704b382d5459f88d57839b7462c55 (commit) via dff3d7da3fecac13de1d7893afa79007a4fc052a (commit) from b9395a9c812522e3a4e20e496622e95c018bd7fb (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log - http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=a1fb47d8d7ed0bdb40ed3e4f878bb888d54869be commit a1fb47d8d7ed0bdb40ed3e4f878bb888d54869be Merge: b9395a9 1ca15f8 Author: Brad King brad.k...@kitware.com AuthorDate: Mon Feb 21 10:44:23 2011 -0500 Commit: Brad King brad.k...@kitware.com CommitDate: Mon Feb 21 10:44:23 2011 -0500 Merge branch 'master' into next --- Summary of changes: Source/kwsys/kwsysDateStamp.cmake |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) hooks/post-receive -- CMake ___ Cmake-commits mailing list Cmake-commits@cmake.org http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-commits
[Cmake-commits] CMake branch, next, updated. v2.8.4-940-g64919dd
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, next has been updated
via 64919dd12d9e1ace9d6da059e3b9d92c891770c7 (commit)
via 6a61a8a5383fe7418cdd893c97328a27b86b08da (commit)
from a1fb47d8d7ed0bdb40ed3e4f878bb888d54869be (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=64919dd12d9e1ace9d6da059e3b9d92c891770c7
commit 64919dd12d9e1ace9d6da059e3b9d92c891770c7
Merge: a1fb47d 6a61a8a
Author: Brad King brad.k...@kitware.com
AuthorDate: Mon Feb 21 14:50:54 2011 -0500
Commit: CMake Topic Stage kwro...@kitware.com
CommitDate: Mon Feb 21 14:50:54 2011 -0500
Merge topic 'mingw-module-definition' into next
6a61a8a Honor module .def files with MinGW tools (#9997)
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=6a61a8a5383fe7418cdd893c97328a27b86b08da
commit 6a61a8a5383fe7418cdd893c97328a27b86b08da
Author: Brad King brad.k...@kitware.com
AuthorDate: Mon Feb 21 13:30:10 2011 -0500
Commit: Brad King brad.k...@kitware.com
CommitDate: Mon Feb 21 14:34:54 2011 -0500
Honor module .def files with MinGW tools (#9997)
Since commit 024d05ad (Fix use of module .def files for MS tools,
2009-09-29) module .def files work for any platform that sets
CMAKE_LINK_DEF_FILE_FLAG correctly. Set it in the Windows-GNU platform
information file to enable support with MinGW tools. Also enable the
test added by commit 0db2c850 (Test use of module .def files for MS
tools, 2009-09-29) for MinGW and MSYS generators.
diff --git a/Modules/Platform/Windows-GNU.cmake
b/Modules/Platform/Windows-GNU.cmake
index 7084b83..8df0bcb 100644
--- a/Modules/Platform/Windows-GNU.cmake
+++ b/Modules/Platform/Windows-GNU.cmake
@@ -43,6 +43,7 @@ endif()
set(CMAKE_DL_LIBS )
set(CMAKE_LIBRARY_PATH_FLAG -L)
set(CMAKE_LINK_LIBRARY_FLAG -l)
+set(CMAKE_LINK_DEF_FILE_FLAG -Wl,)
set(CMAKE_LINK_LIBRARY_SUFFIX )
set(CMAKE_CREATE_WIN32_EXE -mwindows)
diff --git a/Tests/CMakeLists.txt b/Tests/CMakeLists.txt
index 2c11919..5dc35ba 100644
--- a/Tests/CMakeLists.txt
+++ b/Tests/CMakeLists.txt
@@ -1082,8 +1082,11 @@ ${CMake_BINARY_DIR}/bin/cmake -DVERSION=master -P
${CMake_SOURCE_DIR}/Utilities/
IF(CMAKE_TEST_MSVC)
ADD_TEST_MACRO(ForceInclude foo)
ADD_TEST_MACRO(PrecompiledHeader foo)
+ ENDIF()
+ IF(CMAKE_TEST_MSVC OR
+ ${CMAKE_TEST_GENERATOR} MATCHES (MSYS|MinGW) Makefiles)
ADD_TEST_MACRO(ModuleDefinition example_exe)
- ENDIF(CMAKE_TEST_MSVC)
+ ENDIF()
ADD_TEST_MACRO(CheckCompilerRelatedVariables CheckCompilerRelatedVariables)
---
Summary of changes:
Modules/Platform/Windows-GNU.cmake |1 +
Tests/CMakeLists.txt |5 -
2 files changed, 5 insertions(+), 1 deletions(-)
hooks/post-receive
--
CMake
___
Cmake-commits mailing list
Cmake-commits@cmake.org
http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-commits
[Cmake-commits] CMake branch, master, updated. v2.8.4-8-g73bbef3
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project CMake. The branch, master has been updated via 73bbef36d03cce70c7a3c29845d545afc67d81b8 (commit) from 1ca15f85f10704b382d5459f88d57839b7462c55 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log - http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=73bbef36d03cce70c7a3c29845d545afc67d81b8 commit 73bbef36d03cce70c7a3c29845d545afc67d81b8 Author: KWSys Robot kwro...@kitware.com AuthorDate: Tue Feb 22 00:01:04 2011 -0500 Commit: KWSys Robot kwro...@kitware.com CommitDate: Tue Feb 22 00:10:58 2011 -0500 KWSys Nightly Date Stamp diff --git a/Source/kwsys/kwsysDateStamp.cmake b/Source/kwsys/kwsysDateStamp.cmake index 6392180..8d4ad8b 100644 --- a/Source/kwsys/kwsysDateStamp.cmake +++ b/Source/kwsys/kwsysDateStamp.cmake @@ -18,4 +18,4 @@ SET(KWSYS_DATE_STAMP_YEAR 2011) SET(KWSYS_DATE_STAMP_MONTH 02) # KWSys version date day component. Format is DD. -SET(KWSYS_DATE_STAMP_DAY 21) +SET(KWSYS_DATE_STAMP_DAY 22) --- Summary of changes: Source/kwsys/kwsysDateStamp.cmake |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) hooks/post-receive -- CMake ___ Cmake-commits mailing list Cmake-commits@cmake.org http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-commits
