date:20081118

Is there a list of the reserved words or Keywords for CMake.  
Examples would be:


AND, NOT, OR, PROPERTIES, CACHE, FORCE..

Thanks
_
Mike Jackson  [EMAIL PROTECTED]
BlueQuartz Softwarewww.bluequartz.net
Principal Software Engineer  Dayton, Ohio



___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake

[CMake] Does CMake/CPack not support creating a source-only tarball

Hello,

According to the CMake bashing website:

http://www.remlab.net/op/cmake.shtml

CMake/Cpack does not support creating a source-only tarball distribution for a 
collection of software.

Is there some way to create a source-only tarball distribution with CMake/Cpack 
that can selectively pick out files from the original source tree like 
autotools does?

If it does not, then the some Trilinos developers could be quite annoyed by 
this.  I think there are better workarounds for the problem of not releasing 
some files but it will take some work no mater how you look at it.

- Ross

-
Dr. Roscoe A. Bartlett
Senior Member of the Technical Staff
Trilinos Software Engineering Technologies and Integration Lead
Sandia National Laboratories
Phone: (505) 275-6147



___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Does CMake/CPack not support creating a source-only tarball

2008-11-18 Thread Timothy M. Shead


Bartlett, Roscoe A wrote:

Hello,
 
According to the CMake bashing website:
 
_http://www.remlab.net/op/cmake.shtml_
 
CMake/Cpack does not support creating a source-only tarball distribution 
for a collection of software.
 
Is there some way to create a source-only tarball distribution with 
CMake/Cpack that can selectively pick out files from the original source 
tree like autotools does?


By default, CPack supports source tarball generation with make 
source_package, and the generation can be customized in a variety of 
ways (e.g: generating a source package from a subdirectory with a custom 
target, etc).


There is no equivalent to make distcheck, unless you roll your own 
(which certainly would be doable).


Cheers,
Tim

--
Timothy M. Shead
Data Analysis  Visualization (1424)
Sandia National Laboratories
505-284-0139

___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake

[CMake] Bug? additional_clean_files not respected if no target present in directory

2008-11-18 Thread Hugo Heden

Good day all,

It seems that

   set_directory_propersties( properties additional_clean_files ... )

is not respected if no target present in the directory -- that is
'make clean' will not remove the specified additional clean file.

Is this possibly a CMake bug, or is it rather a misunderstanding on my part?

$ cmake --version
cmake version 2.6-patch 2

A little test case to illustrate this follows. We have two
CMakeLists.txt-files, one in the root directory and one in a sub
directory.  The former (src/CMakeLists.txt) is not really important,
but included here for completeness. The latter,
src/subdir/CMakeLists.txt, is where the bug appears. There is also a
file that is being installed, src/subdir/hello.txt. Invoking 'make
clean' will not clean that file unless there is an actual target
specified in src/subdir/CMakeLists.txt.

File tree:.

