[Cmake-commits] CMake branch, master, updated. v3.6.0-rc3-236-g3a04494

[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  3a0449439f03981865b8d43815ac9b6292574a47 (commit)
  from  f05657de9d1ae7247a527186830d37702ec30de4 (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=3a0449439f03981865b8d43815ac9b6292574a47
commit 3a0449439f03981865b8d43815ac9b6292574a47
Author: Kitware Robot <kwro...@kitware.com>
AuthorDate: Sat Jun 25 00:01:05 2016 -0400
Commit: Kitware Robot <kwro...@kitware.com>
CommitDate: Sat Jun 25 00:01:05 2016 -0400

CMake Nightly Date Stamp

diff --git a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake
index 40f8e11..a1d1eb3 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 6)
-set(CMake_VERSION_PATCH 20160624)
+set(CMake_VERSION_PATCH 20160625)
 #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] CMake terminology

[Ruslan Baratov via CMake]

There is cmake **build** step: cmake --build _builds

So in GUI it's:
 * cmake configure
 * cmake generate
 * IDE build (which you can do with cmake --build so it can be called 
"cmake build" step)


in cmd:
 * cmake configure+generate
 * cmake build

Also I can call it "cmake step" in docs about some C++ project, but if 
the docs about cmake itself I think this term is too wide


On 25-Jun-16 02:13, Craig Scott wrote:
In documentation, blog articles, etc. I just call it the "cmake" step 
(or sometimes the "project setup" step if talking in a more 
project-wide sense). For many users, the separate configure and 
generate steps are somewhat of an implementation detail, so it makes 
more sense to give it a single term. I'm not aware of any generally 
accepted term, but the ones I use seem to be fairly easy to 
understand, especially for those new to CMake. YMMV.


On Saturday, 25 June 2016, Ruslan Baratov via CMake > wrote:


On 24-Jun-16 23:49, Robert Maynard wrote:

Please run the configure and generate steps by

It's too long :)

Also it doesn't express the fact that it's a single action, consider:
  "To add variables on configure and generate steps use '-D'"
  "Before running configure and generate steps note that old
variables from cache can be used"
  etc.



On Fri, Jun 24, 2016 at 4:40 PM, Ruslan Baratov
 wrote:

On 24-Jun-16 23:25, Robert Maynard wrote:

cmake from the command line is still running the two
stages, it just
doesn't allow for feedback/input from the user between
the two stages.

Yes, I understand that. Question is about the name of the
step. I.e. when I
do write manual what should I choose
   Please run configure step by: cmake -H. -B_builds
or
   Please run generate step by: cmake -H. -B_builds
?

May be both versions are correct? Or both incorrect?

Ruslo


On Fri, Jun 24, 2016 at 4:06 PM, Ruslan Baratov via CMake
 wrote:

Hi,

I have a question about CMake terminology. When we
are using CMake GUI
there
are two buttons "Configure" and "Generate", hence
we have two stages:

1. Configure step, when we do configuring project,
effectively creating
file
with cache variables (which we can modify) without
really generating
native
tools files like Makefile/*.sln/etc.

2. Generate step, when we do generating project
using file with cache
variables, i.e. create those Makefile/*.sln/etc.

The question is about command line version of
CMake. Since we do creating
file with cache and generate native tools files in
one step what is the
right term? Is it a configure step because we read
user's '-D' and create
cache file?  Is it a generate step because native
tools files generated
at
the end? May be there is a third name to describe
the fact that it's
configure+generate step?

Thanks, Ruslo
--

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




-- 


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 

Re: [CMake] CMake terminology

[Craig Scott]

In documentation, blog articles, etc. I just call it the "cmake" step (or
sometimes the "project setup" step if talking in a more project-wide
sense). For many users, the separate configure and generate steps are
somewhat of an implementation detail, so it makes more sense to give it a
single term. I'm not aware of any generally accepted term, but the ones I
use seem to be fairly easy to understand, especially for those new to
CMake. YMMV.

On Saturday, 25 June 2016, Ruslan Baratov via CMake  wrote:

> On 24-Jun-16 23:49, Robert Maynard wrote:
>
>> Please run the configure and generate steps by
>>
> It's too long :)
>
> Also it doesn't express the fact that it's a single action, consider:
>   "To add variables on configure and generate steps use '-D'"
>   "Before running configure and generate steps note that old variables
> from cache can be used"
>   etc.
>
>
>
>> On Fri, Jun 24, 2016 at 4:40 PM, Ruslan Baratov
>>  wrote:
>>
>>> On 24-Jun-16 23:25, Robert Maynard wrote:
>>>
 cmake from the command line is still running the two stages, it just
 doesn't allow for feedback/input from the user between the two stages.

>>> Yes, I understand that. Question is about the name of the step. I.e.
>>> when I
>>> do write manual what should I choose
>>>Please run configure step by: cmake -H. -B_builds
>>> or
>>>Please run generate step by: cmake -H. -B_builds
>>> ?
>>>
>>> May be both versions are correct? Or both incorrect?
>>>
>>> Ruslo
>>>
>>>
>>> On Fri, Jun 24, 2016 at 4:06 PM, Ruslan Baratov via CMake
  wrote:

> Hi,
>
> I have a question about CMake terminology. When we are using CMake GUI
> there
> are two buttons "Configure" and "Generate", hence we have two stages:
>
> 1. Configure step, when we do configuring project, effectively creating
> file
> with cache variables (which we can modify) without really generating
> native
> tools files like Makefile/*.sln/etc.
>
> 2. Generate step, when we do generating project using file with cache
> variables, i.e. create those Makefile/*.sln/etc.
>
> The question is about command line version of CMake. Since we do
> creating
> file with cache and generate native tools files in one step what is the
> right term? Is it a configure step because we read user's '-D' and
> create
> cache file?  Is it a generate step because native tools files generated
> at
> the end? May be there is a third name to describe the fact that it's
> configure+generate step?
>
> Thanks, Ruslo
> --
>
> 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
>

>>>
>>>
> --
>
> 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
>


-- 
Craig Scott
Melbourne, Australia
http://crascit.com
-- 

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

Re: [CMake] CMake terminology

[Ruslan Baratov via CMake]

On 24-Jun-16 23:49, Robert Maynard wrote:

Please run the configure and generate steps by

It's too long :)

Also it doesn't express the fact that it's a single action, consider:
  "To add variables on configure and generate steps use '-D'"
  "Before running configure and generate steps note that old variables 
from cache can be used"

  etc.




On Fri, Jun 24, 2016 at 4:40 PM, Ruslan Baratov
 wrote:

On 24-Jun-16 23:25, Robert Maynard wrote:

cmake from the command line is still running the two stages, it just
doesn't allow for feedback/input from the user between the two stages.

Yes, I understand that. Question is about the name of the step. I.e. when I
do write manual what should I choose
   Please run configure step by: cmake -H. -B_builds
or
   Please run generate step by: cmake -H. -B_builds
?

May be both versions are correct? Or both incorrect?

Ruslo



On Fri, Jun 24, 2016 at 4:06 PM, Ruslan Baratov via CMake
 wrote:

Hi,

I have a question about CMake terminology. When we are using CMake GUI
there
are two buttons "Configure" and "Generate", hence we have two stages:

1. Configure step, when we do configuring project, effectively creating
file
with cache variables (which we can modify) without really generating
native
tools files like Makefile/*.sln/etc.

2. Generate step, when we do generating project using file with cache
variables, i.e. create those Makefile/*.sln/etc.

The question is about command line version of CMake. Since we do creating
file with cache and generate native tools files in one step what is the
right term? Is it a configure step because we read user's '-D' and create
cache file?  Is it a generate step because native tools files generated
at
the end? May be there is a third name to describe the fact that it's
configure+generate step?

Thanks, Ruslo
--

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





--

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

[Cmake-commits] CMake branch, next, updated. v3.6.0-rc3-530-g2152e11

[Gregor Jasny via Cmake-commits]

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  2152e11e7a4f9d5bb80e224265e3aba40c92a060 (commit)
   via  e301be8c4f82aeab9a5693e611d93b22a901866e (commit)
   via  3b9d0962e79e8bdeec8a92684d62172197c1ae6d (commit)
   via  1721529fa69b60ec2717e85ef8730de549e226b1 (commit)
   via  f05657de9d1ae7247a527186830d37702ec30de4 (commit)
  from  41a51131f9a253459577cbe4562be5dd368a517d (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=2152e11e7a4f9d5bb80e224265e3aba40c92a060
commit 2152e11e7a4f9d5bb80e224265e3aba40c92a060
Merge: 41a5113 e301be8
Author: Gregor Jasny 
AuthorDate: Fri Jun 24 17:26:16 2016 -0400
Commit: CMake Topic Stage 
CommitDate: Fri Jun 24 17:26:16 2016 -0400

Merge topic 'app-framework-bundle-extension' into next

e301be8c Update documentation about bundle extensions
3b9d0962 Honor BUNDLE_EXTENSION also for Frameworks (#14742)
1721529f Honor BUNDLE_EXTENSION also for App Bundles (#16148)
f05657de CMake Nightly Date Stamp


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=e301be8c4f82aeab9a5693e611d93b22a901866e
commit e301be8c4f82aeab9a5693e611d93b22a901866e
Author: Gregor Jasny 
AuthorDate: Fri Jun 24 23:17:22 2016 +0200
Commit: Gregor Jasny 
CommitDate: Fri Jun 24 23:17:22 2016 +0200

Update documentation about bundle extensions

diff --git a/Help/prop_tgt/BUNDLE_EXTENSION.rst 
b/Help/prop_tgt/BUNDLE_EXTENSION.rst
index ea265b3..6b3d580 100644
--- a/Help/prop_tgt/BUNDLE_EXTENSION.rst
+++ b/Help/prop_tgt/BUNDLE_EXTENSION.rst
@@ -1,7 +1,8 @@
 BUNDLE_EXTENSION
 
 
-The file extension used to name a :prop_tgt:`BUNDLE` target on the OS X and 
iOS.
+The file extension used to name a :prop_tgt:`BUNDLE`, a :prop_tgt:`FRAMEWORK`,
+or a :prop_tgt:`MACOSX_BUNDLE` target on the OS X and iOS.
 
-The default value is ``bundle`` - you can also use ``plugin`` or whatever
-file extension is required by the host app for your bundle.
+The default value is ``bundle``, ``framework``, or ``app`` for the respective
+target types.
diff --git a/Help/release/dev/app-framework-bundle-extension.rst 
b/Help/release/dev/app-framework-bundle-extension.rst
new file mode 100644
index 000..01855a2
--- /dev/null
+++ b/Help/release/dev/app-framework-bundle-extension.rst
@@ -0,0 +1,5 @@
+app-framework-bundle-extension
+--
+
+* On Apple platforms the :prop_tgt:`BUNDLE_EXTENSION` now also applies to
+  Frameworks and App Bundles.

https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=3b9d0962e79e8bdeec8a92684d62172197c1ae6d
commit 3b9d0962e79e8bdeec8a92684d62172197c1ae6d
Author: Gregor Jasny 
AuthorDate: Sun Jun 19 21:26:40 2016 +0200
Commit: Gregor Jasny 
CommitDate: Fri Jun 24 23:06:45 2016 +0200

Honor BUNDLE_EXTENSION also for Frameworks (#14742)

diff --git a/Source/cmGeneratorTarget.cxx b/Source/cmGeneratorTarget.cxx
index 4db1bd9..eec3422 100644
--- a/Source/cmGeneratorTarget.cxx
+++ b/Source/cmGeneratorTarget.cxx
@@ -1396,7 +1396,12 @@ std::string 
cmGeneratorTarget::GetFrameworkDirectory(const std::string& config,
 {
   std::string fpath;
   fpath += this->GetOutputName(config, false);
-  fpath += ".framework";
+  fpath += ".";
+  const char* ext = this->GetProperty("BUNDLE_EXTENSION");
+  if (!ext) {
+ext = "framework";
+  }
+  fpath += ext;
   if (!rootDir && !this->Makefile->PlatformIsAppleIos()) {
 fpath += "/Versions/";
 fpath += this->GetFrameworkVersion();
@@ -3013,7 +3018,13 @@ void cmGeneratorTarget::GetFullNameInternal(const 
std::string& config,
   std::string fw_prefix;
   if (this->IsFrameworkOnApple()) {
 fw_prefix = this->GetOutputName(config, false);
-fw_prefix += ".framework/";
+fw_prefix += ".";
+const char* ext = this->GetProperty("BUNDLE_EXTENSION");
+if (!ext) {
+  ext = "framework";
+}
+fw_prefix += ext;
+fw_prefix += "/";
 targetPrefix = fw_prefix.c_str();
 targetSuffix = 0;
   }
diff --git a/Source/cmGlobalXCodeGenerator.cxx 
b/Source/cmGlobalXCodeGenerator.cxx
index d27c579..91a90b2 100644
--- a/Source/cmGlobalXCodeGenerator.cxx
+++ b/Source/cmGlobalXCodeGenerator.cxx
@@ -1843,6 +1843,11 @@ void 
cmGlobalXCodeGenerator::CreateBuildSettings(cmGeneratorTarget* gtgt,
 std::string fw_version = gtgt->GetFrameworkVersion();
 buildSettings->AddAttribute("FRAMEWORK_VERSION",
 this->CreateString(fw_version));
+const char* ext = 

[CMake] Qt 5.6.1 messes up Linux packaging using CPack?

[Michael Jackson]

I have a project that uses CMake. I had been compiling against Qt 5.6.0 for
a while but due to issues with QWebEngine I installed Qt 5.6.1 instead and
compiled against that. I can run my application from the build directory
but when I go to use cpack to package my application I am getting the
following errors for every single one of my libraries that I build:

CMake Error at SimpleITKExplicit/cmake_install.cmake:36 (file):
  file INSTALL cannot find

"/home/mjackson/Workspace/DREAM3D-build/Release/SimpleITKExplicit/CMakeFiles/CMakeRelink.dir/libSimpleITKExplicit-0.9.so.1".
Call Stack (most recent call first):
  cmake_install.cmake:435 (include)


I recompiled in a completely separate directory against my Qt 5.6.0
installation and cpack will execute without any errors.

Has anyone else seen this yet?

Thanks
_
Mike Jackson  mike.jack...@bluequartz.net
BlueQuartz Softwarewww.bluequartz.net
Principal Software Engineer  Dayton, Ohio
-- 

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

Re: [CMake] CMake terminology

[Robert Maynard]

Please run the configure and generate steps by

On Fri, Jun 24, 2016 at 4:40 PM, Ruslan Baratov
 wrote:
>
> On 24-Jun-16 23:25, Robert Maynard wrote:
>>
>> cmake from the command line is still running the two stages, it just
>> doesn't allow for feedback/input from the user between the two stages.
>
> Yes, I understand that. Question is about the name of the step. I.e. when I
> do write manual what should I choose
>   Please run configure step by: cmake -H. -B_builds
> or
>   Please run generate step by: cmake -H. -B_builds
> ?
>
> May be both versions are correct? Or both incorrect?
>
> Ruslo
>
>
>>
>> On Fri, Jun 24, 2016 at 4:06 PM, Ruslan Baratov via CMake
>>  wrote:
>>>
>>> Hi,
>>>
>>> I have a question about CMake terminology. When we are using CMake GUI
>>> there
>>> are two buttons "Configure" and "Generate", hence we have two stages:
>>>
>>> 1. Configure step, when we do configuring project, effectively creating
>>> file
>>> with cache variables (which we can modify) without really generating
>>> native
>>> tools files like Makefile/*.sln/etc.
>>>
>>> 2. Generate step, when we do generating project using file with cache
>>> variables, i.e. create those Makefile/*.sln/etc.
>>>
>>> The question is about command line version of CMake. Since we do creating
>>> file with cache and generate native tools files in one step what is the
>>> right term? Is it a configure step because we read user's '-D' and create
>>> cache file?  Is it a generate step because native tools files generated
>>> at
>>> the end? May be there is a third name to describe the fact that it's
>>> configure+generate step?
>>>
>>> Thanks, Ruslo
>>> --
>>>
>>> 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
>
>
>
-- 

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

Re: [CMake] CMake terminology

[Ruslan Baratov via CMake]

On 24-Jun-16 23:25, Robert Maynard wrote:

cmake from the command line is still running the two stages, it just
doesn't allow for feedback/input from the user between the two stages.
Yes, I understand that. Question is about the name of the step. I.e. 
when I do write manual what should I choose

  Please run configure step by: cmake -H. -B_builds
or
  Please run generate step by: cmake -H. -B_builds
?

May be both versions are correct? Or both incorrect?

Ruslo



On Fri, Jun 24, 2016 at 4:06 PM, Ruslan Baratov via CMake
 wrote:

Hi,

I have a question about CMake terminology. When we are using CMake GUI there
are two buttons "Configure" and "Generate", hence we have two stages:

1. Configure step, when we do configuring project, effectively creating file
with cache variables (which we can modify) without really generating native
tools files like Makefile/*.sln/etc.

2. Generate step, when we do generating project using file with cache
variables, i.e. create those Makefile/*.sln/etc.

The question is about command line version of CMake. Since we do creating
file with cache and generate native tools files in one step what is the
right term? Is it a configure step because we read user's '-D' and create
cache file?  Is it a generate step because native tools files generated at
the end? May be there is a third name to describe the fact that it's
configure+generate step?

Thanks, Ruslo
--

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



--

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

Re: [CMake] CMake terminology

[Robert Maynard]

cmake from the command line is still running the two stages, it just
doesn't allow for feedback/input from the user between the two stages.

On Fri, Jun 24, 2016 at 4:06 PM, Ruslan Baratov via CMake
 wrote:
> Hi,
>
> I have a question about CMake terminology. When we are using CMake GUI there
> are two buttons "Configure" and "Generate", hence we have two stages:
>
> 1. Configure step, when we do configuring project, effectively creating file
> with cache variables (which we can modify) without really generating native
> tools files like Makefile/*.sln/etc.
>
> 2. Generate step, when we do generating project using file with cache
> variables, i.e. create those Makefile/*.sln/etc.
>
> The question is about command line version of CMake. Since we do creating
> file with cache and generate native tools files in one step what is the
> right term? Is it a configure step because we read user's '-D' and create
> cache file?  Is it a generate step because native tools files generated at
> the end? May be there is a third name to describe the fact that it's
> configure+generate step?
>
> Thanks, Ruslo
> --
>
> 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
-- 

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

[CMake] CMake terminology

[Ruslan Baratov via CMake]

Hi,

I have a question about CMake terminology. When we are using CMake GUI 
there are two buttons "Configure" and "Generate", hence we have two stages:


1. Configure step, when we do configuring project, effectively creating 
file with cache variables (which we can modify) without really 
generating native tools files like Makefile/*.sln/etc.


2. Generate step, when we do generating project using file with cache 
variables, i.e. create those Makefile/*.sln/etc.


The question is about command line version of CMake. Since we do 
creating file with cache and generate native tools files in one step 
what is the right term? Is it a configure step because we read user's 
'-D' and create cache file?  Is it a generate step because native tools 
files generated at the end? May be there is a third name to describe the 
fact that it's configure+generate step?


Thanks, Ruslo
--

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

[cmake-developers] Improved handling of %directives in CPACK_RPM_USER_FILELIST

[Andrew Fuller]

Attached is a patch to improve the handling of %directives in 
CPACK_RPM_USER_FILELIST.  Specifically it accepts any characters (even spaces) 
inside the parenthesis so it doesn't need to keep changing every time there's a 
new valid symbol.  The current open ticket is 
https://gitlab.kitware.com/cmake/cmake/issues/13468 which is asking to use an 
underscore.  %caps requires the use of '+' and also spaces.


I've created a merge request here: 
https://gitlab.kitware.com/cmake/cmake/merge_requests/23? with the same 
contents as this format-patch, but the contribution guidelines say a 
format-patch to this list is desired.


Cheers,

-Andrew??
From 13717c3943e11848233f6c8e95ee69ba3bda3ec1 Mon Sep 17 00:00:00 2001
From: Andrew Fuller 
Date: Fri, 24 Jun 2016 10:45:40 -0700
Subject: [PATCH] Adjust the regex to handle %foo and %foo(anything)
 directives.

Directives that are legal inside the %files section of an RPM spec may contain a variety of characters particularly when specifying %caps which can include +, _, and space.  Watch for parenthesis to determine what forms the prefix vs. path.

Fixes issue #14362
---
 Modules/CPackRPM.cmake | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/Modules/CPackRPM.cmake b/Modules/CPackRPM.cmake
index d231ff0..cb8cdc8 100644
--- a/Modules/CPackRPM.cmake
+++ b/Modules/CPackRPM.cmake
@@ -1683,8 +1683,8 @@ function(cpack_rpm_generate_package)
 
 set(CPACK_RPM_USER_INSTALL_FILES "")
 foreach(F IN LISTS CPACK_RPM_USER_FILELIST_INTERNAL)
-  string(REGEX REPLACE "%[A-Za-z0-9\(\),-]* " "" F_PATH ${F})
-  string(REGEX MATCH "%[A-Za-z0-9\(\),-]*" F_PREFIX ${F})
+  string(REGEX REPLACE "%[A-Za-z]+(\\(.*\\))? " "" F_PATH ${F})
+  string(REGEX MATCH "%[A-Za-z]+(\\(.*\\))?" F_PREFIX ${F})
 
   if(CPACK_RPM_PACKAGE_DEBUG)
 message("CPackRPM:Debug: F_PREFIX=<${F_PREFIX}>, F_PATH=<${F_PATH}>")
-- 
2.7.4

-- 

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] gathering directory names in cmake

[Cfyz]

> I have a source tree which contains multiple directories each of
> which has a subdirectory called "xyz". I want to create a target
> that creates a zip file with each of the xyz directories.

You can filter the file paths with a few CMake script lines:

file(GLOB_RECURSE FILES "./*")
foreach(FILE ${FILES})
if(FILE MATCHES ".*/xyz/.*")
list(APPEND XYZ_FILES ${FILE})
endif()
endforeach()

Now XYZ_FILES contains a list of files with /xyz/ subdirectory somewhere in
their path.
-- 

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

[CMake] subversion

[Andreas Naumann]

Dear cmake users,

I have a question if, and how, you use the Subversion module of cmake.
The module provides the macro Subversion_WC_INFO, which extracts 
information of a working copy. I use this information, to generate a sub 
minor revision number of my project.
If I checkout my project using svn, it works. But if I export it, the 
modules failes with a fatal error.
At the moment, I check, if my directory is a working copy and if it is 
not, the version variable is not defined. In my oppinion, it would be 
better, if the macro from the subversion module would simply define a 
variable "is_working_directory" instead of failing hard.

What do you think about this idea? How do you use the subversion module?
The patch would be easy, and I would send one to the developer mailing 
list, if desired.


Regards,
Andreas
--

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

[cmake-developers] Status of pre-compiled headers

[Oleh Kravchenko]

Hello!

As far as I can see from issue tracker and the mail list archives of
"precompiled headers" feature we are still struggling for solution. I'm
ready to contribute to development, but have not idea where shall I
start :)
https://cmake.org/Bug/view.php?id=1260
https://gitlab.kitware.com/cmake/cmake/issues/1260

