Re: [cmake-developers] Testing Config generator expression

2012-11-02 Thread Stephen Kelly
Brad King wrote:

 On 11/01/2012 11:45 AM, Stephen Kelly wrote:
 Ok, I've added a test for that, but as that test uses CMAKE_COMMAND too,
 with makefile generators, the result will be  each time.
 
 Okay, now I see what you meant before.  Sorry.
 
 I think just this will be sufficient (untested):
 

I wasn't able to make that work. Also any solution based on using script 
mode didn't work because I can't use add_custom_command there. 

I've added a solution based on creating top-level tests. Please let me know 
if I should merge that to next.

Thanks,

Steve.


--

Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers


[cmake-developers] [CMake 0013643]: GenerateExportHeader should work for module libraries too

2012-11-02 Thread Mantis Bug Tracker

The following issue has been SUBMITTED. 
== 
http://www.cmake.org/Bug/view.php?id=13643 
== 
Reported By:Gregoire
Assigned To:
== 
Project:CMake
Issue ID:   13643
Category:   Modules
Reproducibility:always
Severity:   minor
Priority:   normal
Status: new
== 
Date Submitted: 2012-11-02 06:13 EDT
Last Modified:  2012-11-02 06:13 EDT
== 
Summary:GenerateExportHeader should work for module
libraries too
Description: 
I am doing my tests with visual 2008 and mingw.

As far as I understand a module is like a shared library that cannot 
be linked. Instead it is dynamically loaded and then we find and use 
symbols in it. It is like doing the linker's job manually at runtime.
 
If nothing is exported from my module then I do cannot find any 
symbol in it. Or at least I do not know how to do so.
 
I modified the GenerateExportHeader module to be able to export 
symbols from my MODULE:

# if(${type} STREQUAL MODULE)
   # message(WARNING This macro should not be used with libraries of
   # type MODULE) return()
# endif()
if(NOT ${type} STREQUAL STATIC_LIBRARY AND NOT ${type} STREQUAL
SHARED_LIBRARY AND NOT ${type} STREQUAL MODULE_LIBRARY)
   message(WARNING This macro can only be used with libraries)
   return()
endif()


Steps to Reproduce: 
Build a module with visual without exported symbols.
Use depends.exe (from http://www.dependencywalker.com/) to open the generated
dll.
It will not find any symbols which means that your application won't be able to
find it either, the module is useless.
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2012-11-02 06:13 Gregoire   New Issue
==

--

Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers


Re: [cmake-developers] Testing Config generator expression

2012-11-02 Thread Brad King
On 11/02/2012 05:26 AM, Stephen Kelly wrote:
 Brad King wrote:
 I think just this will be sufficient (untested):
 
 I wasn't able to make that work. Also any solution based on using script 
 mode didn't work because I can't use add_custom_command there. 

It isn't script mode.  The patch below works for me.

-Brad


diff --git a/Tests/CMakeLists.txt b/Tests/CMakeLists.txt
index 077bbc4..c937906 100644
--- a/Tests/CMakeLists.txt
+++ b/Tests/CMakeLists.txt
@@ -556,6 +556,7 @@ ${CMake_BINARY_DIR}/bin/cmake -DVERSION=master -P 
${CMake_SOURCE_DIR}/Utilities/
 --build-generator ${CMAKE_TEST_GENERATOR}
 --build-project GeneratorExpression
 --build-makeprogram ${CMAKE_TEST_MAKEPROGRAM}
+--build-options -DCMAKE_BUILD_TYPE=\${CTEST_CONFIGURATION_TYPE}
 )
   list(APPEND TEST_BUILD_DIRS ${CMake_BINARY_DIR}/Tests/GeneratorExpression)

