2008/11/20 BRM <[EMAIL PROTECTED]>:
> It was reporting that it could not find the executable.
> However, this was certainly a PEBKAC issue (do'h) - I forgot to have an
> ADD_EXECUTABLE() for the test program - or even an
> CREATE_TEST_SOURCE_LIST()...though so it shouldn't have been finding it.
Matthew Woehlke wrote:
Can someone explain to me:
- why this doesn't work (prints "CFLAGS match broken!!")
- if it's supposed to work or if this is a bug
- a great work-around to this problem ;-)
This is with cmake 2.6.2
macro(foo bar)
if("${ba
Matthew Woehlke wrote:
Michael Jackson wrote:
On Nov 19, 2008, at 12:24 PM, Matthew Woehlke wrote:
Should I post the whole script?
Sure. You can post the script on the CMake Wiki or post it here and
I'll get it up on the Wiki really soon.
My eventual goal is to check it into KDE's svn. (Ac
It was reporting that it could not find the executable.
However, this was certainly a PEBKAC issue (do'h) - I forgot to have an
ADD_EXECUTABLE() for the test program - or even an
CREATE_TEST_SOURCE_LIST()...though so it shouldn't have been finding it. Though
I am not sure what the best method is
Matthew,
On Wed, Nov 19, 2008 at 5:56 PM, Matthew Woehlke
<[EMAIL PROTECTED]> wrote:
> Can someone explain to me:
> - why this doesn't work (prints "CFLAGS match broken!!")
> - if it's supposed to work or if this is a bug
> - a great work-around to this problem ;-)
>
> This is with cmake 2.6.2
>
>
Michael Jackson wrote:
I can do the initial writing if you want. I have everything in place to
add another generator to the code.
My script already works (to the extent the doc is correct) :-). Its only
limitation is that it outputs just the lists, and only knows how to do
something useful wi
Can someone explain to me:
- why this doesn't work (prints "CFLAGS match broken!!")
- if it's supposed to work or if this is a bug
- a great work-around to this problem ;-)
This is with cmake 2.6.2
macro(foo bar)
if("${bar}" MATCHES "CFLAGS")
On Nov 19, 2008, at 12:24 PM, Matthew Woehlke wrote:
Michael Jackson wrote:
I am parsing the $CMAKE_BUILD/Docs/cmake.docbook file. There is
just enough information with the tags to parse out all the
commands, variables and properties. What _is not_ in that file are
the "reserved words" or
Michael Jackson wrote:
I am parsing the $CMAKE_BUILD/Docs/cmake.docbook file. There is just
enough information with the tags to parse out all the commands,
variables and properties. What _is not_ in that file are the "reserved
words" or "special arguments" in any _easy_ tags. I can parse the us
Hello,
Maybe this is slightly offtopic, but I am playing around again with
WinCE and CMake.
For some reason I am now running into an issue I never had before,
during the compile
checks I get the following output in CMakeError.log:
=
Compilin
Hi everyone,
> Since dependency handling seemingly has been improved in cmake 2.6.2,
> the probably correct behaviour now means that a project that gets
> added by add_subdirectory now is installed while it's not actually
> built yet, leading to a post-build error. This is especially true for
Hi there,
Has anyone a good summary on how those three variable interfacts ?
It looks like CPACK_INSTALL_PREFIX is not taken into account for the
NSIS installer, and instead solely CPACK_PACKAGE_INSTALL_DIRECTORY is
used.
I need to locate some resource files installed on the system, so I'd
lik
12 matches
Mail list logo