I have in-depth knowledge of C/C++ development for different platforms
(Windows, Linux), (arm, x86, amd64) and GCC/MSVC compilers.

Please point me to where can I learn the correct process of adding new
features to CMake and current state of "precompiled headers" feature
development.

Best Regards,
Oleh Kravchenko


-- 

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] [ANNOUNCE] DaD's House Standalone Installers

[Konstantin Podsvirov]

Hello dear developers!

Standalone installers for some DaD's House releases now available at SF mirror:

https://sourceforge.net/projects/dad-mirror/files/standalone/2015/dad-0.3.1-windows-vc12x64-2015-standalone.exe/download

https://sourceforge.net/projects/dad-mirror/files/standalone/2015/dad-0.3.1-windows-vc12x86-2015-standalone.exe/download

https://sourceforge.net/projects/dad-mirror/files/standalone/2014/dad-0.3.1-windows-vc12x64-2014-standalone.exe/download

https://sourceforge.net/projects/dad-mirror/files/standalone/2014/dad-0.3.1-windows-vc12x86-2014-standalone.exe/download

This info also available at installers page:

http://dad.podsvirov.pro/house/installers

10.06.2016, 23:54, "Konstantin Podsvirov" :
> Hi guys! Hello developers!
>
> My "DaD's Project" is based on CMake and QtIFW (specifically CPackIFW) 
> continues its development:
>
> http://dad.podsvirov.pro - the official "DaD's House" website now.
>
> "DaD's House" is a resource where you can download the installers to install 
> necessary dependencies
> and immediately begin developing their projects.
>
> Already declared support 40 the following modules:
>
> Curses, ZLib, LibPNG, Jpeg, Libxml2, LibTIFF, Perl, OpenSSL, LibSSH2, cURL,
> PCRE, PROJ, Expat, FreeType, SQLite, GEOS, GDAL, Boost, Qt, QtIFW,
> CMake KDSoap, OSG, osgEarth, osgQtQuick, PostgreSQL, Apache.Apr, The 
> Apache.AprUtil, Apache.Httpd, Protobuf,
> gRPC, MapServer, Bullet, QCA, wxWidgets, LibXSLT, iconv, pgAdmin3, Wt, 
> FreeGLUT.
>
> Also available in 4 port:
>
>  - Windows Visual C++ Compiler 12.0 32bit
>  - Windows Visual C++ Compiler 12.0 64bit
>
> and NEW
>
>  - Windows 5.3.0 MinGW w64 32bit
>  - Windows 5.3.0 MinGW w64 64bit
>
> The last 2 ports have appeared recently and there are still large but 
> interesting work.
>
> All of this can be a good basis for your projects.
> All this is a good basis for my personal growth.
>
> I assess the status of the project as a Beta and write to lists for 
> developers of basic technologies.
>
> Open the curtain.
>
> For each module I have a small CMakeLists.txt:
>
> http://git.podsvirov.pro/?a=project_list;pf=dad/mod
>
> These scripts help me to build the modules and create a repository of binary 
> components.
>
> There is a need to spread content. All available here:
>
> http://download.podsvirov.pro
>
> My server is small and weak. I need help in distribution. I need a mirror 
> "main" module:
>
> rsync://podsvirov.pro
>
> If there are interested parties and you give me the address of the mirror, 
> then I can add them to MirrorBrain setup
> for more efficient distribution.
>
> If you are interested in developing this technology or already use my 
> installers, I would like to hear your opinion
> and to get feedback.
>
> Have a great weekend and good luck in development of your projects!
>
> --
> Regards,
> Konstantin Podsvirov
> --
>
> 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