|-- build
|-- install
`-- src
|-- CMakeLists.txt
`-- subdir
|-- CMakeLists.txt
`-- hello.txt


--- src/CMakeLists.txt:

CMAKE_MINIMUM_REQUIRED(VERSION 2.6)
SET( CMAKE_INSTALL_PREFIX ${CMAKE_SOURCE_DIR}/../install )

ADD_SUBDIRECTORY( subdir )

ADD_CUSTOM_TARGET(
  some_target
  COMMAND ${CMAKE_COMMAND} -E echo HELLO
)



--- src/subdir/CMakeLists.txt:

#ADD_CUSTOM_TARGET(
#  some_subdir_target
#  COMMAND ${CMAKE_COMMAND} -E echo WHOHOO
#)

INSTALL(
  FILES hello.txt
  DESTINATION ./
  )

SET_DIRECTORY_PROPERTIES(
  PROPERTIES
  ADDITIONAL_MAKE_CLEAN_FILES
  ${CMAKE_INSTALL_PREFIX}/hello.txt
  )

---
---

As written above, with the target some_subdir_target commented out,
the ADDITIONAL_MAKE_CLEAN_FILES will not be respected - - it seems to
be sort of optimized away:

$ cd build/
$ cmake ../src
...
...
$ make install
...
$ ls ../install
hello.txt
$ make clean
$ ls ../install/
hello.txt   # --- OUCH





However, if the target is not commented out it will all work nicely:


--- src/subdir/CMakeLists.txt:

ADD_CUSTOM_TARGET(
  some_subdir_target
  COMMAND ${CMAKE_COMMAND} -E echo WHOHOO
)

INSTALL(
  FILES hello.txt
  DESTINATION ./
  )

SET_DIRECTORY_PROPERTIES(
  PROPERTIES
  ADDITIONAL_MAKE_CLEAN_FILES
  ${CMAKE_INSTALL_PREFIX}/hello.txt
  )





$ cd build/
$ cmake ../src
...
...
$ make install
...
$ ls ../install
hello.txt
$ make clean
$ ls ../install/
 # no files -- as expected




Any thoughts? Let me know if this is just a misunderstanding, if I
should file a bug on this or if more information is needed.

Best regards

Hugo Heden
Stockholm
Sweden
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] List of 'Reserved Words'

On Tuesday 18 November 2008, Michael Jackson wrote:
 Is there a list of the reserved words or Keywords for CMake.
 Examples would be:

 AND, NOT, OR, PROPERTIES, CACHE, FORCE..

Not really.
The one here should be quite current:
http://websvn.kde.org/trunk/KDE/kdelibs/kate/syntax/data/cmake.xml?revision=773845view=markup

Alex
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] List of 'Reserved Words'



On Nov 18, 2008, at 2:59 PM, Alexander Neundorf wrote:


On Tuesday 18 November 2008, Michael Jackson wrote:

Is there a list of the reserved words or Keywords for CMake.
Examples would be:

AND, NOT, OR, PROPERTIES, CACHE, FORCE..


Not really.
The one here should be quite current:
http://websvn.kde.org/trunk/KDE/kdelibs/kate/syntax/data/cmake.xml?revision=773845view=markup

Alex


Cool. That was pretty close to what I was looking for but it looks  
like there are some CMake Variables in there also (WIN32). I will  
have to factor those out.


Also, not sure how that file is created but I have a CMakeDocBook  
Parser that I wrote (C++ code) to parse through the cmake docbook xml  
file and extract the following items:


Commands
Variables
Properties
Deprecated Commands

I am currently generating an xml file for the CMakeEd plugin xml for  
completions and also generating the TextMate language definition.  
Maybe this code could also be used to update the kate cmake language  
definition file? You are welcome to the code if you think it would help.


_
Mike Jackson  [EMAIL PROTECTED]
BlueQuartz Softwarewww.bluequartz.net
Principal Software Engineer  Dayton, Ohio



___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Does CMake/CPack not support creating a source-only tarball

Tim,

 -Original Message-
 From: Shead, Timothy
 Sent: Tuesday, November 18, 2008 12:10 PM
 To: Bartlett, Roscoe A
 Cc: cmake@cmake.org
 Subject: Re: [CMake] Does CMake/CPack not support creating a
 source-only tarball

 Bartlett, Roscoe A wrote:
  Hello,

  According to the CMake bashing website:

  _http://www.remlab.net/op/cmake.shtml_

  CMake/Cpack does not support creating a source-only tarball
  distribution for a collection of software.

  Is there some way to create a source-only tarball distribution with
  CMake/Cpack that can selectively pick out files from the original
  source tree like autotools does?

 By default, CPack supports source tarball generation with
 make source_package, and the generation can be customized
 in a variety of ways (e.g: generating a source package from a
 subdirectory with a custom target, etc).

This target does not appear to be supported as shown by:

[EMAIL PROTECTED] SERIAL_DEBUG]$ make source_package
make: *** No rule to make target `source_package'.  Stop.