diff --git a/Tests/GeneratorExpression/CMakeLists.txt 
b/Tests/GeneratorExpression/CMakeLists.txt
index 581d483..3a92d81 100644
--- a/Tests/GeneratorExpression/CMakeLists.txt
+++ b/Tests/GeneratorExpression/CMakeLists.txt
@@ -19,6 +19,10 @@ add_custom_target(check ALL
 -Dtest_and_0_invalidcontent=$AND:0,invalidcontent
 -Dtest_config_0=$CONFIG:$CONFIGURATIONx
 -Dtest_config_1=$CONFIG:$CONFIGURATION
+-Dtest_config_debug=$CONFIG:Debug$CONFIG:DEBUG$CONFIG:DeBuG
+-Dtest_config_release=$CONFIG:Release$CONFIG:RELEASE$CONFIG:ReLeAsE
+
-Dtest_config_relwithdebinfo=$CONFIG:RelWithDebInfo$CONFIG:RELWITHDEBINFO$CONFIG:relwithdebinfo
+
-Dtest_config_minsizerel=$CONFIG:MinSizeRel$CONFIG:MINSIZEREL$CONFIG:minsizerel
 -Dtest_not_0=$NOT:0
 -Dtest_not_1=$NOT:1
 -Dtest_or_0=$OR:0
diff --git a/Tests/GeneratorExpression/check.cmake 
b/Tests/GeneratorExpression/check.cmake
index 88a60ce..af436de 100644
--- a/Tests/GeneratorExpression/check.cmake
+++ b/Tests/GeneratorExpression/check.cmake
@@ -18,6 +18,11 @@ check(test_and_1_1 1)
 check(test_and_0_invalidcontent 0)
 check(test_config_0 0)
 check(test_config_1 1)
+foreach(c debug release relwithdebinfo minsizerel)
+  if(NOT ${test_config_${c}} MATCHES ^(0+|1+)$)
+message(SEND_ERROR test_config_${c} is \${test_config_${c}}\, not all 0 
or all 1)
+  endif()
+endforeach()
 check(test_not_0 1)
 check(test_not_1 0)
 check(test_or_0 0)
--

Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers


Re: [cmake-developers] patch for cmake that adds a new timestamp command

2012-11-02 Thread Nils Gladitz

Thanks!

Let me know if there is anything else I can do.

Nils

On 10/31/2012 09:52 PM, David Cole wrote:
Has anybody tried this anywhere else? I'm going to merge it to 'next' 
tomorrow, so that it will get tested on the dashboards after that. 
Just curious if there are any other known problems with it that I 
should squash in before doing that...


Thanks,
David



On Tue, Oct 16, 2012 at 1:57 PM, David Cole david.c...@kitware.com 
mailto:david.c...@kitware.com wrote:


I have amended the commit and pushed this branch to the stage. If
anybody else would like to try it out they can grab the
add-timestamp-subcommands branch from the CMake stage repo.

I did not merge it to 'next' yet, but I will do that when we're ready
to get it tested on the dashboards.

Thanks for your work on this Nils.


David


On Tue, Oct 16, 2012 at 11:48 AM, Nils Gladitz glad...@sci-vis.de
mailto:glad...@sci-vis.de wrote:
 Ah that might explain it ... I may have been using nmake on
Windows and
 ninja on linux.
 Thanks!

 Nils


 On 10/16/2012 05:27 PM, David Cole wrote:

 On Tue, Oct 16, 2012 at 10:12 AM, Nils Gladitz
glad...@sci-vis.de mailto:glad...@sci-vis.de wrote:

 I certainly wouldn't mind though I'm not sure what that means.
 Do the changes in next still potentially make it into 2.8.10?

 Going into 'next' is how stuff gets tested on the dashboards,
and then
 later Brad and I merge things to 'master' when they're ready.

 After something is merged to 'master' it will be in the CMake
release
 that follows that.


 Brad mentioned this would be on the TODO list for after 2.8.10.

 We can put it in 'next' to vet it and correct any dashboard issues
 that show up (errors/warnings on other platforms, other
platform test
 failures) at any time. But it will probably not go into
'master' until
 after 2.8.10.

 We don't typically add significant features or take risky changes
 after we start doing release candidates.


 I've tried to run all tests successfully before submitting but
I can't
 tell
 if any of those were called BootstrapTest.
 Is there anything special required to run it?

 The BootstrapTest test only runs on Unix Makefiles based
builds, so
 if you're using a different generator, it does not get added as a
 test.


 Nils


 On 10/16/2012 02:49 PM, David Cole wrote:

 I had to do this to get the bootstrap version of CMake to
work (and
 the BootstrapTest to pass):

 $ git diff
 diff --git a/Source/CMakeLists.txt b/Source/CMakeLists.txt
 index 9d46355..8bf6c40 100644
 --- a/Source/CMakeLists.txt
 +++ b/Source/CMakeLists.txt
 @@ -264,8 +264,6 @@ set(SRCS
  cmTarget.cxx
  cmTarget.h
  cmTargetExport.h
 -  cmTimestamp.h
 -  cmTimestamp.cxx
  cmTest.cxx
  cmTest.h
  cmTestGenerator.cxx
 diff --git a/Source/cmBootstrapCommands.cxx
 b/Source/cmBootstrapCommands.cxx
 index 9097a74..e3a2ad4 100644
 --- a/Source/cmBootstrapCommands.cxx
 +++ b/Source/cmBootstrapCommands.cxx
 @@ -89,6 +89,7 @@
#include cmStringCommand.cxx
#include cmSubdirCommand.cxx
#include cmTargetLinkLibrariesCommand.cxx
 +#include cmTimestamp.cxx
#include cmTryCompileCommand.cxx
#include cmTryRunCommand.cxx
#include cmUnsetCommand.cxx


 After amending this, I'll push to next later today unless
somebody
 objects to this??

 Thanks,
 David



 On Fri, Oct 5, 2012 at 4:16 PM, Nils Gladitz
glad...@sci-vis.de mailto:glad...@sci-vis.de wrote:

 I've updated the patch (attached) to return empty string on
failure.
 I also tried to use the time definitions from global
namespace rather
 than
 std::.

 Nils


 On 10/05/2012 09:17 PM, Brad King wrote:

 On 10/05/2012 02:53 PM, Nils Gladitz wrote:

 My initial thought was that NOTFOUND would be a good
idea since it
 evaluates to false and the get_*_property commands also
seem to use
 it.

 I wrote the more general get_property command to replace
those and
 the newer command uses empty string rather than NOTFOUND.
 It is more
 useful when computing pieces of a string to put together,
perhaps when
 appending to a property value.

 Looking at the documentation for if() again only
-NOTFOUND as a
 suffix should evaluate to false though (I assume the
documentation is
 incomplete here?).

 Yes, thanks for pointing it out.  Fixed:

 http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=f63304d9

 On second though relying on timestamps to evaluate to false on
 failure
 is probably a bad idea 

Re: [cmake-developers] patch for cmake that adds a new timestamp command

2012-11-02 Thread David Cole
You're welcome. I decided to wait till the dashboard cleans up again
before merging this topic, but it should be in the next few days.

On Fri, Nov 2, 2012 at 10:19 AM, Nils Gladitz glad...@sci-vis.de wrote:
 Thanks!

 Let me know if there is anything else I can do.

 Nils


 On 10/31/2012 09:52 PM, David Cole wrote:

 Has anybody tried this anywhere else? I'm going to merge it to 'next'
 tomorrow, so that it will get tested on the dashboards after that. Just
 curious if there are any other known problems with it that I should squash
 in before doing that...

 Thanks,
 David



 On Tue, Oct 16, 2012 at 1:57 PM, David Cole david.c...@kitware.com wrote:

 I have amended the commit and pushed this branch to the stage. If
 anybody else would like to try it out they can grab the
 add-timestamp-subcommands branch from the CMake stage repo.

 I did not merge it to 'next' yet, but I will do that when we're ready
 to get it tested on the dashboards.

 Thanks for your work on this Nils.


 David


 On Tue, Oct 16, 2012 at 11:48 AM, Nils Gladitz glad...@sci-vis.de wrote:
  Ah that might explain it ... I may have been using nmake on Windows and
  ninja on linux.
  Thanks!
 
  Nils
 
 
  On 10/16/2012 05:27 PM, David Cole wrote:
 
  On Tue, Oct 16, 2012 at 10:12 AM, Nils Gladitz glad...@sci-vis.de
  wrote:
 
  I certainly wouldn't mind though I'm not sure what that means.
  Do the changes in next still potentially make it into 2.8.10?
 
  Going into 'next' is how stuff gets tested on the dashboards, and then
  later Brad and I merge things to 'master' when they're ready.
 
  After something is merged to 'master' it will be in the CMake release
  that follows that.
 
 
  Brad mentioned this would be on the TODO list for after 2.8.10.
 
  We can put it in 'next' to vet it and correct any dashboard issues
  that show up (errors/warnings on other platforms, other platform test
  failures) at any time. But it will probably not go into 'master' until
  after 2.8.10.
 
  We don't typically add significant features or take risky changes
  after we start doing release candidates.
 
 
  I've tried to run all tests successfully before submitting but I can't
  tell
  if any of those were called BootstrapTest.
  Is there anything special required to run it?
 
  The BootstrapTest test only runs on Unix Makefiles based builds, so
  if you're using a different generator, it does not get added as a
  test.
 
 
  Nils
 
 
  On 10/16/2012 02:49 PM, David Cole wrote:
 
  I had to do this to get the bootstrap version of CMake to work (and
  the BootstrapTest to pass):
 
  $ git diff
  diff --git a/Source/CMakeLists.txt b/Source/CMakeLists.txt
  index 9d46355..8bf6c40 100644
  --- a/Source/CMakeLists.txt
  +++ b/Source/CMakeLists.txt
  @@ -264,8 +264,6 @@ set(SRCS
   cmTarget.cxx
   cmTarget.h
   cmTargetExport.h
  -  cmTimestamp.h
  -  cmTimestamp.cxx
   cmTest.cxx
   cmTest.h
   cmTestGenerator.cxx
  diff --git a/Source/cmBootstrapCommands.cxx
  b/Source/cmBootstrapCommands.cxx
  index 9097a74..e3a2ad4 100644
  --- a/Source/cmBootstrapCommands.cxx
  +++ b/Source/cmBootstrapCommands.cxx
  @@ -89,6 +89,7 @@
 #include cmStringCommand.cxx
 #include cmSubdirCommand.cxx
 #include cmTargetLinkLibrariesCommand.cxx
  +#include cmTimestamp.cxx
 #include cmTryCompileCommand.cxx
 #include cmTryRunCommand.cxx
 #include cmUnsetCommand.cxx
 
 
  After amending this, I'll push to next later today unless
  somebody
  objects to this??
 
  Thanks,
  David
 
 
 
  On Fri, Oct 5, 2012 at 4:16 PM, Nils Gladitz glad...@sci-vis.de
  wrote:
 
  I've updated the patch (attached) to return empty string on failure.
  I also tried to use the time definitions from global namespace
  rather
  than
  std::.
 
  Nils
 
 
  On 10/05/2012 09:17 PM, Brad King wrote:
 
  On 10/05/2012 02:53 PM, Nils Gladitz wrote:
 
  My initial thought was that NOTFOUND would be a good idea since
  it
  evaluates to false and the get_*_property commands also seem to
  use
  it.
 
  I wrote the more general get_property command to replace those
  and
  the newer command uses empty string rather than NOTFOUND.  It is
  more
  useful when computing pieces of a string to put together, perhaps
  when
  appending to a property value.
 
  Looking at the documentation for if() again only -NOTFOUND as
  a
  suffix should evaluate to false though (I assume the documentation
  is
  incomplete here?).
 
  Yes, thanks for pointing it out.  Fixed:
 
  http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=f63304d9
 
  On second though relying on timestamps to evaluate to false on
  failure
  is probably a bad idea since I could have a format string of e.g.
  %w
  (day of the week) which might produce a valid timestamp 0 which
  would
  also evaluate to false.
 
  Yes, so a comparison against  would be more reliable.
 
  Thanks,
  -Brad
 
 
 
  --
  Nils Gladitz, B.Sc.
  DICOM, Konnektivität und Entwicklung
 
  Scivis wissenschaftliche Bildverarbeitung 

[cmake-developers] [CMake 0013644]: Default pdb output location changed in cmake 2.8.10

2012-11-02 Thread Mantis Bug Tracker

The following issue has been SUBMITTED. 
== 
http://www.cmake.org/Bug/view.php?id=13644 
== 
Reported By:Reid Kleckner
Assigned To:
== 
Project:CMake
Issue ID:   13644
Category:   CMake
Reproducibility:always
Severity:   minor
Priority:   normal
Status: new
== 
Date Submitted: 2012-11-02 10:49 EDT
Last Modified:  2012-11-02 10:49 EDT
== 
Summary:Default pdb output location changed in cmake 2.8.10
Description: 
In the course of adding PDB_OUTPUT_DIRECTORY and related properties and
variables, the default location for pdb files changed.

In our project (DynamoRIO) we have a bunch of targets where we set
RUNTIME_OUTPUT_DIRECTORY, LIBRARY_OUTPUT_DIRECTORY, etc.  The .pdb file would
get created in ${RUNTIME_OUTPUT_DIRECTORY} next to the .dll, which is what we
want.  After this change, it would get created in the default output directory,
which is different.  Furthermore, this would mean the pdbs never got installed.

Our CMake code:
set_target_properties(dynamorio PROPERTIES
  LIBRARY_OUTPUT_DIRECTORY${location_suffix} ${DR_LIBRARY_OUTPUT_DIRECTORY}
  RUNTIME_OUTPUT_DIRECTORY${location_suffix} ${DR_LIBRARY_OUTPUT_DIRECTORY}
  ARCHIVE_OUTPUT_DIRECTORY${location_suffix} ${DR_LIBRARY_OUTPUT_DIRECTORY}
  # The next line is the one I added to work around the problem.
  #PDB_OUTPUT_DIRECTORY${location_suffix} ${DR_LIBRARY_OUTPUT_DIRECTORY}
  )

From the linker command line:
/out:lib32\debug\dynamorio.dll
/implib:lib32\debug\dynamorio.lib
/pdb:core\dynamorio.pdb

We can easily work around the problem by setting PDB_OUTPUT_DIRECTORY as well as
RUNTIME, ARCHIVE, and LIBRARY, but it'd be nice for other users that aren't
using cmake from version control if the default didn't change.

Upstream issue where we figured this out:
http://code.google.com/p/chromium/issues/detail?id=159092

Original issue:
http://www.cmake.org/Bug/view.php?id=10830

CMake commit that made the change:
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=3f60dbf1

Steps to Reproduce: 
1. Create a library target
2. Set the runtime and archive output directory to somewhere non-default
3. Build it
4. Observe that the pdb does not reside next to the dll
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2012-11-02 10:49 Reid Kleckner  New Issue
==

--

Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers


[cmake-developers] [CMake 0013645]: Regression: FindOpenSSL doesn't find anything for MSVC

2012-11-02 Thread Mantis Bug Tracker

The following issue has been SUBMITTED. 
== 
http://www.cmake.org/Bug/view.php?id=13645 
== 
Reported By:Thomas Sondergaard
Assigned To:
== 
Project:CMake
Issue ID:   13645
Category:   Modules
Reproducibility:always
Severity:   minor
Priority:   normal
Status: new
== 
Date Submitted: 2012-11-02 14:23 EDT
Last Modified:  2012-11-02 14:23 EDT
== 
Summary:Regression: FindOpenSSL doesn't find anything for
MSVC
Description: 
The use of select_library_configurations from SelectLibraryConfigurations.cmake
is broken. The variables defined with find_library have the wrong names e.g.
LIB_EAY_DEBUG should be LIB_EAY_LIBRARY_DEBUG.

Also, with MSVC libeay32d.lib and ssleay32d.lib are no longer recognized - only
libeay32MDd.lib and ssleay32MDd
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2012-11-02 14:23 Thomas SondergaardNew Issue
==

--

Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers


[cmake-developers] [CMake 0013646]: Automoc doesn't recognise #if QT_VERSION = x anymore

2012-11-02 Thread Mantis Bug Tracker

The following issue has been SUBMITTED. 
== 
http://www.cmake.org/Bug/view.php?id=13646 
== 
Reported By:Dominik Schmidt
Assigned To:
== 
Project:CMake
Issue ID:   13646
Category:   CMake
Reproducibility:always
Severity:   minor
Priority:   normal
Status: new
== 
Date Submitted: 2012-11-02 17:37 EDT
Last Modified:  2012-11-02 17:37 EDT
== 
Summary:Automoc doesn't recognise #if QT_VERSION = x
anymore
Description: 
With the latest release of CMake compilation of Tomahawk Player stopped working
for us because automoc stopped producing output for a certain file.

Obviously code ifdef'ed by #if QT_VERSION = 0x040400 isn't scanned anymore.

The commit that fixed building for us:
https://github.com/tomahawk-player/tomahawk/commit/c910e1b58f01a42b9f99222e501172576d8cad06

Steps to Reproduce: 
Put code in #if QT_VERSION = 0x040400 and run automoc on it.

Additional Information: 
Of course I'm talking about CMake built in automoc, not automoc4 from KDE.
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2012-11-02 17:37 Dominik SchmidtNew Issue
==

--

Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers


Re: [CMake] How to pack a target/file into multiple packages in Linux?

2012-11-02 Thread Eric Noulard
2012/11/2 Ralph Zhang ralph.j.zh...@gmail.com:
 Hi guys

 I'm working on a project which generates quite a few executables, libraries
 and configs, they need to be packed into different packages for deployment.
 The problem is, the inclusion of those targets/files is not mutual
 exclusive. One target/file can belong to multiple packages.

 I'm using CMake 2.8.9 and trying CPack.

Which cpack generator are you targeting? NSIS, PackageMaker, RPM, DEB, ZIP?

 I know it's kind of doable with
 install types. But my platform is Ubuntu, so on Archives/Debs are acceptable
 and they don't seem to support that.

 With components/groups/parent groups it seems only possible to pack one
 target/file into one component/group.

 Is there any way out of this?

I bet that currently you'll have to run cpack as many time as you have packages.

1) Define the components that you need

2) Define CPACK_INSTALL_CMAKE_PROJECTS (and possibly other CPACK_xxx)
variables when launching CPack (could be done using a custom command)
Using this var you can decide which component will be installed so
that you can
include/exclude component.
You may override CPACK_COMPONENTS_ALL as well.

this can be done on the command line
cpack -D CPACK_INSTALL_CMAKE_PROJECTS=...

or from within a CPACK_PROJECT_CONFIG_FILE.

more info:
cpack --help-variable CPACK_COMPONENTS_ALL
cpack --help-variable CPACK_INSTALL_CMAKE_PROJECTS
cpack --help-variable CPACK_PROJECT_CONFIG_FILE


-- 
Erk
Le gouvernement représentatif n'est pas la démocratie --
http://www.le-message.org
--

Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake


Re: [CMake] Change RPATH at the packaging stage

2012-11-02 Thread Eric Noulard
2012/11/1 Vyacheslav Karamov ubuntul...@yandex.ru:
 Hi All!

 Is it possible to change rpath at the packaging stage?

CPack is using cmake_install.cmake scripts which gets influenced
by CMAKE_INSTALL_RPATH variable and/or INSTALL_RPATH target property.

Did you try to play with that? i.e.

SET(CMAKE_INSTALL_RPATH /opt/chatterbox)

you may try to set this in a CPACK_PROJECT_CONFIG_FILE
in order to set it to a CPack-time specific value.

That said I'm not sure it'll work because I don't know for sure when exactly
CMAKE_INSTALL_RPATH is processed, but iit's simple to try.


 I have CMake based project with CPack directives in its CMake script:

  if(${CMAKE_SYSTEM_NAME} STREQUAL Linux AND EXISTS 
 ${CMAKE_ROOT}/Modules/CPack.cmake)

 SET(install_dir /opt/chatterbox)

 SET(CMAKE_SKIP_BUILD_RPATH TRUE)

 SET(CMAKE_BUILD_WITH_INSTALL_RPATH TRUE)

 SET(CMAKE_INSTALL_RPATH /usr/local/lib)

 SET(CMAKE_INSTALL_RPATH_USE_LINK_PATH FALSE)

 ...
 endif()
 --

 Powered by www.kitware.com

 Visit other Kitware open-source projects at 
 http://www.kitware.com/opensource/opensource.html

 Please keep messages on-topic and check the CMake FAQ at: 
 http://www.cmake.org/Wiki/CMake_FAQ

 Follow this link to subscribe/unsubscribe:
 http://www.cmake.org/mailman/listinfo/cmake



-- 
Erk
Le gouvernement représentatif n'est pas la démocratie --
http://www.le-message.org
--

Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake


Re: [CMake] CMake 2.8.10 available for download

2012-11-02 Thread David Cole
The scripts that buld the CMake release binaries are in CMake/Utilities/Release.

If you have a system-installed OpenSSL, then setting the cache
variable CMAKE_USE_OPENSSL should be sufficient.

If not, and you have a custom built openssl, you need to set the
following variables as well:

CMAKE_USE_OPENSSL:BOOL=ON
OPENSSL_CRYPTO_LIBRARY:FILEPATH=/path/to/openssl-1.0.1c-install/lib/libcrypto.a
OPENSSL_INCLUDE_DIR:PATH=/path/to/openssl-1.0.1c-install/include
OPENSSL_SSL_LIBRARY:FILEPATH=/path/to/openssl-1.0.1c-install/lib/libssl.a

If you still have problems after this, send along whatever error
message you're getting...


HTH,
David


On Fri, Nov 2, 2012 at 12:24 AM, Orion Poplawski or...@cora.nwra.com wrote:
 On 10/31/2012 07:45 PM, David Cole wrote:

 On behalf of myself, Ken, Bill, Brad, Alex, Eike, Steve, Eric, Zach,
 Ben and the rest of the CMake team from all around the world, we are
 pleased to announce that CMake 2.8.10 is now available for download
 at:

http://www.cmake.org/files/v2.8/?C=M;O=D

 It is also available from the usual download links found on the CMake web
 site:

http://www.cmake.org/cmake/resources/software.html

 Some of the notable changes in this release are:

   - file(DOWNLOAD now handles https URLs -- the pre-built binaries
 available from Kitware link to OpenSSL


 What is required to enable this when building cmake?  It does not appear
 that:

 ../bootstrap --prefix=/usr --datadir=/share/cmake
 --docdir=/share/doc/cmake-2.8.10 --mandir=/share/man --system-libs
 --parallel=2 --qt-gui -- -DCMAKE_USE_OPENSSL=TRUE

 is sufficient.

 TIA,

   Orion

 --
 Orion Poplawski
 Technical Manager 303-415-9701 x222
 NWRA/CoRA DivisionFAX: 303-415-9702
 3380 Mitchell Lane  or...@cora.nwra.com
 Boulder, CO 80301  http://www.cora.nwra.com
--

Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake


Re: [CMake] Disabling Argument Parsing in CMake -P Scripts

2012-11-02 Thread David Cole
-- for script mode is a good idea. (Actually, if we had this for
non-script mode even, it would then make sense to expose the command
line arguments in similar variables even when configuring a CMakeLists
file. Presently, the CMAKE_ARGVn vars are only available in script
mode.)

Can you propose a patch?

If so, open a feature request in the bug tracker, and attach a git
format-patch -1 file.

Thanks,
David


On Fri, Nov 2, 2012 at 12:21 AM, Eskandar Ensafi
ens...@spacecomputer.com wrote:
 Hello,

 I often find it very useful to run CMake scripts of the form cmake -P 
 script-name arg1 arg2 ... as a cross-platform scripting solution that 
 doesn't rely on Perl, Python, etc.  One major limitation is that CMake 
 continues to parse all arguments after the script name.  For example, if arg1 
 is -i then CMake will enter wizard mode before executing the script, and 
 options such as -D, -G and -L will be parsed and removed from the 
 command-line by CMake.  The current behavior limits the flexibility of 
 CMake's script mode by making it impossible to pass arbitrary options to be 
 parsed directly by the script.

 It would be great if I could somehow specify cmake -P script-name -- arg1 
 arg2 ... to tell CMake to stop parsing all subsequent arguments while still 
 placing arg1, arg2, etc. in the CMAKE_ARGVn variables.  If the -- flag is 
 potentially problematic and may pose compatibility problems, perhaps another 
 syntax can be adopted, such as cmake -PP script-name arg1 arg2 ... where -P 
 is doubled.

 Is this something that can be easily implemented?

 Best,

 Eskandar
 --

 Powered by www.kitware.com

 Visit other Kitware open-source projects at 
 http://www.kitware.com/opensource/opensource.html

 Please keep messages on-topic and check the CMake FAQ at: 
 http://www.cmake.org/Wiki/CMake_FAQ

 Follow this link to subscribe/unsubscribe:
 http://www.cmake.org/mailman/listinfo/cmake
--

Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake


Re: [CMake] GenerateExportHeader for module library

2012-11-02 Thread Gregoire Aujay
Hello,

I filed a bug: http://www.cmake.org/Bug/view.php?id=13643

Regards,

Gregoire

-Original Message-
From: cmake-boun...@cmake.org [mailto:cmake-boun...@cmake.org] On Behalf Of 
Clinton Stimpson
Sent: jeudi 1 novembre 2012 15:05
To: Stephen Kelly
Cc: cmake@cmake.org
Subject: Re: [CMake] GenerateExportHeader for module library


On Nov 1, 2012, at 8:01 AM, Stephen Kelly wrote:

 Gregoire Aujay wrote:
 
 Hello,
 
 I am doing my tests with visual 2008 and mingw.
 
 As far as I understand a module is like a shared library that cannot 
 be linked. Instead it is dynamically loaded and then we find and use 
 symbols in it. It is like doing the linker's job manually at runtime.
 
 If nothing is exported from my module then I do cannot find any 
 symbol in it. Or at least I do not know how to do so.
 
 I modified the GenerateExportHeader module to be able to export 
 symbols from my MODULE:
 
  # if(${type} STREQUAL MODULE)
# message(WARNING This macro should not be used with libraries of
# type MODULE) return()
  # endif()
  if(NOT ${type} STREQUAL STATIC_LIBRARY AND NOT ${type} STREQUAL  
 SHARED_LIBRARY AND NOT ${type} STREQUAL MODULE_LIBRARY)
message(WARNING This macro can only be used with libraries)
return()
  endif()
 
 
 Regards,
 
 Gregoire
 
 
 Please file a bug report so that this is not forgotten. 
 
 Ideally also provide some code to test it. I'm not familiar with how 
 plugins should be loaded in a cross-platform way (without Qt, that is).
 

Perhaps the BundleUtilities test can be modified to use GenerateExportHeader if 
you need some coverage.
It also loads plugins at runtime (without Qt).

Clint

--

Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake


--

Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake


Re: [CMake] SWIG generated .cxx file location issue.

2012-11-02 Thread Hugh Sorby

Hi,

I'm still having problems with this.  It seems my swig is not creating 
the output directory for the swig generated cxx file.  To get this to 
work I have had to add a further make_directory command to the custom 
command to create the required output directory before the file is swigged.


I have done some testing and I cannot get any swig output if the .i file 
is not in the same directory as the CMakeLists.txt file.  Any ideas?


For reference:

cmake version 2.8.10
swig 2.0.8


On 09/27/12 09:42, felix wrote:

Hm strange.
I use the swigmodule a lot and it creates my .cxx files in the binary-dir;
but I have no relative path in the name of the
interface file.

Have you tried to use an absolute path like

set(SRC_FILE ${CMAKE_SOURCE_DIR}/swig/interface/context.i)

?
Relative paths are always a little bit cumbersome; what happens if your
build tree is far away from the source tree?

Felix



--
View this message in context: 
http://cmake.3232098.n2.nabble.com/SWIG-generated-cxx-file-location-issue-tp7581826p7581836.html
Sent from the CMake mailing list archive at Nabble.com.
--

Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake


--

Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake


[CMake] Get corefile from timed out tests with ctest?

2012-11-02 Thread Leif Walsh
When a test times out, I want to inspect its state to look for deadlocks. Is 
there a way to get ctest to save a corefile from a process it kills due to 
timing out? Is there a way to configure it to use a custom signal that I can 
catch in my tests?

I may have asked this before. I remember ctest uses uncatchable signals to kill 
tests in the event of a timeout. 

Sent from my iPhone 
--

Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake


Re: [CMake] Change RPATH at the packaging stage

2012-11-02 Thread Vyacheslav Karamov

Thank you very much, Eric!
It works!

--- CMakeLists.txt --

include (FindSubversion)

if (NOT Subversion_FOUND)
message(FATAL_ERROR Please install subversion command-line client and 
add its folder to the system PATH)

endif()

# Update working copy at every non-debug build
if (NOT (CMAKE_BUILD_TYPE STREQUAL Debug))

add_custom_target(svn_up ALL
# update the working copy
COMMAND ${Subversion_SVN_EXECUTABLE} up ${CMAKE_SOURCE_DIR}
)

endif() # if (NOT (CMAKE_BUILD_TYPE STREQUAL Debug))

# Add code which adds svn revision info at every build

Subversion_WC_INFO(${CMAKE_SOURCE_DIR} ${CMAKE_PROJECT_NAME})

set(chatterbox_revision ${${CMAKE_PROJECT_NAME}_WC_REVISION})

# set product version
set (chatterbox_version_major 1)
set (chatterbox_version_minor 0)
set (chatterbox_version_patch 0)
set (chatterbox_version ${chatterbox_version_major}, 
${chatterbox_version_minor}, ${chatterbox_version_patch}, 
${chatterbox_revision})


set(version_h_contents /**
* Copyright (c) 2008-2012 Transparent Language, Inc. All rights reserved.
*/
#define _VESRION_NUMBER_ ${chatterbox_version}
#define _PRODUCT_NUMBER_ ${chatterbox_version}
#define _VERSION_STRING_ \${chatterbox_version}\
#define _PRODUCT_STRING_ \${chatterbox_version}\
)

#Write version.h
file(WRITE ${CMAKE_CURRENT_SOURCE_DIR}/chatterbox/src/version.h 
${version_h_contents})


set (package_version 
${chatterbox_version_major}.${chatterbox_version_minor}.${chatterbox_version_patch})


add_custom_target(configure_cpack ALL
# generate cpackoptions.cmake at build time so we get the
# most recent revision number
COMMAND ${CMAKE_COMMAND}
-DSOURCE_DIR=${CMAKE_SOURCE_DIR}
-Dproj_name=${CMAKE_PROJECT_NAME}
-Drevision=${chatterbox_revision}
-Dpack_version=${package_version}
-P ${CMAKE_SOURCE_DIR}/cmake/Create-cpackoptions.cmake
)

if (NOT (CMAKE_BUILD_TYPE STREQUAL Debug))
add_dependencies(configure_cpack svn_up)
endif()

set(CPACK_PROJECT_CONFIG_FILE ${CMAKE_SOURCE_DIR}/cmake/CPackOptions.cmake)

--- CMakeLists.txt --


---Create-cpackoptions.cmake--

configure_file(${SOURCE_DIR}/cmake/CPackOptions.cmake.in
${SOURCE_DIR}/cmake/CPackOptions.cmake
@ONLY)

---Create-cpackoptions.cmake--


--CPackOptions.cmake.in---

SET(CMAKE_INSTALL_RPATH /opt/@proj_name@)
set(CPACK_PACKAGE_VERSION @pack_version@)
set(CPACK_PACKAGE_FILE_NAME 
@proj_name@-${CPACK_PACKAGE_VERSION}r@revision@-${CPACK_SYSTEM_NAME})


--CPackOptions.cmake.in---

02.11.2012 11:06, Eric Noulard пишет:

2012/11/1 Vyacheslav Karamov ubuntul...@yandex.ru:

Hi All!

Is it possible to change rpath at the packaging stage?

CPack is using cmake_install.cmake scripts which gets influenced
by CMAKE_INSTALL_RPATH variable and/or INSTALL_RPATH target property.

Did you try to play with that? i.e.

SET(CMAKE_INSTALL_RPATH /opt/chatterbox)

you may try to set this in a CPACK_PROJECT_CONFIG_FILE
in order to set it to a CPack-time specific value.

That said I'm not sure it'll work because I don't know for sure when exactly
CMAKE_INSTALL_RPATH is processed, but iit's simple to try.



I have CMake based project with CPack directives in its CMake script:

  if(${CMAKE_SYSTEM_NAME} STREQUAL Linux AND EXISTS 
${CMAKE_ROOT}/Modules/CPack.cmake)

 SET(install_dir /opt/chatterbox)

 SET(CMAKE_SKIP_BUILD_RPATH TRUE)

 SET(CMAKE_BUILD_WITH_INSTALL_RPATH TRUE)

 SET(CMAKE_INSTALL_RPATH /usr/local/lib)

 SET(CMAKE_INSTALL_RPATH_USE_LINK_PATH FALSE)

...
endif()
--

Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake





--

Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Change RPATH at the packaging stage

2012-11-02 Thread Vyacheslav Karamov

Oh, that is some kind of special street magic!

RPATH is empty without these lines in CMakeLists.txt

set(CPACK_PROJECT_CONFIG_FILE ${CMAKE_SOURCE_DIR}/cmake/CPackOptions.cmake)

if(${CMAKE_SYSTEM_NAME} STREQUAL Linux AND EXISTS 
${CMAKE_ROOT}/Modules/CPack.cmake)


set(CPACK_PACKAGING_INSTALL_PREFIX ${install_dir})
set(CMAKE_INSTALL_RPATH ${install_dir})
endif()



02.11.2012 16:40, Vyacheslav Karamov пишет:

Thank you very much, Eric!
It works!

--- CMakeLists.txt --

include (FindSubversion)

if (NOT Subversion_FOUND)
message(FATAL_ERROR Please install subversion command-line client and 
add its folder to the system PATH)

endif()

# Update working copy at every non-debug build
if (NOT (CMAKE_BUILD_TYPE STREQUAL Debug))

add_custom_target(svn_up ALL
# update the working copy
COMMAND ${Subversion_SVN_EXECUTABLE} up ${CMAKE_SOURCE_DIR}
)

endif() # if (NOT (CMAKE_BUILD_TYPE STREQUAL Debug))

# Add code which adds svn revision info at every build

Subversion_WC_INFO(${CMAKE_SOURCE_DIR} ${CMAKE_PROJECT_NAME})

set(chatterbox_revision ${${CMAKE_PROJECT_NAME}_WC_REVISION})

# set product version
set (chatterbox_version_major 1)
set (chatterbox_version_minor 0)
set (chatterbox_version_patch 0)
set (chatterbox_version ${chatterbox_version_major}, 
${chatterbox_version_minor}, ${chatterbox_version_patch}, 
${chatterbox_revision})


set(version_h_contents /**
* Copyright (c) 2008-2012 Transparent Language, Inc. All rights reserved.
*/
#define _VESRION_NUMBER_ ${chatterbox_version}
#define _PRODUCT_NUMBER_ ${chatterbox_version}
#define _VERSION_STRING_ \${chatterbox_version}\
#define _PRODUCT_STRING_ \${chatterbox_version}\
)

#Write version.h
file(WRITE ${CMAKE_CURRENT_SOURCE_DIR}/chatterbox/src/version.h 
${version_h_contents})


set (package_version 
${chatterbox_version_major}.${chatterbox_version_minor}.${chatterbox_version_patch})


add_custom_target(configure_cpack ALL
# generate cpackoptions.cmake at build time so we get the
# most recent revision number
COMMAND ${CMAKE_COMMAND}
-DSOURCE_DIR=${CMAKE_SOURCE_DIR}
-Dproj_name=${CMAKE_PROJECT_NAME}
-Drevision=${chatterbox_revision}
-Dpack_version=${package_version}
-P ${CMAKE_SOURCE_DIR}/cmake/Create-cpackoptions.cmake
)

if (NOT (CMAKE_BUILD_TYPE STREQUAL Debug))
add_dependencies(configure_cpack svn_up)
endif()

set(CPACK_PROJECT_CONFIG_FILE 
${CMAKE_SOURCE_DIR}/cmake/CPackOptions.cmake)


--- CMakeLists.txt --


---Create-cpackoptions.cmake--

configure_file(${SOURCE_DIR}/cmake/CPackOptions.cmake.in
${SOURCE_DIR}/cmake/CPackOptions.cmake
@ONLY)

---Create-cpackoptions.cmake--


--CPackOptions.cmake.in---

SET(CMAKE_INSTALL_RPATH /opt/@proj_name@)
set(CPACK_PACKAGE_VERSION @pack_version@)
set(CPACK_PACKAGE_FILE_NAME 
@proj_name@-${CPACK_PACKAGE_VERSION}r@revision@-${CPACK_SYSTEM_NAME})


--CPackOptions.cmake.in---

02.11.2012 11:06, Eric Noulard пишет:

2012/11/1 Vyacheslav Karamov ubuntul...@yandex.ru:

Hi All!

Is it possible to change rpath at the packaging stage?

CPack is using cmake_install.cmake scripts which gets influenced
by CMAKE_INSTALL_RPATH variable and/or INSTALL_RPATH target property.

Did you try to play with that? i.e.

SET(CMAKE_INSTALL_RPATH /opt/chatterbox)

you may try to set this in a CPACK_PROJECT_CONFIG_FILE
in order to set it to a CPack-time specific value.

That said I'm not sure it'll work because I don't know for sure when 
exactly

CMAKE_INSTALL_RPATH is processed, but iit's simple to try.



I have CMake based project with CPack directives in its CMake script:

  if(${CMAKE_SYSTEM_NAME} STREQUAL Linux AND EXISTS 
${CMAKE_ROOT}/Modules/CPack.cmake)


 SET(install_dir /opt/chatterbox)

 SET(CMAKE_SKIP_BUILD_RPATH TRUE)

 SET(CMAKE_BUILD_WITH_INSTALL_RPATH TRUE)

 SET(CMAKE_INSTALL_RPATH /usr/local/lib)

 SET(CMAKE_INSTALL_RPATH_USE_LINK_PATH FALSE)

...
endif()
--

Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html


Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ


Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake





--

Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html


Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ


Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake


--

Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake

[CMake] CMake 2.8.10 to MacPorts

2012-11-02 Thread Gary Little
Is any time frame when CMake 2.8.10 will be added to MacPorts?

And to put my time where my mouth is, m ay I be of assistance? Are there files 
I can acquire that would allow me to do add it?

Gary Little
H (952) 223-1349
C (952) 454-4629 
gglit...@comcast.net

--

Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] CMake 2.8.10 to MacPorts

2012-11-02 Thread Bradley Giesbrecht
On Nov 2, 2012, at 9:29 AM, Gary Little wrote:

 Is any time frame when CMake 2.8.10 will be added to MacPorts?
 
 And to put my time where my mouth is, m ay I be of assistance? Are there 
 files I can acquire that would allow me to do add it?

This question is probably better asked on the MacPorts User or Dev mailing list.
http://trac.macports.org/wiki/MailingLists


Search MacPorts trac for a cmake 2.8.10 enhancement ticket.
If not found open an enhancement ticket requesting version update.
Follow ticket guidelines here like cc maintainer:
http://trac.macports.org/wiki/TracTickets

To attach a patch to the ticket grab the current Portfile from your tree or 
here:
https://trac.macports.org/browser/trunk/dports/devel/cmake/Portfile

Make your changes and attache a unified diff (diff -u) to the ticket. If you 
are going to attach a patch add haspatch to the ticket keyword field.
Is all in the ticket guidelines.


Regards,
Bradley Giesbrecht (pixilla)



smime.p7s
Description: S/MIME cryptographic signature
--

Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Change RPATH at the packaging stage

2012-11-02 Thread Rolf Eike Beer
Vyacheslav Karamov wrote:
 Thank you very much, Eric!
 It works!
 
 --- CMakeLists.txt --
 
 include (FindSubversion)
 
 if (NOT Subversion_FOUND)
 message(FATAL_ERROR Please install subversion command-line client and
 add its folder to the system PATH)
 endif()

This can be done simpler:

find_package(Subversion REQUIRED)

Eike
-- 


signature.asc
Description: This is a digitally signed message part.
--

Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake

[CMake] Change in behaviour (regression?) in automoc in latest CMake

2012-11-02 Thread Dominik Schmidt

Moin!

With the latest release of CMake compilation of Tomahawk Player stopped 
working for us because automoc stopped producing output for a certain file.


Obviously code ifdef'ed by #if QT_VERSION = 0x040400 isn't scanned 
anymore. Is that on purpose?


Best regards,
Dominik

P.S.: Commit that fixed building our master: 
https://github.com/tomahawk-player/tomahawk/commit/c910e1b58f01a42b9f99222e501172576d8cad06 


--

Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake


Re: [CMake] Change in behaviour (regression?) in automoc in latest CMake

2012-11-02 Thread Bill Hoffman

On 11/2/2012 5:00 PM, Dominik Schmidt wrote:

With the latest release of CMake compilation of Tomahawk Player stopped
working

Why can't people try the rc releases :(

We put them out there so that stuff can get fixed before the release. 
Any ideas on how to get projects to try the rc's to avoid this sort of 
regression...


-Bill


--

Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake


Re: [CMake] Change in behaviour (regression?) in automoc in latest CMake

2012-11-02 Thread Dominik Schmidt
On 02.11.2012 22:14, Bill Hoffman wrote: On 11/2/2012 5:00 PM, Dominik 
Schmidt wrote:

 With the latest release of CMake compilation of Tomahawk Player stopped
 working
 Why can't people try the rc releases

 We put them out there so that stuff can get fixed before the release.
 Any ideas on how to get projects to try the rc's to avoid this sort of
 regression...

 -Bill

Maybe because we're an open source project without paid contributors and 
everyone only has limited spare time?


Anyways I promise to test next RC releases


Shall I file a bug for this?


Regards,
Domme


P.S.: sorry, Bill, I keep clicking Reply instead of Reply List ...
--

Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake


Re: [CMake] Change in behaviour (regression?) in automoc in latest CMake

2012-11-02 Thread Rolf Eike Beer
Bill Hoffman wrote:
 On 11/2/2012 5:00 PM, Dominik Schmidt wrote:
  With the latest release of CMake compilation of Tomahawk Player stopped
  working
 
 Why can't people try the rc releases :(
 
 We put them out there so that stuff can get fixed before the release.
 Any ideas on how to get projects to try the rc's to avoid this sort of
 regression...

Call them releases and do the real release 2 weeks later.

Eike
-- 


signature.asc
Description: This is a digitally signed message part.
--

Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Change in behaviour (regression?) in automoc in latest CMake

2012-11-02 Thread Dominik Schmidt
On 02.11.2012 22:26, Bill Hoffman wrote: On 11/2/2012 5:18 PM, Dominik 
Schmidt wrote:

 Anyways I promise to test next RC releases :-)

 That would be great.   It was half rant/ half what do we have to do? 
 It just seems that people find the time as soon as the real release 
 comes out.  Of course by that time it is too late, and the release is 
 flawed.