Regards,
Konstantin Podsvirov
-- 

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] daemon-mode meeting last Tuesday

[Daniel Pfeifer]

On Fri, Jun 24, 2016 at 5:24 PM, Tobias Hunger  wrote:
> Hi Daniel,
>
> On Fri, Jun 24, 2016 at 5:08 PM, Daniel Pfeifer  
> wrote:
 Currently cmake-gui supports switching generators, build trees, etc., so
 there is some precedent for such switching within a single process.  If
 we have (re-)initialization bugs they should simply be fixed.
>>>
>>> So you opt for enabling the cmake-server to switch between different
>>> build directories?
>>
>> Clients who need this feature could simply restart the server in the
>> new directory.
>
> yes, that was what Stephen and me thought, too. I understood Brad to
> imply that we should just do everything inside server-mode and fix any
> fallout we run into instead.

I just opened cmake-gui and checked what exactly can be changed. There
is no graphical option to change the generator (you can change the
option sting in the cache, of course). When you change the binary
directory, it reads the cache from that directory, with the effect
that the source directory is changed too. To me, that feels like a
hard reset/restart.

To me it feels like the only reason why there is precedent for such
switching within a single process, is that cmake-gui links against
libcmake instead of using the cmake-server. I don't see any technical
reason apart from that it hasn't been split into two processes yet.
-- 

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] daemon-mode meeting last Tuesday

