[CMake] VS8.0 CompileAs

Hi, For one of my project, I need to compile files with .c extension as C++ files. It's an uncommon need but it exists. In Visual Sturio, there is a compiler option, /TP that does exactly this. In Visual Studio 2005 project files, it seems to translate into CompileAs property which

Re: [CMake] Execute_process with wildcard characters

Bill Hoffman wrote: > FILE(GLOB_RECURSE variable [RELATIVE path]) > FILE(REMOVE [file1 ...]) While we are on this topic, I found something missing from the FILE command: the ability to rename a file or a directory. I need just this for one of my programs and it's missing. I tried to add it as a f

Re: [CMake] How to test environment variable in IF command

Mike Talbot wrote: > Hi, > > I'm trying to work out how to test for an environment variable in an IF > command, the following doesn't work: > > SET(ENV{FOO} ON) > MESSAGE("FOO = $ENV{FOO}")# prints "FOO = ON" > IF(ENV{FOO}) > MESSAGE("FOO is set") > ENDIF(ENV{FOO}) > > Does anyone know wha

[CMake] cmake, ccache and mingw

Hi, Has anybody managed to run successfully CMake, ccache mingw together on windows ? Last time I tried, it failed. I remember having problems with filename having spaces, and problem for passing correct options to ccache. regards, Philippe ___

Re: [CMake] Documentation strategy

Brandon Van Every wrote: > My conclusion is > that Kitware doesn't have the resources to address these things, and > the community has to find a way to do it. If I understood correctly, kitware does not do any money off CMake. They just need CMake to be good and usable, so that they can make money

Re: [CMake] Documentation strategy

Brandon Van Every wrote: > On 6/20/07, Philippe Fremy <[EMAIL PROTECTED]> wrote: >> >> All in all, CMake is a good and powerful tool, but I find that the >> documentation is lacking behind. More structure, more usage example, >> more common cases would in my opinio

Re: [CMake] FILE command in make_custom_target

Brandon Van Every wrote: > On 6/19/07, Bill Hoffman <[EMAIL PROTECTED]> wrote: >> Philippe Fremy wrote: >> > >> > It is ironic that a running cmake instance, that supports platform >> > agnostic directory creation, is not able to do that inside a rule an

Re: [CMake] FILE command in make_custom_target

Brandon Van Every wrote: > On 6/17/07, Philippe Fremy <[EMAIL PROTECTED]> wrote: >> >> Hi, >> >> I want a directory to be built when a custom target is executed. >> >> I tried something like this: >> >> add_custom_target(

[CMake] FILE command in make_custom_target

Hi, I want a directory to be built when a custom target is executed. I tried something like this: add_custom_target( doc_libyzis COMMAND FILE( MAKE_DIRECTORY ${CMAKE_CURRENT_SOURCE_DIR}/../apidoc ) COMMAND ${DOXYGEN} libyzis.doxy

Re: [CMake] compiling implementation first in dependancies

Filip Brcic wrote: > Дана четвртак 14 јун 2007, Philippe Fremy је написао(ла): >> Hi, >> >> In my project, I have very often a pattern like this: >> a.cpp: >> #include "z.h" >> >> b.cpp: >> #include "z.h" >> >&

Re: [CMake] compiling implementation first in dependancies

Alexander Neundorf wrote: >> If I change z.h and z.cpp to add a new method, I usually don't get z.h >> to work out of the box, but only realize it when compiling z.cpp . >> What's annoying is that cmake will first compile a.cpp , b.cpp , c.cpp >> and then only z.cpp . > > Try "make help" to get a

[CMake] compiling implementation first in dependancies

Hi, In my project, I have very often a pattern like this: a.cpp: #include "z.h" b.cpp: #include "z.h" c.cpp: #include "z.h" z.cpp: #include "z.h" If I change z.h and z.cpp to add a new method, I usually don't get z.h to work out of the box, but only realize it when compiling z.cpp .