It wasn't even us finding that out :-)

We got a report by a user and were clueless ourselves at first, someone 
else found out it broke with the new CMake release, then I started to 
investigate what exactly broke.


 Shall I file a bug for this?

 Yes, sounds like a bug.


 Thanks.

Will do.



On 02.11.2012 22:24, Rolf Eike Beer wrote: Bill Hoffman wrote:
 Call them releases and do the real release 2 weeks later.

 Eike

Yeah, arch would have put it in their repos earlier then ;-)


Regards,
Domme
--

Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake


Re: [CMake] Change in behaviour (regression?) in automoc in latest CMake

2012-11-02 Thread Matthew Woehlke

On 2012-11-02 17:14, Bill Hoffman wrote:

On 11/2/2012 5:00 PM, Dominik Schmidt wrote:

With the latest release of CMake compilation of Tomahawk Player stopped
working

Why can't people try the rc releases :(

We put them out there so that stuff can get fixed before the release.
Any ideas on how to get projects to try the rc's to avoid this sort of
regression...


Getting distros to include RC's in their updates-testing stream might 
help...


--
Matthew

--

Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake


Re: [CMake] Disabling Argument Parsing in CMake -P Scripts

2012-11-02 Thread Eskandar Ensafi
I'm not sure if I'm qualified to propose a patch, but I will look at the source 
code to see what I can come up with.  I have additional concerns about the way 
the CMAKE_ARGVn variables are initialized, and this might be a good time to 
address these concerns.