[Tobias Hunger]

Hi Daniel,

On Fri, Jun 24, 2016 at 5:08 PM, Daniel Pfeifer  wrote:
>>> Currently cmake-gui supports switching generators, build trees, etc., so
>>> there is some precedent for such switching within a single process.  If
>>> we have (re-)initialization bugs they should simply be fixed.
>>
>> So you opt for enabling the cmake-server to switch between different
>> build directories?
>
> Clients who need this feature could simply restart the server in the
> new directory.

yes, that was what Stephen and me thought, too. I understood Brad to
imply that we should just do everything inside server-mode and fix any
fallout we run into instead.

That is why I wanted to have this clarified, as this does cause quite
a few changes in the implementation.

Best Regards,
Tobias
-- 

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] Configuring CxxTest

[portolan]

Hello,
I setup my first cmake projet, but I have some problems with generating 
my CxxTest suite.
I can easily call up the CxxTest packgage and specify the generator 
using "CXXTEST_PYTHON_TESTGEN_EXECUTABLE" following the instruction of 
the documentation 
(https://cmake.org/cmake/help/v3.0/module/FindCxxTest.html)

.
But how can I specify parameters to the generator? Most notably I use a 
template so I would need to have something along the lines of 
"--template Runner.tpl".


Thanks,

Michele
--

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

Re: [cmake-developers] daemon-mode meeting last Tuesday

[Daniel Pfeifer]

On Fri, Jun 24, 2016 at 4:56 PM, Tobias Hunger  wrote:
> Hi Brad,
>
> On Thu, Jun 23, 2016 at 10:46 PM, Brad King  wrote:
>>>   * This is currently used to set sourcedirectory, builddirectory and
>>> generator.
>>>
>>> These three should be passed in via the command line instead, again
>>> to avoid trouble with users switching to different build 
>>> directories/etc.
>>> while the daemon is running, which might trigger problems with state
>>> cleanup, etc.
>>
>> Currently cmake-gui supports switching generators, build trees, etc., so
>> there is some precedent for such switching within a single process.  If
>> we have (re-)initialization bugs they should simply be fixed.
>
> So you opt for enabling the cmake-server to switch between different
> build directories?

Clients who need this feature could simply restart the server in the
new directory.
-- 

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] daemon-mode meeting last Tuesday