Is there some special way that we need to configure Trilinos or set up Cpack to 
support this?

Thanks,

- Ross

___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Does CMake/CPack not support creating a source-only tarball

2008-11-18 Thread David Cole

It's package_source and it was also discussed very recently in this
thread:http://www.cmake.org/pipermail/cmake/2008-November/025219.html

It was broken, Bill committed a fix to CVS HEAD. Fix will be in the next RC
of CMake 2.6.3, but if you need it today, use CVS HEAD CMake.


HTH,
David


On Tue, Nov 18, 2008 at 3:36 PM, Bartlett, Roscoe A [EMAIL PROTECTED]wrote:

 Tim,

  -Original Message-
  From: Shead, Timothy
  Sent: Tuesday, November 18, 2008 12:10 PM
  To: Bartlett, Roscoe A
  Cc: cmake@cmake.org
  Subject: Re: [CMake] Does CMake/CPack not support creating a
  source-only tarball
 
  Bartlett, Roscoe A wrote:
   Hello,
  
   According to the CMake bashing website:
  
   _http://www.remlab.net/op/cmake.shtml_
  
   CMake/Cpack does not support creating a source-only tarball
   distribution for a collection of software.
  
   Is there some way to create a source-only tarball distribution with
   CMake/Cpack that can selectively pick out files from the original
   source tree like autotools does?
 
  By default, CPack supports source tarball generation with
  make source_package, and the generation can be customized
  in a variety of ways (e.g: generating a source package from a
  subdirectory with a custom target, etc).

 This target does not appear to be supported as shown by:

[EMAIL PROTECTED] SERIAL_DEBUG]$ make source_package
make: *** No rule to make target `source_package'.  Stop.

 Is there some special way that we need to configure Trilinos or set up
 Cpack to support this?

 Thanks,

 - Ross

 ___
 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

Re: [CMake] List of 'Reserved Words'

On Tuesday 18 November 2008, Michael Jackson wrote:
 On Nov 18, 2008, at 2:59 PM, Alexander Neundorf wrote:
  On Tuesday 18 November 2008, Michael Jackson wrote:
  Is there a list of the reserved words or Keywords for CMake.
  Examples would be:
 
  AND, NOT, OR, PROPERTIES, CACHE, FORCE..
 
  Not really.
  The one here should be quite current:
  http://websvn.kde.org/trunk/KDE/kdelibs/kate/syntax/data/cmake.xml?revisi
 on=773845view=markup
 
  Alex

 Cool. That was pretty close to what I was looking for but it looks
 like there are some CMake Variables in there also (WIN32). I will
 have to factor those out.


I just noticed it wasn't updated for some time.
I added some of the new stuff now.
http://websvn.kde.org/trunk/KDE/kdelibs/kate/syntax/data/cmake.xml?view=log

Alex
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Does CMake/CPack not support creating a source-only tarball

2008-11-18 Thread Timothy M. Shead


Bartlett, Roscoe A wrote:


By default, CPack supports source tarball generation with
make source_package, and the generation can be customized
in a variety of ways (e.g: generating a source package from a
subdirectory with a custom target, etc).


This target does not appear to be supported as shown by:

[EMAIL PROTECTED] SERIAL_DEBUG]$ make source_package
make: *** No rule to make target `source_package'.  Stop.

Is there some special way that we need to configure Trilinos or set up Cpack to 
support this?


Correction - it's package_source, not source_package ...

Truly Yours,
Tim

--
Timothy M. Shead
Data Analysis  Visualization (1424)
Sandia National Laboratories
505-284-0139

___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Does CMake/CPack not support creating a source-only tarball

On Tuesday 18 November 2008, David Cole wrote:
 It's package_source and it was also discussed very recently in this
 thread:http://www.cmake.org/pipermail/cmake/2008-November/025219.html

 It was broken, 

Does it work if you run cpack manually (instead of using the target) ?

Alex
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] List of 'Reserved Words'



On Nov 18, 2008, at 3:49 PM, Alexander Neundorf wrote:


On Tuesday 18 November 2008, Michael Jackson wrote:

On Nov 18, 2008, at 2:59 PM, Alexander Neundorf wrote:

On Tuesday 18 November 2008, Michael Jackson wrote:

Is there a list of the reserved words or Keywords for CMake.
Examples would be:

AND, NOT, OR, PROPERTIES, CACHE, FORCE..


Not really.
The one here should be quite current:
http://websvn.kde.org/trunk/KDE/kdelibs/kate/syntax/data/cmake.xml?revisi
on=773845view=markup

Alex


Cool. That was pretty close to what I was looking for but it looks
like there are some CMake Variables in there also (WIN32). I will
have to factor those out.



I just noticed it wasn't updated for some time.
I added some of the new stuff now.
http://websvn.kde.org/trunk/KDE/kdelibs/kate/syntax/data/cmake.xml?view=log

Alex
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake



Thanks. But how exactly are you adding those? By Hand or do you have  
some sort of script that parses CMake or .. ? It would be great if we  
could sync up the kate and some of the other editors to  
standardize on how the syntax coloring is broken down.


Currently I have commands, properties, cmake variables and 'reserved  
words' which is your 'special_args' section of the kate syntax xml file.


I just don't want to reinvent the wheel unless I really need to. I  
would be happy to update my XML parser to add a kate syntax xml file  
generation...


_
Mike Jackson  [EMAIL PROTECTED]
www.bluequartz.net

___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake

[CMake] [Fwd: CMake and qmake.conf?]

2008-11-18 Thread Eric (Brad) Lemings


---BeginMessage---
We've started working some with CMake here, and I've just come across a
gotcha, I think.

In the qmake.conf files for all Visual Studio compilers later than VC6,
the flag /Zc:wchar- is included.  I'm not at all sure why this is set -
someone asked this before and nobody seemed to know - but when we're
building with CMake, as far as I can tell the qmake.conf file is not
processed at all, so these flags don't get picked up.

What is the correct solution for this issue?  Should the FindQt4.cmake
module be looking at qmake.conf?  Do we need to (conditionally) set this
flag ourselves?
---End Message---
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] [Fwd: CMake and qmake.conf?]

On Nov 18, 2008, at 3:54 PM, Eric (Brad) Lemings wrote:

From: Gordon Schumacher [EMAIL PROTECTED]
Date: November 18, 2008 2:28:03 PM EST
To: Qt-Interest [EMAIL PROTECTED]
Cc: Brad Lemings [EMAIL PROTECTED]
Subject: CMake and qmake.conf?

We've started working some with CMake here, and I've just come  
across a

gotcha, I think.

In the qmake.conf files for all Visual Studio compilers later than  
VC6,
the flag /Zc:wchar- is included.  I'm not at all sure why this is  
set -

someone asked this before and nobody seemed to know - but when we're
building with CMake, as far as I can tell the qmake.conf file is not
processed at all, so these flags don't get picked up.

What is the correct solution for this issue?  Should the  
FindQt4.cmake
module be looking at qmake.conf?  Do we need to (conditionally) set  
this

flag ourselves?

You can use:

IF (NOT MSVC60)
ADD_DEFINITIONS( /Zc:wchar-)
ENDIF(NOT MSVC60)

if you know you need that. I think that should work.

___
Mike Jackson  [EMAIL PROTECTED]
BlueQuartz Softwarewww.bluequartz.net
Principal Software Engineer  Dayton, Ohio

___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] List of 'Reserved Words'