I don't know if this was a design choice, but with some exceptions, CMake seems 
to first parse the entire command-line, and then it runs each -P script in 
order, with CMAKE_ARGC/ARGVn initialized to the entire command-line, not just 
the arguments following the appropriate -P script.  When the command-line is 
parsed, some recognized options are removed (e.g. -L[A][H], -N) with no ill 
effect, others are removed but interfere with the initialization of 
CMAKE_ARGC/ARGVn (e.g. --help, --version, and all variants), and some are 
parsed but NOT removed (e.g. -D name:type=value, -G generator, contrary to 
comments in my previous e-mail).  A more robust treatment of these command-line 
arguments would be to fail with an error if incompatible combinations of 
options are detected, and if any options are recognized and parsed by CMake, 
they should be removed from the command-line.  Parsing errors should cause to 
CMake to exit with an error, but this is not consistent (-G fails given a bogus
  generator, but -D with a badly formed argument allows CMake to continue).

To demonstrate, take the following simple example:

# MyScript.cmake
MESSAGE( BEGIN SCRIPT )
IF (DEFINED MyVar)
  MESSAGE(MyVar = ${MyVar})
ENDIF()
MESSAGE(CMAKE_ARGC = ${CMAKE_ARGC})
MATH(EXPR ARGC ${CMAKE_ARGC} - 1)
FOREACH(I RANGE 0 ${ARGC})
  MESSAGE(CMAKE_ARGV${I} = ${CMAKE_ARGV${I}})
