[Cmake-commits] CMake branch, master, updated. v3.8.1-1140-g91d987e

[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  91d987e15c3249f35bb1151a2a3b7e487c61f095 (commit)
  from  8e2f3582eb9cf75c78fbe8232cdacce2357f7efc (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 -
https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=91d987e15c3249f35bb1151a2a3b7e487c61f095
commit 91d987e15c3249f35bb1151a2a3b7e487c61f095
Author: Kitware Robot <kwro...@kitware.com>
AuthorDate: Fri May 12 00:01:04 2017 -0400
Commit: Kitware Robot <kwro...@kitware.com>
CommitDate: Fri May 12 00:01:04 2017 -0400

CMake Nightly Date Stamp

diff --git a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake
index 6c443d6..bd92879 100644
--- a/Source/CMakeVersion.cmake
+++ b/Source/CMakeVersion.cmake
@@ -1,5 +1,5 @@
 # CMake version number components.
 set(CMake_VERSION_MAJOR 3)
 set(CMake_VERSION_MINOR 8)
-set(CMake_VERSION_PATCH 20170511)
+set(CMake_VERSION_PATCH 20170512)
 #set(CMake_VERSION_RC 1)

---

Summary of changes:
 Source/CMakeVersion.cmake |2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)


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

Re: [cmake-developers] Splitting CMakeLib

[Egor Pugin]

I see, thanks!

I'll ping when something is ready, but do not expect much in the near
future (2-4 months).

On 11 May 2017 at 16:21, Brad King  wrote:
> On 05/10/2017 10:56 AM, Egor Pugin wrote:
>> I'd like to re-use some CMake internal components, but CMakeLib looks too 
>> fat.
>> Is it possible to split it into several libraries? Are such changes
>> welcome to contribute?
>
> Refactoring/organizing/cleanup changes like that would certainly be welcome.
>
>> Some rough plan:
>> 1) Support library (if any stuff)
>> 2) Core library (targets etc.)
>> 3) Generators library
>> 4) CMake syntax library (lexer, parser)
>> 5) Commands implementation library (could be merged with 4)
>>
>> True cmake power is in its generators. It's always possible to rip off
>> all other stuff, but in order to be tied with mainstream and
>> contribute back, I'm asking this.
>
> Stephen Kelly had started work toward separating the code model from the
> language.  The code model should become an independent representation that
> can be input to the generators but be produced independent of the language.
> See cmState for example.  He isn't working on it anymore but left a thread
> some time ago on this list enumerating some future work that could be
> picked up by others (I don't recall which thread though).
>
> -Brad
>



-- 
Egor Pugin
-- 

Powered by www.kitware.com

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

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

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

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

[cmake-developers] CMake 3.9 feature freeze on 2017-06-01

[Brad King]

Hi Folks,

The feature freeze in 'master' for CMake 3.9 will be on June 1, 2017.
I may announce a freeze in 'stage' sometime in the preceding week so
that we can get any remaining dashboard trouble cleaned up.

Thanks,
-Brad
-- 

Powered by www.kitware.com

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

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

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

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

[Cmake-commits] CMake branch, master, updated. v3.8.1-1139-g8e2f358

[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  8e2f3582eb9cf75c78fbe8232cdacce2357f7efc (commit)
   via  20c838da6bac1123cba65845f3ea730cd5ca51ab (commit)
   via  66b81d8ddd4f9696b549494ac6cac4ebe4ef2bb0 (commit)
   via  4c638930b37c7f0e65e617f332f32b5323de9ee6 (commit)
   via  c2ea011830ea35cfefa7957e607c049ba8109041 (commit)
   via  e736dd9389b21eb26486a30caebaa40e299eb32b (commit)
   via  9b79d2a35730a51e3cb022f3c68e01944405dce0 (commit)
   via  1cd40bd2264bed272d404796f20b5c77155f5a1f (commit)
   via  67c9f47901f4b2b287c1bb46fe5c746ab0abbb95 (commit)
   via  608cc887c798d750e8ba7dcb51ddfb7f49c68e2c (commit)
   via  a8f04a6f9cd76ebc034a4596c70d4ce0e2cb17a2 (commit)
   via  469813cce049e18357ab274316aac0cdb4ca6688 (commit)
   via  543cf13406f478557c6ecf2279b6ab1fd3bdde30 (commit)
   via  53e89b6ab0cae7b9ba0316b3806abd986794a22c (commit)
  from  99b1ff714b45d34ad84a5d897b4fce30a9ec3041 (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 -
https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=8e2f3582eb9cf75c78fbe8232cdacce2357f7efc
commit 8e2f3582eb9cf75c78fbe8232cdacce2357f7efc
Merge: 20c838d 53e89b6
Author: Brad King 
AuthorDate: Thu May 11 14:00:08 2017 +
Commit: Kitware Robot 
CommitDate: Thu May 11 10:00:12 2017 -0400

Merge topic 'split-sysroot'

53e89b6a Add options for separate compile and link sysroots

Acked-by: Kitware Robot 
Merge-request: !819


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=20c838da6bac1123cba65845f3ea730cd5ca51ab
commit 20c838da6bac1123cba65845f3ea730cd5ca51ab
Merge: 66b81d8 1cd40bd
Author: Brad King 
AuthorDate: Thu May 11 13:59:44 2017 +
Commit: Kitware Robot 
CommitDate: Thu May 11 09:59:47 2017 -0400

Merge topic 'sunpro-fpp-fix'

1cd40bd2 SunPro: Use -fpp to process all files

Acked-by: Kitware Robot 
Merge-request: !826


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=66b81d8ddd4f9696b549494ac6cac4ebe4ef2bb0
commit 66b81d8ddd4f9696b549494ac6cac4ebe4ef2bb0
Merge: 4c63893 67c9f47
Author: Brad King 
AuthorDate: Thu May 11 13:58:33 2017 +
Commit: Kitware Robot 
CommitDate: Thu May 11 09:59:04 2017 -0400

Merge topic 'fix-typo-in-pgi-lang-std'

67c9f479 PGI: Fix typo in compiler version test for language standards

Acked-by: Kitware Robot 
Merge-request: !825


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=4c638930b37c7f0e65e617f332f32b5323de9ee6
commit 4c638930b37c7f0e65e617f332f32b5323de9ee6
Merge: c2ea011 a8f04a6
Author: Brad King 
AuthorDate: Thu May 11 13:57:39 2017 +
Commit: Kitware Robot 
CommitDate: Thu May 11 09:57:43 2017 -0400

Merge topic 'print-function-server-tests'

a8f04a6f Tests/Server: import print_function from the future

Acked-by: Kitware Robot 
Reviewed-by: Matt Soucy 
Merge-request: !822


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=c2ea011830ea35cfefa7957e607c049ba8109041
commit c2ea011830ea35cfefa7957e607c049ba8109041
Merge: e736dd9 543cf13
Author: Brad King 
AuthorDate: Thu May 11 13:56:45 2017 +
Commit: Kitware Robot 
CommitDate: Thu May 11 09:56:49 2017 -0400

Merge topic 'cpackifw-access-refactoring'

543cf134 CPackIFW: Access refactoring

Acked-by: Kitware Robot 
Merge-request: !820


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=e736dd9389b21eb26486a30caebaa40e299eb32b
commit e736dd9389b21eb26486a30caebaa40e299eb32b
Merge: 9b79d2a 608cc88
Author: Brad King 
AuthorDate: Thu May 11 13:55:41 2017 +
Commit: Kitware Robot 
CommitDate: Thu May 11 09:55:44 2017 -0400

Merge topic 'TestDriver-remove-unused-init'

608cc887 TestDriver: Remove unused local variable initialization

Acked-by: Kitware Robot 
Merge-request: !824


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=9b79d2a35730a51e3cb022f3c68e01944405dce0
commit 9b79d2a35730a51e3cb022f3c68e01944405dce0
Merge: 99b1ff7 469813c
Author: Brad King 
AuthorDate: Thu May 11 13:55:08 2017 +
Commit: Kitware Robot 
CommitDate: Thu May 11 09:55:12 2017 -0400

Merge topic 

[Cmake-commits] CMake branch, master, updated. v3.8.1-1125-g99b1ff7

[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  99b1ff714b45d34ad84a5d897b4fce30a9ec3041 (commit)
   via  fdd341ebfdf1da3e53332303eb93d5db1feaed6d (commit)
   via  67a8d907adbc587021e9eba603cb789da09926d8 (commit)
   via  0c519c70297bd2fd6e139d74c6b175c304c09192 (commit)
  from  f1b9fe5fc4af1bab7d551c48600ca3ebb717db8f (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 -
https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=99b1ff714b45d34ad84a5d897b4fce30a9ec3041
commit 99b1ff714b45d34ad84a5d897b4fce30a9ec3041
Merge: f1b9fe5 fdd341e
Author: Brad King 
AuthorDate: Thu May 11 13:54:13 2017 +
Commit: Kitware Robot 
CommitDate: Thu May 11 09:54:19 2017 -0400

Merge topic 'dead-code-removal'

fdd341eb cmFindCommon: remove unused function SetMakefile
67a8d907 cmExecutionStatus: Remove arguments from setters
0c519c70 bootstrap: Remove leftovers from cmBootstrapCommands

Acked-by: Kitware Robot 
Merge-request: !821


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=fdd341ebfdf1da3e53332303eb93d5db1feaed6d
commit fdd341ebfdf1da3e53332303eb93d5db1feaed6d
Author: Daniel Pfeifer 
AuthorDate: Sun Jan 8 22:27:16 2017 +0100
Commit: Daniel Pfeifer 
CommitDate: Wed May 10 15:58:28 2017 +0200

cmFindCommon: remove unused function SetMakefile

diff --git a/Source/cmFindCommon.cxx b/Source/cmFindCommon.cxx
index 110195c..6ffbb6e 100644
--- a/Source/cmFindCommon.cxx
+++ b/Source/cmFindCommon.cxx
@@ -334,15 +334,3 @@ void cmFindCommon::ComputeFinalPaths()
   std::for_each(this->SearchPaths.begin(), this->SearchPaths.end(),
 );
 }
-
-void cmFindCommon::SetMakefile(cmMakefile* makefile)
-{
-  cmCommand::SetMakefile(makefile);
-
-  // If we are building for Apple (OSX or also iphone), make sure
-  // that frameworks and bundles are searched first.
-  if (this->Makefile->IsOn("APPLE")) {
-this->SearchFrameworkFirst = true;
-this->SearchAppBundleFirst = true;
-  }
-}
diff --git a/Source/cmFindCommon.h b/Source/cmFindCommon.h
index 426d233..bbb7a38 100644
--- a/Source/cmFindCommon.h
+++ b/Source/cmFindCommon.h
@@ -14,8 +14,6 @@
 #include "cmPathLabel.h"
 #include "cmSearchPath.h"
 
-class cmMakefile;
-
 /** \class cmFindCommon
  * \brief Base class for FIND_XXX implementations.
  *
@@ -105,7 +103,6 @@ protected:
 
   bool CheckCommonArgument(std::string const& arg);
   void AddPathSuffix(std::string const& arg);
-  void SetMakefile(cmMakefile* makefile);
 
   bool NoDefaultPath;
   bool NoCMakePath;

https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=67a8d907adbc587021e9eba603cb789da09926d8
commit 67a8d907adbc587021e9eba603cb789da09926d8
Author: Daniel Pfeifer 
AuthorDate: Mon Dec 26 10:30:31 2016 +0100
Commit: Daniel Pfeifer 
CommitDate: Tue May 9 23:49:14 2017 +0200

cmExecutionStatus: Remove arguments from setters

The setters are only used to set boolean values.  The values are never
reset individually.

diff --git a/Source/cmBreakCommand.cxx b/Source/cmBreakCommand.cxx
index 9bb6137..3772c6f 100644
--- a/Source/cmBreakCommand.cxx
+++ b/Source/cmBreakCommand.cxx
@@ -41,7 +41,7 @@ bool cmBreakCommand::InitialPass(std::vector 
const& args,
 }
   }
 
-  status.SetBreakInvoked(true);
+  status.SetBreakInvoked();
 
   if (!args.empty()) {
 bool issueMessage = true;
diff --git a/Source/cmContinueCommand.cxx b/Source/cmContinueCommand.cxx
index 53d035d..2298a05 100644
--- a/Source/cmContinueCommand.cxx
+++ b/Source/cmContinueCommand.cxx
@@ -19,7 +19,7 @@ bool cmContinueCommand::InitialPass(std::vector 
const& args,
 return true;
   }
 
-  status.SetContinueInvoked(true);
+  status.SetContinueInvoked();
 
   if (!args.empty()) {
 this->Makefile->IssueMessage(cmake::FATAL_ERROR,
diff --git a/Source/cmExecutionStatus.h b/Source/cmExecutionStatus.h
index fd3c416..ac5fe1d 100644
--- a/Source/cmExecutionStatus.h
+++ b/Source/cmExecutionStatus.h
@@ -11,16 +11,13 @@
 class cmExecutionStatus
 {
 public:
-  cmExecutionStatus() { this->Clear(); }
-
-  void SetReturnInvoked(bool val) { this->ReturnInvoked = val; }
-  bool GetReturnInvoked() { return this->ReturnInvoked; }
-
-  void SetBreakInvoked(bool val) { this->BreakInvoked = val; }
-  bool GetBreakInvoked() { return this->BreakInvoked; }
-
-  void SetContinueInvoked(bool val) { this->ContinueInvoked = val; }
-  bool GetContinueInvoked() { return this->ContinueInvoked; }
+  cmExecutionStatus()
+: ReturnInvoked(false)
+, BreakInvoked(false)
+, 

Re: [CMake] DLL handling under CMake

[Hendrik Sattler]

Hi,

sorry for the delay. I see you already found a solution yourself.
Still, I want to share mine:
-CopyPrerequisites.cmake
include ( GetPrerequisites )

if ( NOT DEFINED PREREQ_FILE )
  message ( FATAL_ERROR "PREREQ_FILE must be defined(${PREREQ_FILE})" )
endif ()

#
# Satisfy the find_file() search by common subdirs where .dll file can  
be found

#
foreach ( dir ${CMAKE_PREFIX_PATH} )
  list ( APPEND dirs ${dir}/bin )
endforeach ( dir )

get_filename_component ( COPY_DESTINATION "${PREREQ_FILE}" PATH )
get_prerequisites ( "${PREREQ_FILE}" COPY_FILES 1 1 "${dirs}"  
"${COPY_DESTINATION}" )


foreach ( COPY_FILE ${COPY_FILES} )
  if ( NOT IS_ABSOLUTE ${COPY_FILE} )
set ( COPY_FILE_FULL )
gp_resolve_item ( "${PREREQ_FILE}" "${COPY_FILE}" "${dirs}"  
"${COPY_DESTINATION}" COPY_FILE_FULL )

  else ()
set ( COPY_FILE_FULL ${COPY_FILE} )
  endif ()
  if ( COPY_FILE_FULL )
get_filename_component ( COPY_SOURCE_DIR "${COPY_FILE_FULL}" PATH )
if ( NOT COPY_SOURCE_DIR MATCHES "^${COPY_DESTINATION}$" )
  message ( "Copying ${COPY_FILE_FULL} to output directory" )
  execute_process ( COMMAND "${CMAKE_COMMAND}" -E  
copy_if_different "${COPY_FILE_FULL}" "${COPY_DESTINATION}" )

endif ()
  else ()
message ( "Failed to find  ${COPY_FILE}" )
  endif ()
endforeach ( COPY_FILE )
--

This can now be called from CMakeLists.txt:
if ( CMAKE_RUNTIME_OUTPUT_DIRECTORY )
  add_custom_command ( TARGET Gui POST_BUILD
COMMAND ${CMAKE_COMMAND}
"-DCMAKE_PREFIX_PATH:PATH=${SOME_SEARCH_DIRS}"
"-DPREREQ_FILE=$"
-P ${CMAKE_SOURCE_DIR}/CMakeModules/CopyPrerequisites.cmake
VERBATIM
  )
endif ()

The variable SOME_SERACH_DIRS is filled with e.g. IMPORTED_LOCATION  
property values.
The same variable is used when calling INSTALL(CODE ".   
fixup_bundle(...)" )


Regards,

HS

Zitat von lec...@gmail.com:


I managed to get it working by using an intermediate script.
One might want to generate the script instead of using the  
« RUN_IT » variable trick.

This was only tested on Windows, but seems to work fine.
Put the following code in a xx.cmake file, include it from your  
CMakeLists.txt and enjoy.



# This is a helper script to run BundleUtilities fixup_bundle as postbuild
# for a target. The primary use case is to copy .DLLs to the build  
directory for
# the Windows platform. It allows generator expressions to be used  
to determine

# the binary location
#
# Usage : run_fixup(TARGET LIBS DIRS)
# - TARGET : A cmake target
# - See fixup_bundle for LIBS and DIRS arguments

if(RUN_IT)
# Script ran by the add_custom_command
include(BundleUtilities)
fixup_bundle("${TO_FIXUP_FILE}" "${TO_FIXUP_LIBS}" "${TO_FIXUP_DIRS}")
# End of script ran by the add_custom_command
else()

set(THIS_FILE ${CMAKE_CURRENT_LIST_FILE})
message(${THIS_FILE})
function(run_fixup _target _libs _dirs)
message(${THIS_FILE})
add_custom_command(
TARGET ${_target} POST_BUILD
		COMMAND ${CMAKE_COMMAND} -DRUN_IT:BOOL=ON  
-DTO_FIXUP_FILE=$ -DTO_FIXUP_LIBS=${_libs}  
-DTO_FIXUP_DIRS=${_dirs}  -P ${THIS_FILE}

COMMENT "Fixing up dependencies for ${_target}"
VERBATIM
)

endfunction()

endif()


De : Clément Gregoire
Envoyé le :jeudi 4 mai 2017 08:37
À : Hendrik Sattler; Louis-Paul CORDIER; Cmake Mailing List
Objet :Re: [CMake] DLL handling under CMake

I'd also be interested in this. I saw an old mail in the ML about  
this, but it seems fixup_bundle is old and cant use generator  
expressions, making it hard to use (I don't want to hardcode the  
executable path).


Do you have a sample for this ?
CMake would really benefit from having those features made more  
accessible instead of everyone having to write its own script 
Le sam. 29 avr. 2017 22:10, Hendrik Sattler  
 a écrit :



Am 27. April 2017 10:43:50 MESZ schrieb Louis-Paul CORDIER  
:

This steps are tedious and I'm wondering if there is a mechanism that
exists or that have to be imagined to make the DLL nightmare end.


I use BundleUtilities to achieve the copying of DLL files to the  
installation directory. The main problem for this is to enumerate  
the needed directories.


I use the same for copying DLL files to the output directory to ease  
debugging.


The advantage is the inspection of the exe for really needed DLL  
files. This AUTOMATICALLY handles the case debug vs. release.


HS

--
Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.
--

Powered by www.kitware.com

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


Kitware offers various services to support the CMake community. For  
more information on each offering, please visit:


CMake Support: http://cmake.org/cmake/help/support.html

Re: [cmake-developers] Splitting CMakeLib

[Brad King]

On 05/10/2017 10:56 AM, Egor Pugin wrote:
> I'd like to re-use some CMake internal components, but CMakeLib looks too fat.
> Is it possible to split it into several libraries? Are such changes
> welcome to contribute?

Refactoring/organizing/cleanup changes like that would certainly be welcome.

> Some rough plan:
> 1) Support library (if any stuff)
> 2) Core library (targets etc.)
> 3) Generators library
> 4) CMake syntax library (lexer, parser)
> 5) Commands implementation library (could be merged with 4)
> 
> True cmake power is in its generators. It's always possible to rip off
> all other stuff, but in order to be tied with mainstream and
> contribute back, I'm asking this.

Stephen Kelly had started work toward separating the code model from the
language.  The code model should become an independent representation that
can be input to the generators but be produced independent of the language.
See cmState for example.  He isn't working on it anymore but left a thread
some time ago on this list enumerating some future work that could be
picked up by others (I don't recall which thread though).

-Brad

-- 

Powered by www.kitware.com

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

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

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

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

Re: [cmake-developers] Splitting CMakeLib

[Daniel Pfeifer]

On Wed, May 10, 2017 at 4:56 PM, Egor Pugin  wrote:

> Hi!
>
> I'd like to re-use some CMake internal components, but CMakeLib looks too
> fat.
> Is it possible to split it into several libraries? Are such changes
> welcome to contribute?
>

Strongly in favor. Such a modularization will be a benefit for CMake. It
will require to cleanup CMake's internal inter-dependencies and it will
help to keep them clean afterwards.
It will make CMake's codebase easier to approach by new contributors. It
will allow experiments like replacing individual parts (eg. new frontend).
Let's learn from LLVM/Clang.


> Some rough plan:
> 1) Support library (if any stuff)
> 2) Core library (targets etc.)
> 3) Generators library
> 4) CMake syntax library (lexer, parser)
> 5) Commands implementation library (could be merged with 4)
>

Don't merge the commands with the command interpreter/vm.

5) Scripting commands
6) Project commands
7) CTest commands
8) Package generators
9) Server
...

True cmake power is in its generators. It's always possible to rip off
> all other stuff, but in order to be tied with mainstream and
> contribute back, I'm asking this.
>

Personally, I regard the generators as obsolete and see the future in the
server.

Cheers, Daniel
-- 

Powered by www.kitware.com

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

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

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

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