On Tuesday 18 November 2008, Michael Jackson wrote:
 On Nov 18, 2008, at 3:49 PM, Alexander Neundorf wrote:
  On Tuesday 18 November 2008, Michael Jackson wrote:
  On Nov 18, 2008, at 2:59 PM, Alexander Neundorf wrote:
  On Tuesday 18 November 2008, Michael Jackson wrote:
  Is there a list of the reserved words or Keywords for CMake.
  Examples would be:
 
  AND, NOT, OR, PROPERTIES, CACHE, FORCE..
 
  Not really.
  The one here should be quite current:
  http://websvn.kde.org/trunk/KDE/kdelibs/kate/syntax/data/cmake.xml?revi
 si on=773845view=markup
 
  Alex
 
  Cool. That was pretty close to what I was looking for but it looks
  like there are some CMake Variables in there also (WIN32). I will
  have to factor those out.
 
  I just noticed it wasn't updated for some time.
  I added some of the new stuff now.
  http://websvn.kde.org/trunk/KDE/kdelibs/kate/syntax/data/cmake.xml?view=l
 og
 
  Alex
  ___
  CMake mailing list
  CMake@cmake.org
  http://www.cmake.org/mailman/listinfo/cmake

 Thanks. But how exactly are you adding those? By Hand or do you have
 some sort of script that parses CMake or .. ? It would be great if we
 could sync up the kate and some of the other editors to
 standardize on how the syntax coloring is broken down.

Manually.
The commands and properties can be done using the cmake help 
(cmake --help-command-list etc.)
If you have something we'd surely be happy :-)

Alex
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] List of 'Reserved Words'

On Nov 18, 2008, at 4:10 PM, Alexander Neundorf wrote:

On Tuesday 18 November 2008, Michael Jackson wrote:

On Nov 18, 2008, at 3:49 PM, Alexander Neundorf wrote:

On Tuesday 18 November 2008, Michael Jackson wrote:

On Nov 18, 2008, at 2:59 PM, Alexander Neundorf wrote:

On Tuesday 18 November 2008, Michael Jackson wrote:

Is there a list of the reserved words or Keywords for CMake.
Examples would be:

AND, NOT, OR, PROPERTIES, CACHE, FORCE..

Not really.
The one here should be quite current:
http://websvn.kde.org/trunk/KDE/kdelibs/kate/syntax/data/cmake.xml?revi
si on=773845view=markup

Alex

Cool. That was pretty close to what I was looking for but it looks
like there are some CMake Variables in there also (WIN32). I will
have to factor those out.

I just noticed it wasn't updated for some time.
I added some of the new stuff now.
http://websvn.kde.org/trunk/KDE/kdelibs/kate/syntax/data/cmake.xml?view=l
og

Alex
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake

Thanks. But how exactly are you adding those? By Hand or do you
have

some sort of script that parses CMake or .. ? It would be great if we
could sync up the kate and some of the other editors to
standardize on how the syntax coloring is broken down.

Manually.
The commands and properties can be done using the cmake help
(cmake --help-command-list etc.)
If you have something we'd surely be happy :-)

Alex

I have a couple of things that might help.

There is: http://www.cmake.org/Wiki/CMake:CreateQtAssistantDocs
which I wrote to generate Qt Assistant style documentation which could
be easily changed to generate the needed xml file for kate. The
downside to this is that it would only run under MinGW or Cygwin on
windows as it is a bash script.

I have a C++ program (depends on some boost and expat) that parses the
CMake DocBook xml file and extracts out the various bits and pieces
and then generates xml or whatever based on what was read. Currently I
have it extracting out the commands, deprecated commands, properties
and cmake variables. For each of those it will also parse out the
brief documentation for the 'thing' being parsed, the usage (for
commands) and if it is deprecated or not.

If you take a look at http://cmakeed.svn.sourceforge.net/viewvc/cmakeed/trunk/com.cthing.cmakeed.core/plugin.xml?view=markup
you can see what type of XML I happen to be generating for the
CMakeEd Eclipse Plugin.

Looking at the kate syntax xml I can certainly generate that xml from
my program. I can just lump together the cmake variables, properties
and 'special arguments' into the 'special arguments' xml section of
the kate syntax xml.

I would be more than happy to contribute the code to the KDE project
under what ever license it needs to be.