ENDFOREACH()
MESSAGE( END SCRIPT )

Then run it as follows:

cmake -P MyScript.cmake testing -DMyVar=Test one two three -P MyScript.cmake 
four five six

 BEGIN SCRIPT 
CMAKE_ARGC = 13
CMAKE_ARGV0 = cmake
CMAKE_ARGV1 = -P
CMAKE_ARGV2 = MyScript.cmake
CMAKE_ARGV3 = testing
CMAKE_ARGV4 = -DMyVar=Test
CMAKE_ARGV5 = one
CMAKE_ARGV6 = two
CMAKE_ARGV7 = three
CMAKE_ARGV8 = -P
CMAKE_ARGV9 = MyScript.cmake
CMAKE_ARGV10 = four
CMAKE_ARGV11 = five
CMAKE_ARGV12 = six
 END SCRIPT 
 BEGIN SCRIPT 
MyVar = Test
CMAKE_ARGC = 13
CMAKE_ARGV0 = cmake
CMAKE_ARGV1 = -P
CMAKE_ARGV2 = MyScript.cmake
CMAKE_ARGV3 = testing
CMAKE_ARGV4 = -DMyVar=Test
CMAKE_ARGV5 = one
CMAKE_ARGV6 = two
CMAKE_ARGV7 = three
CMAKE_ARGV8 = -P
CMAKE_ARGV9 = MyScript.cmake
CMAKE_ARGV10 = four
CMAKE_ARGV11 = five
CMAKE_ARGV12 = six
 END SCRIPT 

Notice how the entire command-line, including intervening -P options and the 
parsed -D option, is made available to both scripts (i.e. they are both 
executed with the same CMAKE_ARGC/ARGVn even though CMAKE_ARGV7 was the last 
argument for the first script, and CMAKE_ARGV10 to CMAKE_ARGV12 were the 
arguments for the second script).  This may or may not be useful, but to avoid 
breaking compatibility, I propose defining something like CMAKE_ARGC_FIRST and 
CMAKE_ARGC_LAST in each -P script invocation so that we can determine the range 
of options specific to the script being executed.

Now, if we deliberately introduce an error in the -D flag as follows:

cmake -P MyScript.cmake testing -DMyVar one two three -P MyScript.cmake four 
five six

Then CMake will run the first script, and it will exit with an error when it 
tries to parse -DMyVar (missing value).

Since implementing a -- option will require some changes to CMake's 
command-line parsing logic, I suggest that we fix the aforementioned issues as 
part of this effort.  Again, I am not the best person to undertake this effort 
due to my lack of familiarity with the CMake code base, but if someone with 
more experience would like to collaborate with me, I would be more than happy 
to help.

Best,

Eskandar


On Nov 2, 2012, at 2:45 AM, David Cole wrote:

 -- for script mode is a good idea. (Actually, if we had this for
 non-script mode even, it would then make sense to expose the command
 line arguments in similar variables even when configuring a CMakeLists
 file. Presently, the CMAKE_ARGVn vars are only available in script
 mode.)
 
 Can you propose a patch?
 
 If so, open a feature request in the bug tracker, and attach a git
 format-patch -1 file.
 
 Thanks,
 David
 
 
 On Fri, Nov 2, 2012 at 12:21 AM, Eskandar Ensafi
 ens...@spacecomputer.com wrote:
 Hello,
 
 I often find it very useful to run CMake scripts of the form cmake -P 
 script-name arg1 arg2 ... as a cross-platform scripting solution that 
 doesn't rely on Perl, Python, etc.  One major limitation is that CMake 
 continues to parse all arguments after the script name.  For example, if 
 arg1 is -i then CMake will enter wizard mode before executing the script, 
 and options such as -D, -G and -L will be parsed and removed from the 
 command-line by CMake.  The current behavior limits the flexibility of 
 CMake's script mode by making it impossible to pass arbitrary options to be 
 parsed directly by the script.
 
 It would be great if I could somehow specify cmake -P script-name -- arg1 
 

Re: [CMake] Disabling Argument Parsing in CMake -P Scripts