[Tobias Hunger]

Hi Brad,

On Thu, Jun 23, 2016 at 10:46 PM, Brad King  wrote:
>>   * This is currently used to set sourcedirectory, builddirectory and
>> generator.
>>
>> These three should be passed in via the command line instead, again
>> to avoid trouble with users switching to different build directories/etc.
>> while the daemon is running, which might trigger problems with state
>> cleanup, etc.
>
> Currently cmake-gui supports switching generators, build trees, etc., so
> there is some precedent for such switching within a single process.  If
> we have (re-)initialization bugs they should simply be fixed.

So you opt for enabling the cmake-server to switch between different
build directories?

That would have the following side-effects:

* We would need the reset command to get the server back into a defined state

* We need to keep it possible to set source directory, build directory
and generator from inside server mode

* We can keep the existing generators query-able from inside server
mode. If they are set inside server mode, then there is no need to
know them before starting server mode after all.

* The commandline way of querying generators is not necessary. We
might still want that, but it does not belong into this patch set
anymore.

Is this the way to do? I will need to back out some changes I did
since speaking with Stephen then. No problem, git has everything;-)

Best Regards,
Tobias
-- 

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] daemon-mode meeting last Tuesday

[Tobias Hunger]

Hallo Daniel,

On Fri, Jun 24, 2016 at 9:59 AM, Daniel Pfeifer  wrote:
> On Thu, Jun 23, 2016 at 2:27 PM, Tobias Hunger  wrote:
>>   * We both think it only makes sense to merge the infrastructure part into
>> cmake (if it passes review first of course) once we have some 
>> functionality
>> that is genuinely useful. So we want to aim at having the infrastructure
>> and the codemodel merged in one go.
>
> Please think about adding libuv earlier. As Brad wrote before, libuv
> could replace some #ifdef code that we currently have (process
> handling, file operations). I am currently refactoring the code around
> the cmOutputConverter and I would like to introduce a cmPath class (I
> will write more about that later, but I can already say that libuv
> might come handy for some functionality).