_
Mike Jackson [EMAIL PROTECTED]
BlueQuartz Softwarewww.bluequartz.net
Principal Software Engineer Dayton, Ohio

___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Does CMake/CPack not support creating a source-only tarball

Tim,

Thanks, that did the trick.  Note that this tars up *everything* in the source 
tree which might actually be a good thing if you want, for example, to build 
doxygen documentation first and then tar up and distribute you code.

Thanks,

- Ross

 -Original Message-
 From: Shead, Timothy
 Sent: Tuesday, November 18, 2008 1:46 PM
 To: Bartlett, Roscoe A
 Cc: cmake@cmake.org
 Subject: Re: [CMake] Does CMake/CPack not support creating a
 source-only tarball

 Bartlett, Roscoe A wrote:

  By default, CPack supports source tarball generation with make
  source_package, and the generation can be customized in a
 variety of
  ways (e.g: generating a source package from a subdirectory with a
  custom target, etc).
 
  This target does not appear to be supported as shown by:
 
  [EMAIL PROTECTED] SERIAL_DEBUG]$ make source_package
  make: *** No rule to make target `source_package'.  Stop.
 
  Is there some special way that we need to configure
 Trilinos or set up Cpack to support this?

 Correction - it's package_source, not source_package ...

 Truly Yours,
 Tim

 --
 Timothy M. Shead
 Data Analysis  Visualization (1424)
 Sandia National Laboratories
 505-284-0139


___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Does CMake/CPack not support creating a source-only tarball

2008-11-18 Thread Timothy M. Shead


Bartlett, Roscoe A wrote:


Thanks, that did the trick.  Note that this tars up *everything* in the source 
tree which might actually be a good thing if you want, for example, to build 
doxygen documentation first and then tar up and distribute you code.


If there's something in your source dir that you *don't* want to 
distribute, you can set CPACK_SOURCE_IGNORE_FILES to a list of regex 
expressions that will be ignored.  Note that the default value for this 
variable is used to strip CVS/.svn cruft out when packaging the sources.


Cheers,
Tim

--
Timothy M. Shead
Data Analysis  Visualization (1424)
Sandia National Laboratories
505-284-0139

___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Does CMake/CPack not support creating a source-only tarball

Bingo!

 -Original Message-
 From: Shead, Timothy
 Sent: Tuesday, November 18, 2008 2:50 PM
 To: Bartlett, Roscoe A
 Cc: cmake@cmake.org
 Subject: Re: [CMake] Does CMake/CPack not support creating a
 source-only tarball

 Bartlett, Roscoe A wrote:

  Thanks, that did the trick.  Note that this tars up
 *everything* in the source tree which might actually be a
 good thing if you want, for example, to build doxygen
 documentation first and then tar up and distribute you code.

 If there's something in your source dir that you *don't* want
 to distribute, you can set CPACK_SOURCE_IGNORE_FILES to a
 list of regex expressions that will be ignored.  Note that
 the default value for this variable is used to strip CVS/.svn
 cruft out when packaging the sources.

 Cheers,
 Tim

 --
 Timothy M. Shead
 Data Analysis  Visualization (1424)
 Sandia National Laboratories
 505-284-0139

___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] INSTALL(FILES ... ) and $(OutDir): DEPENDENCIE ?

2008-11-18 Thread Mathieu Malaterre

On Tue, Nov 18, 2008 at 1:47 PM, Mathieu Malaterre
[EMAIL PROTECTED] wrote:
 David,

 On Tue, Nov 18, 2008 at 1:09 PM, David Cole [EMAIL PROTECTED] wrote:
 Looks like your definition of GDCM_LIBRARY_DIR must include
 ${CMAKE_CFG_INTDIR}. You can't use that in an install rule... rather use
 \${BUILD_TYPE} (with an escaped dollar sign) like in the VTK install
 rules...

And for the same reason I cannot have a ${CMAKE_CFG_INTDIR} in my
DEPENDS from a ADD_CUSTOM_COMMAND, correct ?

Thanks,
-- 
Mathieu
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake

[CMake] 'unset' not in --help-commands-list (also, attn: neundorf)

2008-11-18 Thread Matthew Woehlke


Need a bug opened for this or is it trivial enough to fix on the spot?

Background:
I'm taking another look at a script that auto-generates command and 
keyword lists (for a highlighter for KDE's kate). The deltas in the 
command list are all either reordering or ITK/VTK stuff... except for 
'unset', which has a --help-command entry but isn't in the commands 
list. The keywords list has quite a few more deltas, for which I may 
start either complaining or opening bugs about (especially ones I know 
are legitimate). My goal here would be to have cmake fully documented, 
meaning that all useful keywords appear in the --helpwhatever output.


@neundorf: do we really want ITK/VTK commands in the generic 
highlighter? If yes I'm going to move them to their own section; since 
cmake does not document them they get (correctly, IMO) removed from the 
main list.


--
Matthew
Please do not quote my e-mail address unobfuscated in message bodies.
--
vIMprove your life! Now on version 7!

___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] List of 'Reserved Words'

2008-11-18 Thread Matthew Woehlke


Michael Jackson wrote:
Thanks. But how exactly are you adding those? By Hand or do you have 
some sort of script that parses CMake or .. ? It would be great if we 
could sync up the kate and some of the other editors to standardize 
on how the syntax coloring is broken down.


Obviously I am behind on reading this list :-) (see the message I just 
posted about unset not listed).


I have had, for some time, a script to generate keyword lists from 
cmake's built-in help.


The meat (arg extraction) looks like this:

extract_args() {
sed -e '/'$1'(/ba' \
-e 'd' \
-e ':a' \
-e '/)/{s/^.*(\(.*\)).*$/\1/p;d}' \
-e 'N;s/\n/ /;ba' | \
sed -e 's/[][]//g' -e 's/|\| \+/\n/g' | \
sed -n '/^[[:upper:][:digit:]_]\+$/p'  $t.args
}
while read COMMAND ; do
$CMAKE --help-command $COMMAND | extract_args $COMMAND
done  $t.commands
sort $t.args | uniq  $t.argsu

I just don't want to reinvent the wheel unless I really need to. I would 
be happy to update my XML parser to add a kate syntax xml file 
generation...


Well, I'm already doing that... :-) What XML, though? Are you parsing 
'cmake --help-html'? Or is there something that clearly delineates cmake 
keywords that I don't know about?


--
Matthew
Please do not quote my e-mail address unobfuscated in message bodies.
--
vIMprove your life! Now on version 7!

___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] CTest question...

2008-11-18 Thread BRM

Any info on this? Any better resources?

TIA,

Ben



- Original Message 
From: BRM [EMAIL PROTECTED]
To: CMake cmake@cmake.org
Sent: Monday, November 17, 2008 3:14:53 AM
Subject: [CMake] CTest question...

I'd like to build a series of test using the CTest functionality in CMake.
I have added ENABLE_TESTING() to the main CMakeLists, and was hoping to put the 
tests in their own sub-directories - as follows:

/
/Tests
/Tests/object
/Tests/object/child-objects

I added the Tests directory in the root's CMakeLists.txt. I've created my first 
test (/Tests/object/objectTest) and tried adding it via ADD_TEST(objectTest 
${EXECUTABLE_OUTPUT_PATH}/objectTest}) - no parameters needed (as described by 
http://www.vtk.org/Wiki/CMake_Testing_With_CTest). However, it's unable to find 
the test when I run make test.

Note: I tried doing a MESSAGE() to find out the value of EXECUTABLE_OUTPUT_PATH 
and it seems to be NULL. Is that reall the right variable?

The documentation on ENABLE_TESTING() mentions that CTest expects files in 
build's root directory. Does that also apply to ADD_TEST()? (no mention in 
ADD_TEST()'s documentation of this).

Advice appreciated.

TIA,

Ben

___
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

Re: [CMake] List of 'Reserved Words'