Hi,
I’ve stumbled over following issue:
if (NOT ^ MATCHES ^\^ )
message(FATAL_ERROR "Anker not found!")
endif()
if (NOT $
signature.asc
Description: Message signed with OpenPGP
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.or
Hi everyone,
I'm trying to figure out a way to escape the special keywords that are
used to introduce named options in function arguments (see
CMakeParseArguments [1]), for example to pass the string
RESULT_VARIABLE as argument to a command executed via
execute_process():
set(what "RESULT_VAR
Thanks that was it!
On Thu, Apr 11, 2013 at 9:02 AM, David Cole wrote:
> Try:
>
> cmake -D "DOXYGEN_TAGFILES:STRING=C:/bar/somevalue=C:/foo/another" -P
> configure_file.cmake
>
> Because of the “:TYPE” parsing, “:” after the = sign can sometimes be
> misinterpreted by the regex code used to p
Try:
cmake -D "DOXYGEN_TAGFILES:STRING=C:/bar/somevalue=C:/foo/another" -P
configure_file.cmake
Because of the “:TYPE” parsing, “:” after the = sign can sometimes be
misinterpreted by the regex code used to parse these out...
HTH,
David
From: Robert Dailey
Sent: Thursday, April
Actually I did a bit more testing on this:
C:\Work\rdailey-hp\dpd-cmake\cmake\scripts\cmake>cmake -D
"DOXYGEN_TAGFILES=C:/bar/somevalue=C:/foo/another" -P configur
e_file.cmake
DOXYGEN_TAGFILES:
C:\Work\rdailey-hp\dpd-cmake\cmake\scripts\cmake>cmake -D
"DOXYGEN_TAGFILES=C/bar/somevalue=C:/foo/ano
I'm invoking cmake -P to execute a CMake script in a custom command,
and I also pass in variables via -D. Here is the command that gets
generated by CMake for the custom command:
"C:\Program Files (x86)\CMake 2.8\bin\cmake.exe" -D
IN_FILE=C:/Work/rdailey-hp/dpd-cmake/server/gmmserver/domino/server
On 10/18/2010 06:50 PM, David Genest wrote:
> Hi,
>
> I have tried and tried, but haven't succeeded to include a semicolon as a
> COMPILE_FLAGS property for a file. I turn to you for wisdom:
>
> I need to get this as a result in the pre-processor definitions:
>
> MYPATH=\"d:\\;.\\Lib\"
>
> B
Hi,
I have tried and tried, but haven't succeeded to include a semicolon as a
COMPILE_FLAGS property for a file. I turn to you for wisdom:
I need to get this as a result in the pre-processor definitions:
MYPATH=\"d:\\;.\\Lib\"
But when I use the following escape sequence in set_source_files_
> On Dec 20, 2007 4:25 PM, Andrew Roark wrote:
> >
> > By all means, if it can be done in CMake, then do it in CMake.
> >
> > But the CMake philosophy itself is in dispute with your argument.
>
> I don't need anything but CMake to do regexes. They aren't ideal
> regexes, but you can still get pr
On Dec 20, 2007 4:25 PM, Andrew Roark <[EMAIL PROTECTED]> wrote:
>
> By all means, if it can be done in CMake, then do it in CMake.
>
> But the CMake philosophy itself is in dispute with your argument.
I don't need anything but CMake to do regexes. They aren't ideal
regexes, but you can still get
> On Dec 10, 2007 7:12 PM, Andrew Roark wrote:
> >
> > For any tricky file operations (like "all files ending with
> XML
>
greater than 2Kb using DOS newlines" etc) I would personally write a
> python
>
script (e.g. ROOTDIR/util/xmlfinder.py) to do that work and make
> the
>
command simply i
On Dec 12, 2007 10:09 AM, Javier Gonzalez <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Well, these don't answer much. The first message (from Andrew) mentions
> an option I have considered: writing everything on a script and calling
> the script.
>
> However, I thought it would be possible with cmake.
"It
Hi,
Well, these don't answer much. The first message (from Andrew) mentions
an option I have considered: writing everything on a script and calling
the script.
However, I thought it would be possible with cmake. The wiki just says:
"You may need \\ instead of \ due to CMake argument processing. \
I'm quite jaded about keeping CMakeLists.txt "simple." As far as I'm
concerned, it should be as simple as the level of complication of your
build. If I want encapsulation, I write a macro. Otherwise I'll just
write straight CMake script, because I'd rather read CMake script than
the docs of 5
I'm quite jaded about keeping CMakeLists.txt "simple." As far as I'm
concerned, it should be as simple as the level of complication of your
build. If I want encapsulation, I write a macro. Otherwise I'll just
write straight CMake script, because I'd rather read CMake script than
the docs of 5
On Dec 10, 2007 7:12 PM, Andrew Roark <[EMAIL PROTECTED]> wrote:
>
> For any tricky file operations (like "all files ending with XML greater than
> 2Kb using DOS newlines" etc) I would personally write a python script (e.g.
> ROOTDIR/util/xmlfinder.py) to do that work and make the command simply
- Original Message
> From: Hendrik Sattler <[EMAIL PROTECTED]>
> To: cmake@cmake.org
> Sent: Monday, December 10, 2007 7:29:21 PM
> Subject: Re: [CMake] escaping!
>
> Am Dienstag 11 Dezember 2007 schrieb Andrew Roark:
> > > Is it pos
Am Dienstag 11 Dezember 2007 schrieb Andrew Roark:
> > Is it possible to have a command like this?
> > ADD_CUSTOM_COMMAND(OUTPUT ${my_file}
> > ...
> >COMMAND find . -name "*xml" > /dev/null
> > ...
> > VERBATIM
> > )
>
> Not sure if you got a reply to this, nor if the following is any
> Is it possible to have a command like this?
> ADD_CUSTOM_COMMAND(OUTPUT ${my_file}
> ...
>COMMAND find . -name "*xml" > /dev/null
> ...
> VERBATIM
> )
Not sure if you got a reply to this, nor if the following is any help, BUT...
For any tricky file operations (like "all files ending
Hi all,
Is it possible to have a command like this?
ADD_CUSTOM_COMMAND(OUTPUT ${my_file}
...
COMMAND find . -name "*xml" > /dev/null
...
VERBATIM
)
I managed to get it working without the verbatim option but now I added
other things and it became a nightmare. I'm trying the verbatim op
Kedzierski, Artur CIV NAVSURFWARCENDIV CORONA wrote:
> Hi,
>
> I am trying to create FooConfig.cmake by having
> FooConfig.cmake.in and running CONFIGURE_FILE(FooConfig.cmake.in
> FooConfig.cmake)
> on it.
> In FooConfig.cmake.in, I have something like:
> SET(MY_LOCAL ${CMAKE_INS
Hi,
I am trying to create FooConfig.cmake by having
FooConfig.cmake.in and running CONFIGURE_FILE(FooConfig.cmake.in
FooConfig.cmake)
on it.
In FooConfig.cmake.in, I have something like:
SET(MY_LOCAL ${CMAKE_INSTALL_PREFIX}/include/foo)
IF (WIN32)
SET(MY_LOCAL \$(M
Zachary Pincus wrote:
Assuming I'm stuck with 2.2.3, what's my best bet: use a
CUSTOM_COMMAND, or do you think that the following usage is portable:
If you want it to occur at CMake time then you need EXEC_PROGRAM. If it
can wait until build time you should use a custom command.
EXEC_PROGR
Now, when I had set this all up in the context of an
ADD_CUSTOM_COMMAND instead of an EXEC_PROGRAM, things seemed to
work -- is there automatic path escaping for args to custom
commands, but not exec'd programs, in this version of CMake? (For
some reason, we had to move to EXEC_PROGRAM
Zachary Pincus wrote:
Hi folks,
I'm using CMake 2.2-3, and have recently run into some problems with a
stanza of CMake code that looks like this:
SET(src "${IN_DIR}/foo.bar")
SET(tgt "${OUT_DIR}/foo.bar")
EXEC_PROGRAM(${CMAKE_COMMAND} ARGS -E copy_if_different ${src} ${tgt})
The problem com
Hi folks,
I'm using CMake 2.2-3, and have recently run into some problems with
a stanza of CMake code that looks like this:
SET(src "${IN_DIR}/foo.bar")
SET(tgt "${OUT_DIR}/foo.bar")
EXEC_PROGRAM(${CMAKE_COMMAND} ARGS -E copy_if_different ${src} ${tgt})
The problem comes when src or tgt have
26 matches
Mail list logo
