Hi there,
I am confused on how to use install(files...) with VS 2008 IDE. Here
is what I wrote:
cmake
ADD_CUSTOM_COMMAND(
OUTPUT ${GDCM_LIBRARY_DIR}/gdcm_csharp.dll
COMMAND ${CMAKE_CSHARP_COMPILER} ARGS /t:library
/out:${GDCM_LIBRARY_DIR}/gdcm_csharp.dll *.cs
WORKING_DIRECTORY
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...
Cool
Hi,
As far as I understand, the scope of rules created by add_custom_target
and add_custom_command is current directory and subdirectories, whereas
the scope of targets created by add_library and add_executable are
global. Is this true? Is there a way to make a custom target/command
rule
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
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
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
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 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:
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:
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
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
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
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
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
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
---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
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
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
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
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,
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
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
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
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
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
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
On Nov 18, 2008, at 6:48 PM, Matthew Woehlke wrote:
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
Le Tue, 18 Nov 2008 15:53:25 -0800 (PST),
BRM [EMAIL PROTECTED] a écrit :
Any info on this? Any better resources?
I think we miss informations about your particular configuration.
I do use ADD_TEST with no trouble.
See more question below:
From: BRM [EMAIL PROTECTED]
To: CMake
28 matches
Mail list logo