Feel free to merge it at your own pace. I'll just use your copy then:-)

Currently I just link to an external version of said library and have
not yet tried to figure out what the policy is wrt. 3rd party code in
cmake. Stephen suggested that we would need to include a copy into the
cmake repository and hinted at a script that keeps these copies
updated.

>>   2.7 cache (report contents of CMakeCache.txt file)
>>
>>   * Review by other potential users would be appreciated, but no obvious
>> problems seen.
>
> Is this needed? If the CMakeCache.txt file continues to be written,
> clients could just parse that file. If clients want to make changes
> (ie. cache editors), they can rewrite the file. Is that a problem? I
> assume it is, because CMake needs to reconfigure when it rereads it.
> In that case, the server should provide a way to report the contents,
> but also ways to modify it.

Yes, this is needed.

I do not want 3rd party code to interact with what is basically a file
internal to cmake.

And the syntax of that file is not as trivial as the comment at its
top claims it is. Just check how properties on values are encoded.

Best Regards,
Tobias
-- 

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] daemon-mode meeting last Tuesday

[Daniel Pfeifer]

On Thu, Jun 23, 2016 at 2:27 PM, Tobias Hunger  wrote:
>   * We both think it only makes sense to merge the infrastructure part into
> cmake (if it passes review first of course) once we have some 
> functionality
> that is genuinely useful. So we want to aim at having the infrastructure
> and the codemodel merged in one go.