2012-11-02 Thread David Cole
On Fri, Nov 2, 2012 at 5:44 PM, Eskandar Ensafi
ens...@spacecomputer.com wrote:
 I'm not sure if I'm qualified to propose a patch, but I will look at the 
 source code to see what I can come up with.  I have additional concerns about 
 the way the CMAKE_ARGVn variables are initialized, and this might be a good 
 time to address these concerns.

 I don't know if this was a design choice, but with some exceptions, CMake 
 seems to first parse the entire command-line, and then it runs each -P script 
 in order, with CMAKE_ARGC/ARGVn initialized to the entire command-line, not 
 just the arguments following the appropriate -P script.  When the 
 command-line is parsed, some recognized options are removed (e.g. -L[A][H], 
 -N) with no ill effect, others are removed but interfere with the 
 initialization of CMAKE_ARGC/ARGVn (e.g. --help, --version, and all 
 variants), and some are parsed but NOT removed (e.g. -D name:type=value, -G 
 generator, contrary to comments in my previous e-mail).  A more robust 
 treatment of these command-line arguments would be to fail with an error if 
 incompatible combinations of options are detected, and if any options are 
 recognized and parsed by CMake, they should be removed from the command-line. 
  Parsing errors should cause to CMake to exit with an error, but this is not 
 consistent (-G fails given a bog
 us generator, but -D with a badly formed argument allows CMake to continue).

 To demonstrate, take the following simple example:

 # MyScript.cmake
 MESSAGE( BEGIN SCRIPT )
 IF (DEFINED MyVar)
   MESSAGE(MyVar = ${MyVar})
 ENDIF()
 MESSAGE(CMAKE_ARGC = ${CMAKE_ARGC})
 MATH(EXPR ARGC ${CMAKE_ARGC} - 1)
 FOREACH(I RANGE 0 ${ARGC})
   MESSAGE(CMAKE_ARGV${I} = ${CMAKE_ARGV${I}})
 ENDFOREACH()
 MESSAGE( END SCRIPT )

 Then run it as follows:

 cmake -P MyScript.cmake testing -DMyVar=Test one two three -P MyScript.cmake 
 four five six

 BEGIN SCRIPT 
 CMAKE_ARGC = 13
 CMAKE_ARGV0 = cmake
 CMAKE_ARGV1 = -P
 CMAKE_ARGV2 = MyScript.cmake
 CMAKE_ARGV3 = testing
 CMAKE_ARGV4 = -DMyVar=Test
 CMAKE_ARGV5 = one
 CMAKE_ARGV6 = two
 CMAKE_ARGV7 = three
 CMAKE_ARGV8 = -P
 CMAKE_ARGV9 = MyScript.cmake
 CMAKE_ARGV10 = four
 CMAKE_ARGV11 = five
 CMAKE_ARGV12 = six
  END SCRIPT 
 BEGIN SCRIPT 
 MyVar = Test
 CMAKE_ARGC = 13
 CMAKE_ARGV0 = cmake
 CMAKE_ARGV1 = -P
 CMAKE_ARGV2 = MyScript.cmake
 CMAKE_ARGV3 = testing
 CMAKE_ARGV4 = -DMyVar=Test
 CMAKE_ARGV5 = one
 CMAKE_ARGV6 = two
 CMAKE_ARGV7 = three
 CMAKE_ARGV8 = -P
 CMAKE_ARGV9 = MyScript.cmake
 CMAKE_ARGV10 = four
 CMAKE_ARGV11 = five
 CMAKE_ARGV12 = six
  END SCRIPT 

 Notice how the entire command-line, including intervening -P options and the 
 parsed -D option, is made available to both scripts (i.e. they are both 
 executed with the same CMAKE_ARGC/ARGVn even though CMAKE_ARGV7 was the last 
 argument for the first script, and CMAKE_ARGV10 to CMAKE_ARGV12 were the 
 arguments for the second script).  This may or may not be useful, but to 
 avoid breaking compatibility, I propose defining something like 
 CMAKE_ARGC_FIRST and CMAKE_ARGC_LAST in each -P script invocation so that we 
 can determine the range of options specific to the script being executed.

 Now, if we deliberately introduce an error in the -D flag as follows:

 cmake -P MyScript.cmake testing -DMyVar one two three -P MyScript.cmake four 
 five six

 Then CMake will run the first script, and it will exit with an error when it 
 tries to parse -DMyVar (missing value).

 Since implementing a -- option will require some changes to CMake's 
 command-line parsing logic, I suggest that we fix the aforementioned issues 
 as part of this effort.  Again, I am not the best person to undertake this 
 effort due to my lack of familiarity with the CMake code base, but if someone 
 with more experience would like to collaborate with me, I would be more than 
 happy to help.

 Best,

 Eskandar


 On Nov 2, 2012, at 2:45 AM, David Cole wrote:

 -- for script mode is a good idea. (Actually, if we had this for
 non-script mode even, it would then make sense to expose the command
 line arguments in similar variables even when configuring a CMakeLists
 file. Presently, the CMAKE_ARGVn vars are only available in script
 mode.)

 Can you propose a patch?

 If so, open a feature request in the bug tracker, and attach a git
 format-patch -1 file.

 Thanks,
 David


 On Fri, Nov 2, 2012 at 12:21 AM, Eskandar Ensafi
 ens...@spacecomputer.com wrote:
 Hello,

 I often find it very useful to run CMake scripts of the form cmake -P 
 script-name arg1 arg2 ... as a cross-platform scripting solution that 
 doesn't rely on Perl, Python, etc.  One major limitation is that CMake 
 continues to parse all arguments after the script name.  For example, if 
 arg1 is -i then CMake will enter wizard mode before executing the script, 
 and options such as -D, -G and -L will be parsed and removed from the 
 command-line by CMake.  The current behavior limits the flexibility of 
 CMake's script mode by 

[Cmake-commits] CMake branch, next, updated. v2.8.10-694-gc024b9e

2012-11-02 Thread Stephen Kelly
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.

The branch, next has been updated
   via  c024b9ecd0352a3f87168ec821169a7ce1dc8fbf (commit)
   via  d9c16eb0ff56126e81934f153ca6934535d33e51 (commit)
  from  3573b4485cb8cc027a4e56a0e02849b093acbcfb (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=c024b9ecd0352a3f87168ec821169a7ce1dc8fbf
commit c024b9ecd0352a3f87168ec821169a7ce1dc8fbf
Merge: 3573b44 d9c16eb
Author: Stephen Kelly steve...@gmail.com
AuthorDate: Fri Nov 2 08:17:52 2012 -0400
Commit: CMake Topic Stage kwro...@kitware.com
CommitDate: Fri Nov 2 08:17:52 2012 -0400

Merge topic 'generator-expression-bug-fixes' into next

d9c16eb Use case insensitive comparison for the $CONFIG expression.


http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=d9c16eb0ff56126e81934f153ca6934535d33e51
commit d9c16eb0ff56126e81934f153ca6934535d33e51
Author: Stephen Kelly steve...@gmail.com
AuthorDate: Thu Nov 1 14:21:25 2012 +0100
Commit: Stephen Kelly steve...@gmail.com
CommitDate: Fri Nov 2 13:16:29 2012 +0100

Use case insensitive comparison for the $CONFIG expression.

This fixes a regression introduced by commit f1eacf0e 
(cmGeneratorExpression:
Re-write for multi-stage evaluation)

diff --git a/Source/cmGeneratorExpressionEvaluator.cxx 
b/Source/cmGeneratorExpressionEvaluator.cxx
index 287066a..03173e6 100644
--- a/Source/cmGeneratorExpressionEvaluator.cxx
+++ b/Source/cmGeneratorExpressionEvaluator.cxx
@@ -16,6 +16,8 @@
 #include cmGeneratorExpressionDAGChecker.h
 #include cmGeneratorExpression.h
 
+#include cmsys/String.h
+
 //
 #if !defined(__SUNPRO_CC) || __SUNPRO_CC  0x510
 static
@@ -253,7 +255,8 @@ static const struct ConfigurationTestNode : public 
cmGeneratorExpressionNode
   return parameters.front().empty() ? 1 : 0;
   }
 
-return *parameters.begin() == context-Config ? 1 : 0;
+return cmsysString_strcasecmp(parameters.begin()-c_str(),
+  context-Config) == 0 ? 1 : 0;
   }
 } configurationTestNode;
 
diff --git a/Tests/CMakeLists.txt b/Tests/CMakeLists.txt
index b404333..bbf804b 100644
--- a/Tests/CMakeLists.txt
+++ b/Tests/CMakeLists.txt
@@ -556,6 +556,7 @@ ${CMake_BINARY_DIR}/bin/cmake -DVERSION=master -P 
${CMake_SOURCE_DIR}/Utilities/
 --build-generator ${CMAKE_TEST_GENERATOR}
 --build-project GeneratorExpression
 --build-makeprogram ${CMAKE_TEST_MAKEPROGRAM}
+--build-options -DCMAKE_BUILD_TYPE=\${CTEST_CONFIGURATION_TYPE}
 )
   list(APPEND TEST_BUILD_DIRS ${CMake_BINARY_DIR}/Tests/GeneratorExpression)
 
