RE: [CMake] Problem in ADD_CUSTOM_COMMAND
Tried that also...still not working!!..:(...any other clue? Thanks and Regards Anupam Malhotra -Original Message- From: Sylvain Benner [mailto:[EMAIL PROTECTED] Sent: Monday, February 11, 2008 5:05 PM To: Malhotra, Anupam Cc: cmake@cmake.org Subject: Re: [CMake] Problem in ADD_CUSTOM_COMMAND And using xcopy instead of copy ? --Sylvain The information contained in this electronic mail transmission may be privileged and confidential, and therefore, protected from disclosure. If you have received this communication in error, please notify us immediately by replying to this message and deleting it from your computer without copying or disclosing it. ___ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Wee question about CMake developer etiquette
On Monday 11 February 2008, KHMan wrote: ... > As it is, I have tried to look for a list of key developers, but > since the project is identified more with the company, I was > unable to find a list of key developers easily. I looked at the > website and tarball, but didn't manage to get a clear answer. The cmake developers are: -core developers: Bill, Brad and Ken -everybody with a @kitware.com email address And some more contributors, AFAIK all of them are maintaining cmake based buildsystems for their respective project, e.g. Alan Irwin, Andreas Schneider, Eric Wing and myself. Brandon is an active user (as you can see on this mailing list), but no cmake developer or endorsed by the cmake developers or something like that. Alex ___ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] ADD_COMPILE_TEST macro
Alexander Neundorf wrote: On Monday 11 February 2008, Mathieu Malaterre wrote: Hi there, I would like to know if anyone has written a ADD_COMPILE_TEST macro for cmake. Basically I would like to check that some template instantiation should not compile, while other should. I tried quickly doing cmake -P + TRY_COMPILE but I am getting an error : Command TRY_COMPILE not scriptable Code can be found here: Maybe you want CHECK_CXX_SOURCE_COMPILES ? It comes with cmake. That won't help, as it is still not going to be accessible from a cmake -P script. Why are you doing this as a -P script and not part of the build? -Bill ___ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake
[CMake] ctest & ctrl-c
When running ctest, and I hit ctrl-c to stop it, is it supposed to kill the application being run by ctest? On Windows, I'm stale apps that I have to kill with the task manager that ctest didn't kill. Clint ___ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Problem in ADD_CUSTOM_COMMAND
On Feb 8, 2008 6:35 AM, Sylvain Benner <[EMAIL PROTECTED]> wrote:
>
> >
> > SET(CMAKE_COMMAND "copy \"${vpcl_path}\" \"${PROJECT_SOURCE_DIR}\"")
> >
> > ADD_CUSTOM_COMMAND(TARGET vpcl POST_BUILD COMMAND ${CMAKE_COMMAND}
> > VERBATIM)
> >
> I think you have forgot the ARGS argument
ARGS is old school. Not necessary anymore.
I think someone forgot to convert the paths to native Windows paths.
Use file(TO_NATIVE_PATH path result)
Cheers,
Brandon Van Every
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
Re: AW: [CMake] "Treat wchar as built-in type" in Cmake ?
Gerhard Grimm wrote: > Hi Stephen, > > there are two ways to have this compiler flag added in a non-global fashion: > > - You can add it to specific targets using > > set_target_properties(mytarget1 mytarget2 ... > PROPERTIES COMPILE_FLAGS "/Zc:wchar_t-") This works fine - thanks to all who suggested it. > - You can add it to specific source files using > > set_source_files_properties(mysource1 mysource2 ... > PROPERTIES COMPILE_FLAGS "/Zc:wchar_t-") > This is useful to know too. I don't see how the COMPILE_CXX_FLAGS suggestion would have worked though - isn't that a global setting ? -- Regards Steve Collyer Netspinner Ltd ___ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake
RE: [CMake] Problem in ADD_CUSTOM_COMMAND
In general, this code-fragment works:
SET(_srcDir1 /${vpcl_path})
SET(_destination /${PROJECT_SOURCE_DIR}})
IF (MSVC)
SET(command xcopy)
SET(_parameter "/Y/I")
ELSE(MSVC)
set(command cp)
ENDIF(MSVC)
ADD_CUSTOM_TARGET(myTarget ALL DEPENDS ${_srcDir1})
FILE(TO_NATIVE_PATH ${_srcDir1} _srcDir1)
FILE(TO_NATIVE_PATH ${_destination} _destination)
ADD_CUSTOM_COMMAND(
TARGET myTarget
POST_BUILD
COMMAND ${command} ${_srcDir1} ${_destination} ${_parameter}
)
With MS-copy there are sometimes problems especially if you use
directory names like sigC++ or libxml++
Michael
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] CMake book
2008/2/6, Michael Wild <[EMAIL PROTECTED]>: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Hi all > > I wanted to ask whether the new CMake book will be available on Amazon > or some other (preferably european) retailer. The problem is that if I > buy it through the Yahoo shop, shipping to Switzerland is ridiculously > expensive (more than the book is worth!). It seems that The new CMake book reach Amazon.com: http://www.amazon.com/Mastering-CMake-4th-Ken-Marti/dp/1930934203/ref=sr_1_5?ie=UTF8&s=books&qid=1202758460&sr=8-5 -- Erk ___ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Problem in ADD_CUSTOM_COMMAND
What's the value of $(IntDir) ? Have you already tried this : $(IntDir)/vpcl.lib instead of C:/NIGHTLY_BUILD_IMPROVED_TESTING/Visual Studio 6Debug/output/$(IntDir)/vpcl.lib? ? And in your path the directory "Visual Studio 6Debug" is right ? --Sylvain ___ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Problem in ADD_CUSTOM_COMMAND
And using xcopy instead of copy ? --Sylvain ___ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] converting VS projects to CMake
Brandon Van Every a écrit : CMake's Killer App would be a build conversion evaluator that gives hope to the project, and incrementally leads to a full translation. That is the vision. Do you want to help with that or do you want to leave me to figure it out? If I had time to help, sure I would do it, but there is another problem. My vision of CMake and how I understand it have been quite diverging since it's like I started a new branch of CMake 1,5 years ago. I don't know very well the new features, but if I can help a bit on the mailing list I do it. One of my bigger regret is to have reached the point of no return, so much customizations, add-ons, new commands that our CMake scripts and version of CMake cannot fit the official version. Since even my vision of CMake is not right, my vision for new features of CMake cannot be right. I apologize for not telling this before. --Sylvain ___ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake
[CMake] ADD_COMPILE_TEST macro
Hi there, I would like to know if anyone has written a ADD_COMPILE_TEST macro for cmake. Basically I would like to check that some template instantiation should not compile, while other should. I tried quickly doing cmake -P + TRY_COMPILE but I am getting an error : Command TRY_COMPILE not scriptable Code can be found here: https://gdcm.svn.sourceforge.net/svnroot/gdcm/Sandbox/CMakeModules/UseCompileTest.cmake Thanks for suggestions, -- Mathieu ___ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake
AW: [CMake] "Treat wchar as built-in type" in Cmake ?
Hi Stephen, there are two ways to have this compiler flag added in a non-global fashion: - You can add it to specific targets using set_target_properties(mytarget1 mytarget2 ... PROPERTIES COMPILE_FLAGS "/Zc:wchar_t-") - You can add it to specific source files using set_source_files_properties(mysource1 mysource2 ... PROPERTIES COMPILE_FLAGS "/Zc:wchar_t-") Usually you want to take the first approach - unless you are using the "NMake Makefiles" generator and have a resource script (.rc file) among your sources. In this case your custom compile flags will be passed to the resource compiler as well, causing it to either error out or generate an invalid .res file (happens with the /MT option BTW) that will crash the linker. Go for the second approach then. The "Visual Studio xxx" generators behave more useful here. They filter out any target compile flags unsuitable for the resource compiler and only pass /I or /D flags to it. Best regards, Gerhard -Ursprüngliche Nachricht- Gesendet: Samstag, 9. Februar 2008 22:29 Cc: CMake@cmake.org Betreff: Re: [CMake] "Treat wchar as built-in type" in Cmake ? Stefan Buschmann wrote: > Just add the corresponding command line option for the compiler: > > ADD_DEFINITIONS( > /Zc:wchar_t-# Treat wchar_t as > built-in type > ) > > BTW: The command line switch for a specific option is usually mentioned > in the comments for that option in Visual Studio. Thanks. However, as far as I can see, ADD_DEFINITIONS adds the option globally for all projects. I want to restrict it to one only - is that possible ? -- Regards Steve Collyer Netspinner Ltd ___ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake ___ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake
[CMake] Qt 4.4 Phonon and WebKit
Hello List, I've started using cmake some days ago to build a cpp-app using Qt4.4 Technology Preview 1 on my Debian Sid host. I need to link against the new Phonon-Lib, so I extended the standard CMake 2.4.8 Modules to be able to link against the lib. I only tested Phonon, whose name may change in future. I tried to test if the minor version is 4, but I don't know if the position of the test (UseQt4.cmake) is right, as my understanding of cmake is rather limited ATM. The Patches: http://web1.v846.ncsrv.de/cmake/UseQt4.cmake_Qt4.4tp1.patch http://web1.v846.ncsrv.de/cmake/FindQt4.cmake_Qt4.4tp1.patch HTH Stefan ___ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake
RE: [CMake] Problem in ADD_CUSTOM_COMMAND
I tried this command. Now it is not giving any error but the file is not
actually copied. I printed the value of vpcl_path. It is showing that
as:
C:/NIGHTLY_BUILD_IMPROVED_TESTING/Visual Studio
6Debug/output/$(IntDir)/vpcl.lib
Please advice. Thanks in advance.
Thanks and Regards
Anupam Malhotra
-Original Message-
From: Sylvain Benner [mailto:[EMAIL PROTECTED]
Sent: Monday, February 11, 2008 4:42 PM
To: Malhotra, Anupam
Cc: cmake@cmake.org
Subject: Re: [CMake] Problem in ADD_CUSTOM_COMMAND
I missed the additional quotes, the correct command is :
ADD_CUSTOM_COMMAND(TARGET vpcl POST_BUILD COMMAND copy
"\"${vpcl_path}\"" "\"${PROJECT_SOURCE_DIR}\"" VERBATIM)
This is a common rule in CMake script, when you want to pass an
argument, always use quotes to be sure it will not be split into several
arguments due to spaces or some other characters.
--Sylvain
The information contained in this electronic mail transmission
may be privileged and confidential, and therefore, protected
from disclosure. If you have received this communication in
error, please notify us immediately by replying to this
message and deleting it from your computer without copying
or disclosing it.
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] ADD_COMPILE_TEST macro
On Monday 11 February 2008, Mathieu Malaterre wrote: > Hi there, > > I would like to know if anyone has written a ADD_COMPILE_TEST macro > for cmake. Basically I would like to check that some template > instantiation should not compile, while other should. I tried quickly > doing cmake -P + TRY_COMPILE but I am getting an error : > >Command TRY_COMPILE not scriptable > > Code can be found here: Maybe you want CHECK_CXX_SOURCE_COMPILES ? It comes with cmake. Alex ___ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Problem in ADD_CUSTOM_COMMAND
Hi,
ADD_CUSTOM_COMMAND(TARGET vpcl POST_BUILD COMMAND copy ARGS
"\"${vpcl_path}\"" "\"${PROJECT_SOURCE_DIR}\"" VERBATIM)
And also
ADD_CUSTOM_COMMAND(TARGET vpcl POST_BUILD COMMAND copy ARGS
"${vpcl_path}" "${PROJECT_SOURCE_DIR}" VERBATIM)
Can you developp the command, what's the value of ${vpcl_path} ?
Put the value of ${PROJECT_SOURCE_DIR} also, but the error should not
come from this one.
The ARGS argument is optional, I checked one of our post build rules.
Try the first syntax you used but without the CMAKE_COMMAND variable:
ADD_CUSTOM_COMMAND(TARGET vpcl POST_BUILD COMMAND copy \"${vpcl_path}\"
\"${PROJECT_SOURCE_DIR}\" VERBATIM)
If it works and you want to use a variable, try to define it like this:
LIST(APPEND CMAKE_COMMAND copy "\"${vpcl_path}\""
"\"${PROJECT_SOURCE_DIR}\"")
--Sylvain
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Problem in ADD_CUSTOM_COMMAND
I missed the additional quotes, the correct command is :
ADD_CUSTOM_COMMAND(TARGET vpcl POST_BUILD COMMAND copy
"\"${vpcl_path}\"" "\"${PROJECT_SOURCE_DIR}\"" VERBATIM)
This is a common rule in CMake script, when you want to pass an
argument, always use quotes to be sure it will not be split into several
arguments due to spaces or some other characters.
--Sylvain
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
[CMake] ctest scripts with svn
Hi everybody, I'm trying to get a ctest (from cmake-2.4.8 release) script to run with our svn repository and am hitting some obstacles in the way ;) To begin with, I can't get the generated DartConfiguration.tcl to contain an SVNCommand definition. I do set CTEST_SVN_COMMAND and let ctest insert SVNCOMMAND in the initial CMakeCache.txt - but CTEST_SVN_COMMAND doesn't seem to have any effect at all. Ok. The - slightly hackish - solution to this, from reading on this list, seems to be to 'misuse' CTEST_CVS_COMMAND instead. However, this breaks the ExperimentalUpdate stage for me since if CVSCOMMAND is set, cmake assumes it should update in cvs mode ... In my case - since no SVNCommand def is written to DartConfiguration.tcl - the ExperimentalUpdate stage fails with message 'No CVSCommand, SVNCommand or UpdateCommand found in DartConfiguration.tcl' ... as soon as I insert an SVNCommand definition in DartConfiguration.tcl manuall, it works as expected. Any ideas? Or maybe a link to a working ctest-script using an svn repository? ;) Best regards, -.jan.- ___ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Qt 4.4 Phonon and WebKit
On Monday 11 February 2008 8:53:34 am StefanV wrote: > Hello List, > I've started using cmake some days ago to build a cpp-app using Qt4.4 > Technology Preview 1 on my Debian Sid host. I need to link against the > new Phonon-Lib, so I extended the standard CMake 2.4.8 Modules to be > able to link against the lib. I only tested Phonon, whose name may > change in future. I tried to test if the minor version is 4, but I > don't know if the position of the test (UseQt4.cmake) is right, as my > understanding of cmake is rather limited ATM. The Patches: > http://web1.v846.ncsrv.de/cmake/UseQt4.cmake_Qt4.4tp1.patch > http://web1.v846.ncsrv.de/cmake/FindQt4.cmake_Qt4.4tp1.patch > Thanks. You can track the status with this bug report. http://public.kitware.com/Bug/view.php?id=6316 Clint ___ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake
RE: [CMake] Problem in ADD_CUSTOM_COMMAND
Hi I am using GET_TARGET_PROPERTY(vpcl_path vpcl LOCATION) This command returns the vpcl_path as C:/NIGHTLY_BUILD_IMPROVED_TESTING/Visual Studio 6Debug/output/$(IntDir)/vpcl.lib The $(IntDir) variable must be some CMake specific variable. Instead of the path returned from GET_TARGET_PROPERTY, I hardcoded the exact path. But still it's giving no error and the actual copy is still not happeneing. Thanks and Regards Anupam Malhotra -Original Message- From: Sylvain Benner [mailto:[EMAIL PROTECTED] Sent: Monday, February 11, 2008 5:29 PM To: Malhotra, Anupam Cc: cmake@cmake.org Subject: Re: [CMake] Problem in ADD_CUSTOM_COMMAND What's the value of $(IntDir) ? Have you already tried this : $(IntDir)/vpcl.lib instead of C:/NIGHTLY_BUILD_IMPROVED_TESTING/Visual Studio 6Debug/output/$(IntDir)/vpcl.lib? ? And in your path the directory "Visual Studio 6Debug" is right ? --Sylvain The information contained in this electronic mail transmission may be privileged and confidential, and therefore, protected from disclosure. If you have received this communication in error, please notify us immediately by replying to this message and deleting it from your computer without copying or disclosing it. ___ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] ADD_COMPILE_TEST macro
On Feb 11, 2008 6:45 PM, Bill Hoffman <[EMAIL PROTECTED]> wrote: > Alexander Neundorf wrote: > > On Monday 11 February 2008, Mathieu Malaterre wrote: > >> Hi there, > >> > >> I would like to know if anyone has written a ADD_COMPILE_TEST macro > >> for cmake. Basically I would like to check that some template > >> instantiation should not compile, while other should. I tried quickly > >> doing cmake -P + TRY_COMPILE but I am getting an error : > >> > >>Command TRY_COMPILE not scriptable > >> > >> Code can be found here: > > > > Maybe you want CHECK_CXX_SOURCE_COMPILES ? It comes with cmake. > > > That won't help, as it is still not going to be accessible from a cmake > -P script. Why are you doing this as a -P script and not part of the > build? This is a test... I need to run it just like a normal test. I know this sound weird to check for something that do not compile. The simpliest case is when I need to trigger a static assert. Another example could be for ITK to check that their itkConceptChecking are actually working: Luis are you doing that ? Or maybe I misunderstood you suggestion, and I could run the test, by simply sending the stored result from CMakeCache.txt (thus the test would be run at build time), is this correct ? Thanks again, -- Mathieu ___ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake
