[CMake] VisualStudio debug command
Probably newby question: Under Visual Studio, at least from VS 7, a project can have debugging command and command arguments. Is it possible to set them in a CMakeFile ? Thanks a lot Luigi ___ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake
RE: [CMake] VisualStudio debug command
Hi Luigi, I believe debugging info is held in a binary file - *.suo for vc7 - so would be tricky to set using cmake without using the vcproject automation engine. Ian -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Luigi Calori Sent: 28 March 2006 12:45 To: cmake@cmake.org Subject: [CMake] VisualStudio debug command Probably newby question: Under Visual Studio, at least from VS 7, a project can have debugging command and command arguments. Is it possible to set them in a CMakeFile ? Thanks a lot Luigi ___ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake Visit our website at http://www.ubs.com This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message which arise as a result of e-mail transmission. If verification is required please request a hard-copy version. This message is provided for informational purposes and should not be construed as a solicitation or offer to buy or sell any securities or related financial instruments. ___ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] how to set the executable flag on a file ?
Gaetan Lehmann wrote: In our project, with CONFIGURE_FILE() macro, we are configuring the paths in a script. How can we set the executable flag on this script, both for file in build tree and installed one ? Currently you have to make sure the input file has the proper permissions to get it working in the build tree, which will then also get it working in the install tree. -Brad ___ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Is it possible to set some environment vars to run some tests ?
At 10:08 AM 3/28/2006, Brad King wrote: Gaetan Lehmann wrote: To run some tests on the python modules compiled with cmake, I need to set the PYTHONPATH environement variable for the tests added with ADD_TEST() macro. Is it possible ? Not directly with Dart or ctest. We typically have created test driver programs that wrap around tests and setup whatever environment is needed. These drivers are also useful for interpreting custom failure cases. See this one as an example: http://www.paraview.org/cgi-bin/viewcvs.cgi/GUI/Client/pvTestDriver.cxx?root=ParaViewview=markup Another option is a ctest -S script. In those scripts it is possible to set environment variables. -Bill ___ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] order of include dirs
Alexander Neundorf wrote:
in KDE we have the problem that e.g. when compiling kdebase the headers
in the source dir should be preferred over the installed ones.
Usually we would do
include_directories( ${KDE4_INCLUDES} ) in the toplevel CMakeLists.txt.
When adding more include dirs in CMakeLists.txt in deeper directories,
these directories will be appended to the list of include dirs, except
when used with the BEFORE keyword.
But now we cannot realistically expect that every KDE developer will
always remember the BEFORE keyword.
So we had two ideas:
make the behaviour configurable:
# make prepend default:
set(CMAKE_INCLUDE_DIRS_APPEND false)
# to force appending:
include_directories(AFTER dir1 dir2)
Problem here: moving cmake files around to another project where this
isn't set would change the behaviour.
Second idea:
include_directories(LAST dir1 dir2)
which would have the effect that the listed directories would always be
used after all other include dirs specified without the LAST keyword.
I think that will create two ordered lists of include directories
instead of one, which will just be confusing. I suggest creating a
kde4_add_indluce_directories macro that adds the BEFORE option:
macro(kde4_add_indluce_directories)
include_directories(BEFORE ${ARGN})
endmacro(kde4_add_indluce_directories)
-Brad
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