Please think about adding libuv earlier. As Brad wrote before, libuv
could replace some #ifdef code that we currently have (process
handling, file operations). I am currently refactoring the code around
the cmOutputConverter and I would like to introduce a cmPath class (I
will write more about that later, but I can already say that libuv
might come handy for some functionality).

>   2.7 cache (report contents of CMakeCache.txt file)
>
>   * Review by other potential users would be appreciated, but no obvious
> problems seen.

Is this needed? If the CMakeCache.txt file continues to be written,
clients could just parse that file. If clients want to make changes
(ie. cache editors), they can rewrite the file. Is that a problem? I
assume it is, because CMake needs to reconfigure when it rereads it.
In that case, the server should provide a way to report the contents,
but also ways to modify it.

Cheers, Daniel

PS: Next meeting in a Biergarten in Munich?
-- 

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, next, updated. v3.6.0-rc3-525-g41a5113

[Daniel Pfeifer]

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  41a51131f9a253459577cbe4562be5dd368a517d (commit)
   via  8fd49ae83957bf1504a94a5ed2c8ccf89dbc5f09 (commit)
  from  272f159ea60d27ff817bd32335a8edcf2a994fcd (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=41a51131f9a253459577cbe4562be5dd368a517d
commit 41a51131f9a253459577cbe4562be5dd368a517d
Merge: 272f159 8fd49ae
Author: Daniel Pfeifer 
AuthorDate: Fri Jun 24 02:00:52 2016 -0400
Commit: CMake Topic Stage 
CommitDate: Fri Jun 24 02:00:52 2016 -0400

Merge topic 'compiler-features' into next

8fd49ae8 fixup! Make C++ feature checks extensible


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=8fd49ae83957bf1504a94a5ed2c8ccf89dbc5f09
commit 8fd49ae83957bf1504a94a5ed2c8ccf89dbc5f09
Author: Daniel Pfeifer 
AuthorDate: Fri Jun 24 07:58:35 2016 +0200
Commit: Daniel Pfeifer 
CommitDate: Fri Jun 24 07:59:31 2016 +0200

fixup! Make C++ feature checks extensible

diff --git a/Source/Checks/cm_cxx_features.cmake 
b/Source/Checks/cm_cxx_features.cmake
index 20a9348..18dbaf8 100644
--- a/Source/Checks/cm_cxx_features.cmake
+++ b/Source/Checks/cm_cxx_features.cmake
@@ -9,6 +9,10 @@ function(cm_check_cxx_feature name)
   CMAKE_FLAGS -DCMAKE_CXX_STANDARD=${CMAKE_CXX_STANDARD}
   OUTPUT_VARIABLE OUTPUT
   )
+# If using the feature causes warnings, treat it as broken/unavailable.
+if(OUTPUT MATCHES "warning")
+  set(CMake_HAVE_CXX_${FEATURE} OFF CACHE INTERNAL "TRY_COMPILE" FORCE)
+endif()
 if(CMake_HAVE_CXX_${FEATURE})
   message(STATUS "Checking if compiler supports C++ ${name} - yes")
   file(APPEND ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeOutput.log

---

Summary of changes:
 Source/Checks/cm_cxx_features.cmake |4 
 1 file changed, 4 insertions(+)


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