diff --git a/Tests/GeneratorExpression/CMakeLists.txt 
b/Tests/GeneratorExpression/CMakeLists.txt
index 581d483..3a92d81 100644
--- a/Tests/GeneratorExpression/CMakeLists.txt
+++ b/Tests/GeneratorExpression/CMakeLists.txt
@@ -19,6 +19,10 @@ add_custom_target(check ALL
 -Dtest_and_0_invalidcontent=$AND:0,invalidcontent
 -Dtest_config_0=$CONFIG:$CONFIGURATIONx
 -Dtest_config_1=$CONFIG:$CONFIGURATION
+-Dtest_config_debug=$CONFIG:Debug$CONFIG:DEBUG$CONFIG:DeBuG
+-Dtest_config_release=$CONFIG:Release$CONFIG:RELEASE$CONFIG:ReLeAsE
+
-Dtest_config_relwithdebinfo=$CONFIG:RelWithDebInfo$CONFIG:RELWITHDEBINFO$CONFIG:relwithdebinfo
+
-Dtest_config_minsizerel=$CONFIG:MinSizeRel$CONFIG:MINSIZEREL$CONFIG:minsizerel
 -Dtest_not_0=$NOT:0
 -Dtest_not_1=$NOT:1
 -Dtest_or_0=$OR:0
diff --git a/Tests/GeneratorExpression/check.cmake 
b/Tests/GeneratorExpression/check.cmake
index 88a60ce..af436de 100644
--- a/Tests/GeneratorExpression/check.cmake
+++ b/Tests/GeneratorExpression/check.cmake
@@ -18,6 +18,11 @@ check(test_and_1_1 1)
 check(test_and_0_invalidcontent 0)
 check(test_config_0 0)
 check(test_config_1 1)
+foreach(c debug release relwithdebinfo minsizerel)
+  if(NOT ${test_config_${c}} MATCHES ^(0+|1+)$)
+message(SEND_ERROR test_config_${c} is \${test_config_${c}}\, not all 0 
or all 1)
+  endif()
+endforeach()
 check(test_not_0 1)
 check(test_not_1 0)
 check(test_or_0 0)

---

Summary of changes:
 Source/cmGeneratorExpressionEvaluator.cxx |5 -
 Tests/CMakeLists.txt  |1 +
 Tests/GeneratorExpression/CMakeLists.txt  |4 
 Tests/GeneratorExpression/check.cmake |5 +
 4 files changed, 14 insertions(+), 1 deletions(-)


hooks/post-receive
-- 
CMake
___
Cmake-commits mailing list
Cmake-commits@cmake.org
http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-commits


[Cmake-commits] CMake branch, next, updated. v2.8.10-697-g0baf436

2012-11-02 Thread Brad King
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.

The branch, next has been updated
   via  0baf4365ba53001e3d528d67c46a6926cc675b37 (commit)
   via  3673b96507199da13b0726e57491b4ee46f86330 (commit)
   via  424fb9589f408a06f499ed038043554f70666df2 (commit)
  from  c024b9ecd0352a3f87168ec821169a7ce1dc8fbf (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=0baf4365ba53001e3d528d67c46a6926cc675b37
commit 0baf4365ba53001e3d528d67c46a6926cc675b37
Merge: c024b9e 3673b96
Author: Brad King brad.k...@kitware.com
AuthorDate: Fri Nov 2 08:28:28 2012 -0400
Commit: CMake Topic Stage kwro...@kitware.com
CommitDate: Fri Nov 2 08:28:28 2012 -0400

Merge topic 'fix-KWSys-SystemInformation' into next

3673b96 KWSys: Fix SystemInformation on FreeBSD
424fb95 Revert KWSys: In SystemInformation use netdb.h only where 
available


http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=3673b96507199da13b0726e57491b4ee46f86330
commit 3673b96507199da13b0726e57491b4ee46f86330
Author: Richard Wackerbarth rich...@nfsnet.org
AuthorDate: Fri Nov 2 08:26:04 2012 -0400
Commit: Brad King brad.k...@kitware.com
CommitDate: Fri Nov 2 08:26:04 2012 -0400

KWSys: Fix SystemInformation on FreeBSD

Add missing includes for this platform.

diff --git a/Source/kwsys/SystemInformation.cxx 
b/Source/kwsys/SystemInformation.cxx
index 7612138..83dedfd 100644
--- a/Source/kwsys/SystemInformation.cxx
+++ b/Source/kwsys/SystemInformation.cxx
@@ -74,6 +74,14 @@ typedef int siginfo_t;
 # include errno.h // extern int errno;
 #endif
 
+#ifdef __FreeBSD__
+# include sys/sysctl.h
+# include fenv.h
+# include sys/socket.h
+# include netdb.h
+# include netinet/in.h
+#endif
+
 #ifdef __APPLE__
 # include sys/sysctl.h
 # include mach/vm_statistics.h

http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=424fb9589f408a06f499ed038043554f70666df2
commit 424fb9589f408a06f499ed038043554f70666df2
Author: Brad King brad.k...@kitware.com
AuthorDate: Fri Nov 2 08:24:40 2012 -0400
Commit: Brad King brad.k...@kitware.com
CommitDate: Fri Nov 2 08:24:40 2012 -0400

Revert KWSys: In SystemInformation use netdb.h only where available

This reverts commit 7bc06080fff9e151a0bc09ac59ea5a5f7a4bb2f1.

diff --git a/Source/kwsys/CMakeLists.txt b/Source/kwsys/CMakeLists.txt
index bc133fd..777d76f 100644
--- a/Source/kwsys/CMakeLists.txt
+++ b/Source/kwsys/CMakeLists.txt
@@ -582,11 +582,6 @@ IF(KWSYS_USE_SystemInformation)
   SET_PROPERTY(SOURCE SystemInformation.cxx APPEND PROPERTY
 COMPILE_DEFINITIONS KWSYS_SYS_HAS_IFADDRS_H=1)
 ENDIF()
-CHECK_INCLUDE_FILES(sys/types.h;netdb.h KWSYS_SYS_HAS_NETDB_H)
-IF(KWSYS_SYS_HAS_NETDB_H)
-  SET_PROPERTY(SOURCE SystemInformation.cxx APPEND PROPERTY
-COMPILE_DEFINITIONS KWSYS_SYS_HAS_NETDB_H=1)
-ENDIF()
   ENDIF()
   IF(WIN32)
 INCLUDE(CheckSymbolExists)
diff --git a/Source/kwsys/SystemInformation.cxx 
b/Source/kwsys/SystemInformation.cxx
index c5b6655..7612138 100644
--- a/Source/kwsys/SystemInformation.cxx
+++ b/Source/kwsys/SystemInformation.cxx
@@ -82,6 +82,7 @@ typedef int siginfo_t;
 # include mach/mach_types.h
 # include fenv.h
 # include sys/socket.h
+# include netdb.h
 # include netinet/in.h
 # if __ENVIRONMENT_MAC_OS_X_VERSION_MIN_REQUIRED__-0 = 1050
 #  include execinfo.h
@@ -92,6 +93,7 @@ typedef int siginfo_t;
 #ifdef __linux
 # include fenv.h
 # include sys/socket.h
+# include netdb.h
 # include netinet/in.h
 # if defined(__GNUG__)
 #  include execinfo.h
@@ -114,9 +116,6 @@ typedef struct rlimit ResourceLimitType;
 #if defined(KWSYS_SYS_HAS_IFADDRS_H)
 # include ifaddrs.h
 #endif
-#if defined(KWSYS_SYS_HAS_NETDB_H)
-# include netdb.h
-#endif
 
 #ifdef __HAIKU__
 # include OS.h
@@ -1274,7 +1273,7 @@ int 
SystemInformationImplementation::GetFullyQualifiedDomainName(
   WSACleanup();
   return 0;
 
-#elif defined(KWSYS_SYS_HAS_IFADDRS_H)  defined(KWSYS_SYS_HAS_NETDB_H)
+#elif defined(KWSYS_SYS_HAS_IFADDRS_H)
   // gethostname typical returns an alias for loopback interface
   // we want the fully qualified domain name. Because there are
   // any number of interfaces on this system we look for the

---

Summary of changes:
 Source/kwsys/CMakeLists.txt|5 -
 Source/kwsys/SystemInformation.cxx |   15 +++
 2 files changed, 11 insertions(+), 9 deletions(-)


hooks/post-receive
-- 
CMake
___
Cmake-commits mailing list
Cmake-commits@cmake.org
http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-commits


[Cmake-commits] CMake branch, next, updated. v2.8.10-700-g108910e

2012-11-02 Thread Brad King
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.

The branch, next has been updated
   via  108910ed07828f4d919572bbc613f82b6d196564 (commit)
   via  2ca56fd86c22fb1c65eca1c0cb6c37d467884813 (commit)
   via  53c3de07c7d9c4cc99a7cf0deaf228f563ba8d06 (commit)
  from  0baf4365ba53001e3d528d67c46a6926cc675b37 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=108910ed07828f4d919572bbc613f82b6d196564
commit 108910ed07828f4d919572bbc613f82b6d196564
Merge: 0baf436 2ca56fd
Author: Brad King brad.k...@kitware.com
AuthorDate: Fri Nov 2 08:29:46 2012 -0400
Commit: CMake Topic Stage kwro...@kitware.com
CommitDate: Fri Nov 2 08:29:46 2012 -0400

Merge topic 'fix-KWSys-SystemInformation' into next

2ca56fd KWSys: Fix SystemInformation on FreeBSD
53c3de0 KWSys: In SystemInformation skip backtrace on LSB  4.1


http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=2ca56fd86c22fb1c65eca1c0cb6c37d467884813
commit 2ca56fd86c22fb1c65eca1c0cb6c37d467884813
Author: Richard Wackerbarth rich...@nfsnet.org
AuthorDate: Fri Nov 2 08:26:04 2012 -0400
Commit: Brad King brad.k...@kitware.com
CommitDate: Fri Nov 2 08:29:26 2012 -0400

KWSys: Fix SystemInformation on FreeBSD

Add missing includes for this platform.

diff --git a/Source/kwsys/SystemInformation.cxx 
b/Source/kwsys/SystemInformation.cxx
index 7612138..83dedfd 100644
--- a/Source/kwsys/SystemInformation.cxx
+++ b/Source/kwsys/SystemInformation.cxx
@@ -74,6 +74,14 @@ typedef int siginfo_t;
 # include errno.h // extern int errno;
 #endif
 
+#ifdef __FreeBSD__
+# include sys/sysctl.h
+# include fenv.h
+# include sys/socket.h
+# include netdb.h
+# include netinet/in.h
+#endif
+
 #ifdef __APPLE__
 # include sys/sysctl.h
 # include mach/vm_statistics.h

http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=53c3de07c7d9c4cc99a7cf0deaf228f563ba8d06
commit 53c3de07c7d9c4cc99a7cf0deaf228f563ba8d06
Author: Brad King brad.k...@kitware.com
AuthorDate: Thu Nov 1 10:46:18 2012 -0400
Commit: Brad King brad.k...@kitware.com
CommitDate: Fri Nov 2 08:29:26 2012 -0400

KWSys: In SystemInformation skip backtrace on LSB  4.1

The backtrace API was added in LSB 4.1 but does not exist in 4.0.

diff --git a/Source/kwsys/SystemInformation.cxx 
b/Source/kwsys/SystemInformation.cxx
index 8d2d191..7612138 100644
--- a/Source/kwsys/SystemInformation.cxx
+++ b/Source/kwsys/SystemInformation.cxx
@@ -97,7 +97,9 @@ typedef int siginfo_t;
 # include netinet/in.h
 # if defined(__GNUG__)
 #  include execinfo.h
-#  define KWSYS_SYSTEMINFORMATION_HAVE_BACKTRACE
+#  if !(defined(__LSB_VERSION__)  __LSB_VERSION__  41)
+#   define KWSYS_SYSTEMINFORMATION_HAVE_BACKTRACE
+#  endif
 # endif
 # if defined(KWSYS_CXX_HAS_RLIMIT64)
 typedef struct rlimit64 ResourceLimitType;

---

Summary of changes:


hooks/post-receive
-- 
CMake
___
Cmake-commits mailing list
Cmake-commits@cmake.org
http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-commits


[Cmake-commits] CMake branch, next, updated. v2.8.10-710-g6596b62

2012-11-02 Thread Rolf Eike Beer
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.

The branch, next has been updated
   via  6596b6248fad49fcc70fafcb83352cf30df31179 (commit)
   via  828d4f514d04eb522e70173ac1e4f6790fac1460 (commit)
   via  82106e3783b8c9a5f21f7ffea336c38b1f13c33f (commit)
   via  56125a3f363272568c578c7e329af37d97b24df0 (commit)
   via  48ed48f7ad4c2da8037e997129b5ae8923ab7268 (commit)
   via  c2a6cb64af7fdb0e31d5c0781cbd0dabb4197b5a (commit)
   via  07251a8ea5322f957adfcbb2fffb6c5ca121418c (commit)
   via  1b078c304db63eb6cd46fe0f22988f8241a389b2 (commit)
   via  f560977540215e533c5360e1ab84dd0846d18310 (commit)
   via  d211e5d20324783b7c5eb06725dda08c12c41787 (commit)
  from  108910ed07828f4d919572bbc613f82b6d196564 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=6596b6248fad49fcc70fafcb83352cf30df31179
commit 6596b6248fad49fcc70fafcb83352cf30df31179
Merge: 108910e 828d4f5
Author: Rolf Eike Beer e...@sf-mail.de
AuthorDate: Fri Nov 2 12:31:26 2012 -0400
Commit: CMake Topic Stage kwro...@kitware.com
CommitDate: Fri Nov 2 12:31:26 2012 -0400

Merge topic 'start-contributing-irc-session' into next

828d4f5 Add several get_property() tests
82106e3 GetProperty test: move doc property tests into main process
56125a3 list: add tests for CMP0007 behavior
48ed48f Add test to secure the file(GLOB empty) behavior.
c2a6cb6 file: remove dead code
07251a8 Consolidate list() argument count testing
1b078c3 Add tests for list() invalid arguments
f560977 Add tests for list() argument count
d211e5d CMakeTests: allow to call the check_cmake_test macro with a given 
file


http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=828d4f514d04eb522e70173ac1e4f6790fac1460
commit 828d4f514d04eb522e70173ac1e4f6790fac1460
Author: Petr Kmoch petr.km...@gmail.com
AuthorDate: Wed Oct 3 17:09:09 2012 +0200
Commit: Rolf Eike Beer e...@sf-mail.de
CommitDate: Fri Nov 2 17:10:07 2012 +0100

Add several get_property() tests

Add tests for some get_property() uses not covered by existing tests.

diff --git a/Tests/CMakeTests/GetPropertyTest.cmake.in 
b/Tests/CMakeTests/GetPropertyTest.cmake.in
index 7d6e013..306ab72 100644
--- a/Tests/CMakeTests/GetPropertyTest.cmake.in
+++ b/Tests/CMakeTests/GetPropertyTest.cmake.in
@@ -11,6 +11,23 @@ if (NOT FOO_FULL STREQUAL NOTFOUND)
   message(SEND_ERROR property FOO has FULL_DOCS set to '${FOO_FULL}')
 endif ()
 
+get_property(test_brief GLOBAL PROPERTY ENABLED_FEATURES BRIEF_DOCS)
+get_property(test_full GLOBAL PROPERTY ENABLED_FEATURES FULL_DOCS)
+
+if(test_brief STREQUAL NOTFOUND)
+  message(SEND_ERROR property ENABLED_FEATURES has no BRIEF_DOCS)
+endif()
+
+if(test_full STREQUAL NOTFOUND)
+  message(SEND_ERROR property ENABLED_FEATURES has no FULL_DOCS)
+endif()
+
+set(test_var alpha)
+get_property(result VARIABLE PROPERTY test_var)
+if(NOT result STREQUAL alpha)
+  message(SEND_ERROR bad value of VARIABLE PROPERTY test_var: got '${result}' 
instead of 'alpha')
+endif()
+
 set(Missing-Argument-RESULT 1)
 set(Missing-Argument-STDERR .*CMake Error at 
(@CMAKE_CURRENT_SOURCE_DIR@/)?GetProperty-Missing-Argument.cmake:1 
\\(get_property\\):.*get_property called with incorrect number of arguments.*)
 

http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=82106e3783b8c9a5f21f7ffea336c38b1f13c33f
commit 82106e3783b8c9a5f21f7ffea336c38b1f13c33f
Author: Rolf Eike Beer e...@sf-mail.de
AuthorDate: Mon Oct 8 19:31:59 2012 +0200
Commit: Rolf Eike Beer e...@sf-mail.de
CommitDate: Fri Nov 2 17:10:07 2012 +0100

GetProperty test: move doc property tests into main process

They will not raise an error in the normal case so we do not need to run 
them
in their own process.

diff --git a/Tests/CMakeTests/GetProperty-Doc-Properties.cmake 
b/Tests/CMakeTests/GetProperty-Doc-Properties.cmake
deleted file mode 100644
index 6c2c362..000
--- a/Tests/CMakeTests/GetProperty-Doc-Properties.cmake
+++ /dev/null
@@ -1,10 +0,0 @@
-get_property(FOO_BRIEF GLOBAL PROPERTY FOO BRIEF_DOCS)
-get_property(FOO_FULL GLOBAL PROPERTY FOO FULL_DOCS)
-
-if (NOT FOO_BRIEF STREQUAL NOTFOUND)
-  message(SEND_ERROR property FOO has BRIEF_DOCS set to '${FOO_BRIEF}')
-endif ()
-
-if (NOT FOO_FULL STREQUAL NOTFOUND)
-  message(SEND_ERROR property FOO has FULL_DOCS set to '${FOO_FULL}')
-endif ()
diff --git a/Tests/CMakeTests/GetPropertyTest.cmake.in 
b/Tests/CMakeTests/GetPropertyTest.cmake.in
index ab96e5b..7d6e013 100644
--- a/Tests/CMakeTests/GetPropertyTest.cmake.in
+++ b/Tests/CMakeTests/GetPropertyTest.cmake.in
@@ -1,5 +1,16 @@
 

[Cmake-commits] CMake branch, next, updated. v2.8.10-712-g2d354f7

2012-11-02 Thread Rolf Eike Beer
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.

The branch, next has been updated
   via  2d354f79c91b48d351ea737b190ca396be1630fc (commit)
   via  2272a596096980780eb2c7da7d22359e047df52d (commit)
  from  6596b6248fad49fcc70fafcb83352cf30df31179 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=2d354f79c91b48d351ea737b190ca396be1630fc
commit 2d354f79c91b48d351ea737b190ca396be1630fc
Merge: 6596b62 2272a59
Author: Rolf Eike Beer e...@sf-mail.de
AuthorDate: Fri Nov 2 15:41:50 2012 -0400
Commit: CMake Topic Stage kwro...@kitware.com
CommitDate: Fri Nov 2 15:41:50 2012 -0400

Merge topic 'fix-openssl-win' into next

2272a59 FindOpenSSL: fix library selection on Windows (#13645)


http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=2272a596096980780eb2c7da7d22359e047df52d
commit 2272a596096980780eb2c7da7d22359e047df52d
Author: Rolf Eike Beer e...@sf-mail.de
AuthorDate: Fri Nov 2 20:41:37 2012 +0100
Commit: Rolf Eike Beer e...@sf-mail.de
CommitDate: Fri Nov 2 20:41:37 2012 +0100

FindOpenSSL: fix library selection on Windows (#13645)

diff --git a/Modules/FindOpenSSL.cmake b/Modules/FindOpenSSL.cmake
index e2cc427..1f6d58c 100644
--- a/Modules/FindOpenSSL.cmake
+++ b/Modules/FindOpenSSL.cmake
@@ -127,6 +127,11 @@ if(WIN32 AND NOT CYGWIN)
 lib/VC
 )
 
+set(LIB_EAY_LIBRARY_DEBUG ${LIB_EAY_DEBUG})
+set(LIB_EAY_LIBRARY_RELEASE ${LIB_EAY_RELEASE})
+set(SSL_EAY_LIBRARY_DEBUG ${SSL_EAY_DEBUG})
+set(SSL_EAY_LIBRARY_RELEASE ${SSL_EAY_RELEASE})
+
 include(${CMAKE_CURRENT_LIST_DIR}/SelectLibraryConfigurations.cmake)
 select_library_configurations(LIB_EAY)
 select_library_configurations(SSL_EAY)

---

Summary of changes:
 Modules/FindOpenSSL.cmake |5 +
 1 files changed, 5 insertions(+), 0 deletions(-)


hooks/post-receive
-- 
CMake
___
Cmake-commits mailing list
Cmake-commits@cmake.org
http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-commits


[Cmake-commits] CMake branch, next, updated. v2.8.10-714-gafe04cd

2012-11-02 Thread Rolf Eike Beer
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.

The branch, next has been updated
   via  afe04cdb3ddd4645e456e7b129466e782a31649e (commit)
   via  fb44b3374be48edd56e2c86818b55bb5ecef4500 (commit)
  from  2d354f79c91b48d351ea737b190ca396be1630fc (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=afe04cdb3ddd4645e456e7b129466e782a31649e
commit afe04cdb3ddd4645e456e7b129466e782a31649e
Merge: 2d354f7 fb44b33
Author: Rolf Eike Beer e...@sf-mail.de
AuthorDate: Fri Nov 2 19:01:07 2012 -0400
Commit: CMake Topic Stage kwro...@kitware.com
CommitDate: Fri Nov 2 19:01:07 2012 -0400

Merge topic 'fix-openssl-win' into next

fb44b33 FindOpenSSL: also find the non-MD debug libraries for MSVC


http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=fb44b3374be48edd56e2c86818b55bb5ecef4500
commit fb44b3374be48edd56e2c86818b55bb5ecef4500
Author: Rolf Eike Beer e...@sf-mail.de
AuthorDate: Fri Nov 2 23:59:08 2012 +0100
Commit: Rolf Eike Beer e...@sf-mail.de
CommitDate: Fri Nov 2 23:59:08 2012 +0100

FindOpenSSL: also find the non-MD debug libraries for MSVC

We already search for them in release mode.

diff --git a/Modules/FindOpenSSL.cmake b/Modules/FindOpenSSL.cmake
index 1f6d58c..224c88e 100644
--- a/Modules/FindOpenSSL.cmake
+++ b/Modules/FindOpenSSL.cmake
@@ -87,6 +87,7 @@ if(WIN32 AND NOT CYGWIN)
 find_library(LIB_EAY_DEBUG
   NAMES
 libeay32MDd
+libeay32d
   ${_OPENSSL_ROOT_HINTS_AND_PATHS}
   PATH_SUFFIXES
 lib
@@ -108,6 +109,7 @@ if(WIN32 AND NOT CYGWIN)
 find_library(SSL_EAY_DEBUG
   NAMES
 ssleay32MDd
+ssleay32d
   ${_OPENSSL_ROOT_HINTS_AND_PATHS}
   PATH_SUFFIXES
 lib

---

Summary of changes:
 Modules/FindOpenSSL.cmake |2 ++
 1 files changed, 2 insertions(+), 0 deletions(-)


hooks/post-receive
-- 
CMake
___
Cmake-commits mailing list
Cmake-commits@cmake.org
http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-commits


[Cmake-commits] CMake branch, master, updated. v2.8.10-48-gd39bd3e

2012-11-02 Thread Kitware Robot
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.

The branch, master has been updated
   via  d39bd3e6a8dc89637197c305102724c337b7fb0f (commit)
  from  1295247cad992fc29427eb910d03d66ada9d41ee (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=d39bd3e6a8dc89637197c305102724c337b7fb0f
commit d39bd3e6a8dc89637197c305102724c337b7fb0f
Author: Kitware Robot kwro...@kitware.com
AuthorDate: Sat Nov 3 00:01:03 2012 -0400
Commit: Kitware Robot kwro...@kitware.com
CommitDate: Sat Nov 3 00:01:03 2012 -0400

CMake Nightly Date Stamp

diff --git a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake
index 8b5eda1..1dc4a30 100644
--- a/Source/CMakeVersion.cmake
+++ b/Source/CMakeVersion.cmake
@@ -2,5 +2,5 @@
 set(CMake_VERSION_MAJOR 2)
 set(CMake_VERSION_MINOR 8)
 set(CMake_VERSION_PATCH 10)
-set(CMake_VERSION_TWEAK 20121102)
+set(CMake_VERSION_TWEAK 20121103)
 #set(CMake_VERSION_RC 1)

---

Summary of changes:
 Source/CMakeVersion.cmake |2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)


hooks/post-receive
-- 
CMake
___
Cmake-commits mailing list
Cmake-commits@cmake.org
http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-commits