[Cmake-commits] CMake branch, master, updated. v3.10.1-744-g89ec1aa

[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  89ec1aacd781dcaf4aa0c6899bface518ac6afca (commit)
  from  e44c5828d368c81a1f478bf9c12ad4ff1bb87772 (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=89ec1aacd781dcaf4aa0c6899bface518ac6afca
commit 89ec1aacd781dcaf4aa0c6899bface518ac6afca
Author: Kitware Robot <kwro...@kitware.com>
AuthorDate: Wed Jan 10 00:01:50 2018 -0500
Commit: Kitware Robot <kwro...@kitware.com>
CommitDate: Wed Jan 10 00:01:50 2018 -0500

CMake Nightly Date Stamp

diff --git a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake
index 6fb5057..0a1834f 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 10)
-set(CMake_VERSION_PATCH 20180109)
+set(CMake_VERSION_PATCH 20180110)
 #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
https://cmake.org/mailman/listinfo/cmake-commits

Re: [CMake] include_directories converting CMAKE_BINARY_DIR into relative path

[Russell L. Carter]

Ah well, I figured out the problem, it was located between my
chair and my keyboard.  Everything works perfectly now.  I sure
do love cmake.

Thanks,
Russell

On 01/09/18 15:46, Russell L. Carter wrote:

Greetings,

I am trying to generate a platform specific file by copying it from
the source tree into a specific directory in the separate
out-of-source build tree.  The file generation works fine.

When I try the following cmake code:

set(target_dir ${CMAKE_BINARY_DIR}/nail/platform)
message("target_dir: ${target_dir}")
include_directories(${target_dir})

where message displays:

target_dir: /home/rcarter/nail/core/build/g++7.Debug/nail/platform

That's what I want and the generated files exist in that directory.

However, I get the following error:

FAILED: nail/CMakeFiles/nail_core.dir/platform/time.cpp.o
/usr/local/bin/g++7  -Dnail_core_EXPORTS -I../../ -Inail/platform -g -O 
-std=c++17 -fno-omit-frame-pointer -fstack-protector -Wall -Wextra 
-fvisibility=hidden -fvisibility-inlines-hidden -fPIC -MD -MT 
nail/CMakeFiles/nail_core.dir/platform/time.cpp.o -MF 
nail/CMakeFiles/nail_core.dir/platform/time.cpp.o.d -o 
nail/CMakeFiles/nail_core.dir/platform/time.cpp.o -c nail/platform/time.cpp
nail/platform/time.cpp:2:10: fatal error: nail/platform/time.hpp: No 
such file or directory


Evidently the include_directories() command is converting the
the supplied absolute path to a relative path (-Inail/platform).

What should I do to get that include directory in the
build tree added correctly to the includes?  I suppose I could
add it manually to the CXX flags?  What's the best cmake
friendly way to handle this?

Thanks,
Russell

--

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:
https://cmake.org/mailman/listinfo/cmake

[CMake] include_directories converting CMAKE_BINARY_DIR into relative path

[Russell L. Carter]

Greetings,

I am trying to generate a platform specific file by copying it from
the source tree into a specific directory in the separate
out-of-source build tree.  The file generation works fine.

When I try the following cmake code:

set(target_dir ${CMAKE_BINARY_DIR}/nail/platform)
message("target_dir: ${target_dir}")
include_directories(${target_dir})

where message displays:

target_dir: /home/rcarter/nail/core/build/g++7.Debug/nail/platform

That's what I want and the generated files exist in that directory.

However, I get the following error:

FAILED: nail/CMakeFiles/nail_core.dir/platform/time.cpp.o
/usr/local/bin/g++7  -Dnail_core_EXPORTS -I../../ -Inail/platform -g -O 
-std=c++17 -fno-omit-frame-pointer -fstack-protector -Wall -Wextra 
-fvisibility=hidden -fvisibility-inlines-hidden -fPIC -MD -MT 
nail/CMakeFiles/nail_core.dir/platform/time.cpp.o -MF 
nail/CMakeFiles/nail_core.dir/platform/time.cpp.o.d -o 
nail/CMakeFiles/nail_core.dir/platform/time.cpp.o -c nail/platform/time.cpp
nail/platform/time.cpp:2:10: fatal error: nail/platform/time.hpp: No 
such file or directory


Evidently the include_directories() command is converting the
the supplied absolute path to a relative path (-Inail/platform).

What should I do to get that include directory in the
build tree added correctly to the includes?  I suppose I could
add it manually to the CXX flags?  What's the best cmake
friendly way to handle this?

Thanks,
Russell
--

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:
https://cmake.org/mailman/listinfo/cmake

[Cmake-commits] CMake branch, master, updated. v3.10.1-743-ge44c582

[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  e44c5828d368c81a1f478bf9c12ad4ff1bb87772 (commit)
   via  81868e6badbb36947a6e89b0e97f2f0526d59a67 (commit)
  from  e40541339ae8a780bc410f0ef8b22d01e594c1ba (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=e44c5828d368c81a1f478bf9c12ad4ff1bb87772
commit e44c5828d368c81a1f478bf9c12ad4ff1bb87772
Merge: e405413 81868e6
Author: Craig Scott 
AuthorDate: Tue Jan 9 21:15:00 2018 +
Commit: Kitware Robot 
CommitDate: Tue Jan 9 16:15:11 2018 -0500

Merge topic 'add_cuda_to_source_regex'

81868e6b CUDA: Add cu as default source file extension

Acked-by: Kitware Robot 
Acked-by: Brad King 
Merge-request: !1629


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=81868e6badbb36947a6e89b0e97f2f0526d59a67
commit 81868e6badbb36947a6e89b0e97f2f0526d59a67
Author: Robert Maynard 
AuthorDate: Wed Jan 3 09:22:47 2018 -0500
Commit: Robert Maynard 
CommitDate: Mon Jan 8 16:16:52 2018 -0500

CUDA: Add cu as default source file extension

diff --git a/Source/cmExtraCodeBlocksGenerator.cxx 
b/Source/cmExtraCodeBlocksGenerator.cxx
index edce330..31c8bca 100644
--- a/Source/cmExtraCodeBlocksGenerator.cxx
+++ b/Source/cmExtraCodeBlocksGenerator.cxx
@@ -371,10 +371,10 @@ void cmExtraCodeBlocksGenerator::CreateNewProjectFile(
   continue;
 }
 
-// check whether it is a C/C++ implementation file
+// check whether it is a C/C++/CUDA implementation file
 bool isCFile = false;
 std::string lang = s->GetLanguage();
-if (lang == "C" || lang == "CXX") {
+if (lang == "C" || lang == "CXX" || lang == "CUDA") {
   std::string const& srcext = s->GetExtension();
   isCFile = cm->IsSourceExtension(srcext);
 }
diff --git a/Source/cmExtraCodeLiteGenerator.cxx 
b/Source/cmExtraCodeLiteGenerator.cxx
index 383942b..4958007 100644
--- a/Source/cmExtraCodeLiteGenerator.cxx
+++ b/Source/cmExtraCodeLiteGenerator.cxx
@@ -227,10 +227,10 @@ std::string cmExtraCodeLiteGenerator::CollectSourceFiles(
   gt->GetSourceFiles(sources,
  makefile->GetSafeDefinition("CMAKE_BUILD_TYPE"));
   for (cmSourceFile* s : sources) {
-// check whether it is a C/C++ implementation file
+// check whether it is a C/C++/CUDA implementation file
 bool isCFile = false;
 std::string lang = s->GetLanguage();
-if (lang == "C" || lang == "CXX") {
+if (lang == "C" || lang == "CXX" || lang == "CUDA") {
   std::string const& srcext = s->GetExtension();
   isCFile = cm->IsSourceExtension(srcext);
 }
diff --git a/Source/cmMakefile.cxx b/Source/cmMakefile.cxx
index a1e2f63..9fb8001 100644
--- a/Source/cmMakefile.cxx
+++ b/Source/cmMakefile.cxx
@@ -967,7 +967,7 @@ void cmMakefile::AddCustomCommandOldStyle(
   }
 
   // Each output must get its own copy of this rule.
-  cmsys::RegularExpression sourceFiles("\\.(C|M|c|c\\+\\+|cc|cpp|cxx|m|mm|"
+  cmsys::RegularExpression sourceFiles("\\.(C|M|c|c\\+\\+|cc|cpp|cxx|cu|m|mm|"
"rc|def|r|odl|idl|hpj|bat|h|h\\+\\+|"
"hm|hpp|hxx|in|txx|inl)$");
   for (std::string const& oi : outputs) {
diff --git a/Source/cmSourceFile.h b/Source/cmSourceFile.h
index c2105d2..da722ea 100644
--- a/Source/cmSourceFile.h
+++ b/Source/cmSourceFile.h
@@ -120,7 +120,8 @@ private:
 #define CM_HEADER_REGEX "\\.(h|hh|h\\+\\+|hm|hpp|hxx|in|txx|inl)$"
 
 #define CM_SOURCE_REGEX   \
-  "\\.(C|M|c|c\\+\\+|cc|cpp|cxx|f|f90|for|fpp|ftn|m|mm|rc|def|r|odl|idl|hpj"  \
+  "\\.(C|M|c|c\\+\\+|cc|cpp|cxx|cu|f|f90|for|fpp|ftn|m|mm|rc|def|r|odl|idl|"  \
+  "hpj"   \
   "|bat)$"
 
 #define CM_RESOURCE_REGEX "\\.(pdf|plist|png|jpeg|jpg|storyboard|xcassets)$"
diff --git a/Source/cmSystemTools.cxx b/Source/cmSystemTools.cxx
index 5d1f5f7..c321236 100644
--- a/Source/cmSystemTools.cxx
+++ b/Source/cmSystemTools.cxx
@@ -1308,6 +1308,9 @@ cmSystemTools::FileFormat 
cmSystemTools::GetFileFormat(const char* cext)
   if (ext == "java" || ext == ".java") {
 return cmSystemTools::JAVA_FILE_FORMAT;
   }
+  if (ext == "cu" || ext == ".cu") {
+return cmSystemTools::CUDA_FILE_FORMAT;
+  }
   if (ext == "H" || ext == ".H" || 

Re: [CMake] Multiple cross compiling

[Robert Maynard]

Currently CMake only supports a single platform / toolchain per build directory.

If you need to build with multiple toolchains you will need to use
some form of a wrapper. Which can either be an external script that
invokes CMake multiple times or a CMake project that uses
ExternalProject (
https://cmake.org/cmake/help/latest/module/ExternalProject.html )


On Mon, Jan 8, 2018 at 2:44 PM, szymon zakrent  wrote:
> Is there a way to make cmake cross compile automatically for multiple
> platforms at the same time without running cmake multiple times with
> different toolchains?
>
> --
>
> 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:
> https://cmake.org/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:
https://cmake.org/mailman/listinfo/cmake

Re: [CMake] how to detect architecture ?

[Franck Houssen]

Thanks ! 

- Mail original -
> De: "Konstantin Tokarev" 
> À: "Franck Houssen" , "CMake Mail List" 
> 
> Envoyé: Mardi 9 Janvier 2018 16:00:55
> Objet: Re: [CMake] how to detect architecture ?
> 
> 
> 
> 09.01.2018, 17:58, "Franck Houssen" :
> > Is there a way to detect architecture ?
> >
> > Seems there is nothing simple since these old threads :
> > https://stackoverflow.com/questions/11944060/how-to-detect-target-architecture-using-cmake/12024211#12024211
> > https://stackoverflow.com/questions/16796629/cmake-create-architecture-aware-makefile
> >
> > Is there a solution now ?
> >
> > My need is quite simple: I have an executable who needs dlopen. To test it,
> > I planned to write a bash script that would have done "./exe
> > /path/to/lib.so" on linux (debian, ...) OR "./exe /path/to/lib.dylib" on
> > osx. To replace correctly so/dylib in the bash script I need to know the
> > architecture. Any idea how to do this ?
> 
> ${CMAKE_SHARED_LIBRARY_SUFFIX}
> 

Oh man ! Didn't know this one : exactly what I was looking for

> > Franck
> > ,--
> >
> > 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:
> > https://cmake.org/mailman/listinfo/cmake
> 
> 
> --
> Regards,
> Konstantin
> 
-- 

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:
https://cmake.org/mailman/listinfo/cmake

Re: [CMake] how to detect architecture ?

[J Decker]

On Tue, Jan 9, 2018 at 6:57 AM, Franck Houssen 
wrote:

> Is there a way to detect architecture ?
>
> Seems there is nothing simple since these old threads :
> https://stackoverflow.com/questions/11944060/how-to-
> detect-target-architecture-using-cmake/12024211#12024211
> https://stackoverflow.com/questions/16796629/cmake-
> create-architecture-aware-makefile
>
> Is there a solution now ?
>
> My need is quite simple: I have an executable who needs dlopen. To test
> it, I planned to write a bash script that would have done "./exe
> /path/to/lib.*so*" on linux (debian, ...) OR "./exe /path/to/lib.*dylib*"
> on osx. To replace correctly so/dylib in the bash script I need to know the
> architecture. Any idea how to do this ?
>
>
https://cmake.org/Wiki/CMake_Useful_Variables
https://cmake.org/Wiki/CMake_Checking_Platform

if( APPLE )
   install( PROGRAMS apple.script.sh DESTINATION script.sh )
elseif( UNIX )
   install( PROGRAMS linux.script.sh DESTINATION script.sh )
endif( )
# not sure what the correct tag in endif should be.

so you can just keep 2 scripts and install approrpiately


> Franck
>
> --
>
> 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:
> https://cmake.org/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:
https://cmake.org/mailman/listinfo/cmake

Re: [CMake] how to detect architecture ?

[Konstantin Tokarev]

09.01.2018, 17:58, "Franck Houssen" :
> Is there a way to detect architecture ?
>
> Seems there is nothing simple since these old threads :
> https://stackoverflow.com/questions/11944060/how-to-detect-target-architecture-using-cmake/12024211#12024211
> https://stackoverflow.com/questions/16796629/cmake-create-architecture-aware-makefile
>
> Is there a solution now ?
>
> My need is quite simple: I have an executable who needs dlopen. To test it, I 
> planned to write a bash script that would have done "./exe /path/to/lib.so" 
> on linux (debian, ...) OR "./exe /path/to/lib.dylib" on osx. To replace 
> correctly so/dylib in the bash script I need to know the architecture. Any 
> idea how to do this ?

${CMAKE_SHARED_LIBRARY_SUFFIX}

> Franck
> ,--
>
> 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:
> https://cmake.org/mailman/listinfo/cmake


-- 
Regards,
Konstantin
-- 

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:
https://cmake.org/mailman/listinfo/cmake

[CMake] how to detect architecture ?

[Franck Houssen]

Is there a way to detect architecture ? 

Seems there is nothing simple since these old threads : 
https://stackoverflow.com/questions/11944060/how-to-detect-target-architecture-using-cmake/12024211#12024211
 
https://stackoverflow.com/questions/16796629/cmake-create-architecture-aware-makefile
 

Is there a solution now ? 

My need is quite simple: I have an executable who needs dlopen. To test it, I 
planned to write a bash script that would have done "./exe /path/to/lib. so " 
on linux (debian, ...) OR "./exe /path/to/lib. dylib " on osx. To replace 
correctly so/dylib in the bash script I need to know the architecture. Any idea 
how to do this ? 

Franck 
-- 

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:
https://cmake.org/mailman/listinfo/cmake

[Cmake-commits] CMake branch, release, updated. v3.10.1-6-g9559eb7

[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, release has been updated
   via  9559eb7aa7bcb267f49bb304075ef952660753ee (commit)
   via  9417a6d322fbb943217abd02358dab21689c (commit)
  from  c69ce01d44fc0dc876aa8d9c4e6e2edd97619a4b (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 -
---

Summary of changes:
 Modules/FindPostgreSQL.cmake |4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)


hooks/post-receive
-- 
CMake
___
Cmake-commits mailing list
Cmake-commits@cmake.org
https://cmake.org/mailman/listinfo/cmake-commits

[Cmake-commits] CMake branch, master, updated. v3.10.1-741-ge405413

[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  e40541339ae8a780bc410f0ef8b22d01e594c1ba (commit)
   via  ce629c5ddeb7d4a87ac287c293fb164099812ca2 (commit)
   via  9559eb7aa7bcb267f49bb304075ef952660753ee (commit)
   via  9417a6d322fbb943217abd02358dab21689c (commit)
  from  ae89a6e110badd54c1aa8a2957f15e260224c7df (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=e40541339ae8a780bc410f0ef8b22d01e594c1ba
commit e40541339ae8a780bc410f0ef8b22d01e594c1ba
Merge: ce629c5 9559eb7
Author: Brad King 
AuthorDate: Tue Jan 9 09:45:58 2018 -0500
Commit: Brad King 
CommitDate: Tue Jan 9 09:45:58 2018 -0500

Merge branch 'release-3.10'


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=ce629c5ddeb7d4a87ac287c293fb164099812ca2
commit ce629c5ddeb7d4a87ac287c293fb164099812ca2
Merge: ae89a6e 9417a6d
Author: Brad King 
AuthorDate: Tue Jan 9 14:45:41 2018 +
Commit: Kitware Robot 
CommitDate: Tue Jan 9 09:45:45 2018 -0500

Merge topic 'FindPostgres_support_for_v10'

9417a6d3 FindPostgreSQL: Add support for PG10

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


---

Summary of changes:
 Modules/FindPostgreSQL.cmake |4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)


hooks/post-receive
-- 
CMake
___
Cmake-commits mailing list
Cmake-commits@cmake.org
https://cmake.org/mailman/listinfo/cmake-commits

[Cmake-commits] CMake branch, master, updated. v3.10.1-737-gae89a6e

[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  ae89a6e110badd54c1aa8a2957f15e260224c7df (commit)
   via  1906dd3e3d63b18784e551cb3c21b02a073dab34 (commit)
   via  2cd2dd9cdefa283cdf42008c9b8e6116b6f78ec3 (commit)
   via  947d6de8339d13422aa2c0b018b125f07c1003d3 (commit)
   via  118815f095e9737dc05806a4d6734a3b9de37e39 (commit)
   via  6c5d3989f71d9a1952a508404e858965fd320010 (commit)
   via  edebf6f31ad33d4b2d69eb7ccaf2de1e94abe5fb (commit)
   via  e41536405884fc3d6342748a20cc3f391d4a3221 (commit)
  from  847110e6faeffb85d12a1c145b3846263ee35bdc (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=ae89a6e110badd54c1aa8a2957f15e260224c7df
commit ae89a6e110badd54c1aa8a2957f15e260224c7df
Merge: 1906dd3 e415364
Author: Brad King 
AuthorDate: Tue Jan 9 14:37:58 2018 +
Commit: Kitware Robot 
CommitDate: Tue Jan 9 09:38:02 2018 -0500

Merge topic 'cpack_versions'

e4153640 Cpack.cmake: Document some CPACK_* default values

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


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=1906dd3e3d63b18784e551cb3c21b02a073dab34
commit 1906dd3e3d63b18784e551cb3c21b02a073dab34
Merge: 2cd2dd9 118815f
Author: Brad King 
AuthorDate: Tue Jan 9 14:36:24 2018 +
Commit: Kitware Robot 
CommitDate: Tue Jan 9 09:36:29 2018 -0500

Merge topic 'COMPILE_FLAGS-clarify-sf-prop-documentation'

118815f0 COMPILE_FLAGS: do not imply that the property is a list

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


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=2cd2dd9cdefa283cdf42008c9b8e6116b6f78ec3
commit 2cd2dd9cdefa283cdf42008c9b8e6116b6f78ec3
Merge: 947d6de edebf6f
Author: Brad King 
AuthorDate: Tue Jan 9 14:35:28 2018 +
Commit: Kitware Robot 
CommitDate: Tue Jan 9 09:35:46 2018 -0500

Merge topic 'doc-CMAKE_SYSTEM_NAME-mode'

edebf6f3 Help: note that CMAKE_SYSTEM_NAME is not set in script mode

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


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=947d6de8339d13422aa2c0b018b125f07c1003d3
commit 947d6de8339d13422aa2c0b018b125f07c1003d3
Merge: 847110e 6c5d398
Author: Brad King 
AuthorDate: Tue Jan 9 14:35:15 2018 +
Commit: Kitware Robot 
CommitDate: Tue Jan 9 09:35:19 2018 -0500

Merge topic 'doc-OUTPUT_NAME-clarify'

6c5d3989 Help: fix documentation for OUTPUT_NAME

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


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=118815f095e9737dc05806a4d6734a3b9de37e39
commit 118815f095e9737dc05806a4d6734a3b9de37e39
Author: Ben Boeckel 
AuthorDate: Mon Jan 8 11:36:40 2018 -0500
Commit: Ben Boeckel 
CommitDate: Mon Jan 8 11:44:18 2018 -0500

COMPILE_FLAGS: do not imply that the property is a list

The "added to the list" language hinted that the property was
interpreted as a CMake list, but this is not correct. It is just a
string.

diff --git a/Help/prop_sf/COMPILE_FLAGS.rst b/Help/prop_sf/COMPILE_FLAGS.rst
index 1012164..be81cf6 100644
--- a/Help/prop_sf/COMPILE_FLAGS.rst
+++ b/Help/prop_sf/COMPILE_FLAGS.rst
@@ -3,9 +3,9 @@ COMPILE_FLAGS
 
 Additional flags to be added when compiling this source file.
 
-These flags will be added to the list of compile flags when this
-source file builds.  Use :prop_sf:`COMPILE_DEFINITIONS` to pass
-additional preprocessor definitions.
+The ``COMPILE_FLAGS`` property sets additional compiler flags used to build
+source files.  Use :prop_sf:`COMPILE_DEFINITIONS` to pass additional
+preprocessor definitions.
 
 Contents of ``COMPILE_FLAGS`` may use "generator expressions"
 with the syntax ``$<...>``.  See the :manual:`cmake-generator-expressions(7)`

https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=6c5d3989f71d9a1952a508404e858965fd320010
commit 6c5d3989f71d9a1952a508404e858965fd320010
Author: Kyle Edwards 
AuthorDate: Wed Jan 3 11:09:21 2018 -0500
Commit: Kyle Edwards 
CommitDate: Mon Jan 8 11:33:05 2018 -0500

Help: fix documentation for OUTPUT_NAME

Fixes #17177.

diff --git a/Help/prop_tgt/OUTPUT_NAME.rst b/Help/prop_tgt/OUTPUT_NAME.rst
index f1bdb7c..4b33b38 100644
--- a/Help/prop_tgt/OUTPUT_NAME.rst

[Cmake-commits] CMake branch, master, updated. v3.10.1-729-g847110e

[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  847110e6faeffb85d12a1c145b3846263ee35bdc (commit)
   via  e2edc9280c86d99e39412ec19be23dd366c70695 (commit)
   via  5fbfa18fadf945963687cd95627c1bc62b68948a (commit)
   via  bc88329e5ba7b1a14538f23f4fa223ac8d6d5895 (commit)
   via  fab1b432eb1207513bee57039ecb21d95f880f89 (commit)
   via  ff41a4b817749be1e51ebb6ab15bab6f0e488139 (commit)
   via  d09af9461964d22d6946893b52b82c5c9a752f28 (commit)
   via  92c7b5260795153f4152e8562a7abac3d6d77d8a (commit)
  from  89d12746306571a323549ad0f8d11284999053d5 (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=847110e6faeffb85d12a1c145b3846263ee35bdc
commit 847110e6faeffb85d12a1c145b3846263ee35bdc
Merge: e2edc92 d09af94
Author: Brad King 
AuthorDate: Tue Jan 9 14:33:39 2018 +
Commit: Kitware Robot 
CommitDate: Tue Jan 9 09:34:08 2018 -0500

Merge topic 'vs10-target-generator-range-for'

d09af946 VS: Modernize 'for' loops in cmVisualStudio10TargetGenerator to 
C++11

Acked-by: Kitware Robot 
Acked-by: Ben Boeckel 
Merge-request: !1617


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=e2edc9280c86d99e39412ec19be23dd366c70695
commit e2edc9280c86d99e39412ec19be23dd366c70695
Merge: 5fbfa18 92c7b52
Author: Brad King 
AuthorDate: Tue Jan 9 14:33:29 2018 +
Commit: Kitware Robot 
CommitDate: Tue Jan 9 09:33:33 2018 -0500

Merge topic 'vs-ranged-for'

92c7b526 VS: Use range-based 'for' loops in generator code

Acked-by: Kitware Robot 
Acked-by: Ben Boeckel 
Merge-request: !1616


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=5fbfa18fadf945963687cd95627c1bc62b68948a
commit 5fbfa18fadf945963687cd95627c1bc62b68948a
Merge: bc88329 ff41a4b
Author: Brad King 
AuthorDate: Tue Jan 9 14:26:35 2018 +
Commit: Kitware Robot 
CommitDate: Tue Jan 9 09:26:51 2018 -0500

Merge topic 'FindCUDA-deduplicate-c+std-host-flags'

ff41a4b8 FindCUDA: de-duplicates C++11 flag when propagating host flags.

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


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=bc88329e5ba7b1a14538f23f4fa223ac8d6d5895
commit bc88329e5ba7b1a14538f23f4fa223ac8d6d5895
Merge: 89d1274 fab1b43
Author: Brad King 
AuthorDate: Tue Jan 9 14:26:16 2018 +
Commit: Kitware Robot 
CommitDate: Tue Jan 9 09:26:20 2018 -0500

Merge topic 'msvc2017-findcuda'

fab1b432 FindCUDA: Update to properly find MSVC 2017 compiler tools

Acked-by: Kitware Robot 
Acked-by: Robert Maynard 
Merge-request: !1631


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=fab1b432eb1207513bee57039ecb21d95f880f89
commit fab1b432eb1207513bee57039ecb21d95f880f89
Author: Aaron Bray 
AuthorDate: Wed Jan 3 11:18:34 2018 -0500
Commit: Aaron Bray 
CommitDate: Mon Jan 8 11:35:36 2018 -0500

FindCUDA: Update to properly find MSVC 2017 compiler tools

An implementation that handles the different installation locations of
visual studio compiler tools

diff --git a/Modules/FindCUDA.cmake b/Modules/FindCUDA.cmake
index 04b5cf9..0b63e04 100644
--- a/Modules/FindCUDA.cmake
+++ b/Modules/FindCUDA.cmake
@@ -98,12 +98,13 @@
 #   CUDA_HOST_COMPILATION_CPP (Default ON)
 #   -- Set to OFF for C compilation of host code.
 #
-#   CUDA_HOST_COMPILER (Default CMAKE_C_COMPILER, $(VCInstallDir)/bin for VS)
+#   CUDA_HOST_COMPILER (Default CMAKE_C_COMPILER)
 #   -- Set the host compiler to be used by nvcc.  Ignored if -ccbin or
 #  --compiler-bindir is already present in the CUDA_NVCC_FLAGS or
-#  CUDA_NVCC_FLAGS_ variables.  For Visual Studio targets
-#  $(VCInstallDir)/bin is a special value that expands out to the path when
-#  the command is run from within VS.
+#  CUDA_NVCC_FLAGS_ variables.  For Visual Studio targets,
+#  the host compiler is constructed with one or more visual studio macros
+#  such as $(VCInstallDir), that expands out to the path when
+#  the command is run from withing VS.
 #
 #   CUDA_NVCC_FLAGS
 #   CUDA_NVCC_FLAGS_
@@ -527,7 +528,13 @@ option(CUDA_HOST_COMPILATION_CPP "Generated file 
extension" ON)
 set(CUDA_NVCC_FLAGS "" CACHE STRING 

Re: [CMake] how to port to cmake a project using gnulib

[Alan W. Irwin]

On 2018-01-09 12:01- Cosimo Lupo wrote:


Hello,

I'm new to Cmake.

I would like to port to cmake a project that is currently built with the
Autotools and depends on gnulib, the GNU Portability Library:
https://www.gnu.org/software/gnulib/

(The project in question is https://www.freetype.org/ttfautohint/)

It appears that gnulib itself is very much tied with
autoconf/automake/libtool.

In fact I couldn't find any examples of other CMake based projects that use
gnulib.

Does anyone has any tips or examples on how I could proceed?


Hi Cosimo:

I have looked at the subsequent list traffic responding to your
question above, and there
appeared to be a clear need for a description of what gnulib really
is.  That is provided by  which
states that gnulib is the GNU Portability Library that is apparently
designed to aid portability of software to different operating systems.
That description of gnulib further
states (in part):

"Gnulib [...] components are intended to be
shared at the source level, rather than being a library that gets
built, installed, and linked against. Thus, there is no distribution
tarball; the idea is to copy files from Gnulib into your own source
tree."

However, I think because gnulib is all about aiding portability and
CMake already is designed to do that task, you likely won't need
gnulib at all once you implement a CMake-based build system for your
own software.  I base that opinion on the general complete lack of
knowledge (including me before I got curious and read the above
description of gnulib) concerning gnulib here.  However, if it turns
out there is still some small useful component of gnulib C source code
that would be useful for your own project, it is an absolutely simple
matter under CMake to build a mixture of library source code from your
project's source directories and some subset of the source code from
the gnulib source directories.

So my best advice is don't be concerned about gnulib executables or
autotools-related cruft at all.  That is, don't be concerned in the
slightest about gnulib unless there is some specific place in your
source code that calls one of the gnulib routines.  And take care
of that case with CMake as indicated above.

Alan
__
Alan W. Irwin

Astronomical research affiliation with Department of Physics and Astronomy,
University of Victoria (astrowww.phys.uvic.ca).

Programming affiliations with the FreeEOS equation-of-state
implementation for stellar interiors (freeeos.sf.net); the Time
Ephemerides project (timeephem.sf.net); PLplot scientific plotting
software package (plplot.sf.net); the libLASi project
(unifont.org/lasi); the Loads of Linux Links project (loll.sf.net);
and the Linux Brochure Project (lbproject.sf.net).
__

Linux-powered Science
__
--

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:
https://cmake.org/mailman/listinfo/cmake

Re: [CMake] how to port to cmake a project using gnulib

[Konstantin Tokarev]

Alfred: Gnulib isn't library in usual sense, AFAIK it's a bunch of source files 
some of which
may be added to the project if needed

Cosimo: I think you should stay with autotools, otherwsie it might be a can of 
worms.
Or get rid of gnulib.


09.01.2018, 15:55, "Cosimo Lupo" :
> This is from the gnulib mailing list in reply to a similar question on how to 
> use gnulib without autotools:
>
> https://lists.gnu.org/archive/html/bug-gnulib/2010-02/msg00248.html
>
> "Gnulib depends heavily on autoconf and automake.
> You could manually extract the portions you think you need
> and attempt to use them without the requisite glue, but that is
> very error-prone."
>
> :,(
>
> On Tue, Jan 9, 2018 at 12:50 PM Cosimo Lupo  wrote:
>> Thanks for your help, Alfred.
>>
>> The problem is that very concept of "external dependency" seems to be at 
>> odds with the way gnulib is supposed to work.
>>
>> And the docs are clear that "Gnulib assumes that your project uses Autoconf. 
>> When using Gnulib, you will need to have Autoconf among your build tools."
>>
>> https://www.gnu.org/software/gnulib/manual/html_node//Initial-import.html#Initial-import
>>
>> Anyway, let's see if others have any more clues.
>>
>> Cheers
>>
>> Cosimo
>>
>> On Tue, Jan 9, 2018 at 12:36 PM Alfred Sawaya  wrote:
>>> Sorry, I did not got this hint.
>>>
>>> Well, you might still use gnulib as an external dependency 
>>> (https://www.gnu.org/software/gnulib/manual/html_node/POSIX-Substitutes-Library.html#POSIX-Substitutes-Library).
>>>  Maybe be it worth considering a better separation if the build tool is 
>>> different.
>>>
>>> I need to read more about gnulib to give you a better answer. Maybe someone 
>>> already has a clue on the list.
>>>
>>> Regards,
>>>
>>> Cordialement,
>>>
>>> Alfred Sawaya
>>>
>>> De: cos...@anthrotype.com
>>> Envoyé: 9 janvier 2018 1:17 PM
>>> À: alf...@huji.fr
>>> Cc: cmake@cmake.org
>>> Objet: Re: [CMake] how to port to cmake a project using gnulib
>>> Thanks.
>>> However, that's not exactly what I was looking for. The gnulib, by design, 
>>> is not an external library that you link with, but a collection of modules 
>>> that are meant to be copied into one's project.
>>> I would like to build ttfautohint with cmake (and ninja), not just adding 
>>> ttfautohint as an external project built with autotools and GNU make.
>>>
>>> On Tue, Jan 9, 2018 at 12:10 PM Alfred Sawaya  wrote:
 Hello,

 I have some CMake projects that depend on autotools bases libs.
 I compile them as External project.

 https://cmake.org/cmake/help/latest/module/ExternalProject.html

 Regards

 Cordialement,

 Alfred Sawaya

 De: cos...@anthrotype.com
 Envoyé: 9 janvier 2018 1:01 PM
 À: cmake@cmake.org
 Objet: [CMake] how to port to cmake a project using gnulib
 Hello,

 I'm new to Cmake.

 I would like to port to cmake a project that is currently built with the 
 Autotools and depends on gnulib, the GNU Portability Library: 
 https://www.gnu.org/software/gnulib/

 (The project in question is https://www.freetype.org/ttfautohint/)

 It appears that gnulib itself is very much tied with 
 autoconf/automake/libtool.

 In fact I couldn't find any examples of other CMake based projects that 
 use gnulib.

 Does anyone has any tips or examples on how I could proceed?

 Thank you,

 Cosimo Lupo

 --
 Cosimo Lupo
>>>
>>> --
>>> Cosimo Lupo
>>
>> --
>> Cosimo Lupo
>
> --
> Cosimo Lupo
> ,--
>
> 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:
> https://cmake.org/mailman/listinfo/cmake


-- 
Regards,
Konstantin
-- 

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:
https://cmake.org/mailman/listinfo/cmake

Re: [CMake] how to port to cmake a project using gnulib

[Cosimo Lupo]

This is from the gnulib mailing list in reply to a similar question on how
to use gnulib without autotools:

https://lists.gnu.org/archive/html/bug-gnulib/2010-02/msg00248.html

"Gnulib depends heavily on autoconf and automake.
You could manually extract the portions you think you need
and attempt to use them without the requisite glue, but that is
very error-prone."

:,(


On Tue, Jan 9, 2018 at 12:50 PM Cosimo Lupo  wrote:

> Thanks for your help, Alfred.
>
> The problem is that very concept of "external dependency" seems to be at
> odds with the way gnulib is supposed to work.
>
> And the docs are clear that "Gnulib assumes that your project uses
> Autoconf. When using Gnulib, you will need to have Autoconf among your
> build tools."
>
>
> https://www.gnu.org/software/gnulib/manual/html_node//Initial-import.html#Initial-import
>
> Anyway, let's see if others have any more clues.
>
> Cheers
>
> Cosimo
>
>
>
> On Tue, Jan 9, 2018 at 12:36 PM Alfred Sawaya  wrote:
>
>> Sorry, I did not got this hint.
>>
>> Well, you might still use gnulib as an external dependency (
>> https://www.gnu.org/software/gnulib/manual/html_node/POSIX-Substitutes-Library.html#POSIX-Substitutes-Library).
>> Maybe be it worth considering a better separation if the build tool is
>> different.
>>
>> I need to read more about gnulib to give you a better answer. Maybe
>> someone already has a clue on the list.
>>
>> Regards,
>>
>> Cordialement,
>>
>> Alfred Sawaya
>> *De:* cos...@anthrotype.com
>> *Envoyé:* 9 janvier 2018 1:17 PM
>> *À:* alf...@huji.fr
>> *Cc:* cmake@cmake.org
>> *Objet:* Re: [CMake] how to port to cmake a project using gnulib
>>
>> Thanks.
>> However, that's not exactly what I was looking for. The gnulib, by
>> design, is not an external library that you link with, but a collection of
>> modules that are meant to be copied into one's project.
>> I would like to build ttfautohint with cmake (and ninja), not just adding
>> ttfautohint as an external project built with autotools and GNU make.
>>
>>
>> On Tue, Jan 9, 2018 at 12:10 PM Alfred Sawaya  wrote:
>>
>>> Hello,
>>>
>>> I have some CMake projects that depend on autotools bases libs.
>>> I compile them as External project.
>>>
>>> https://cmake.org/cmake/help/latest/module/ExternalProject.html
>>>
>>> Regards
>>>
>>> Cordialement,
>>>
>>> Alfred Sawaya
>>> *De:* cos...@anthrotype.com
>>> *Envoyé:* 9 janvier 2018 1:01 PM
>>> *À:* cmake@cmake.org
>>> *Objet:* [CMake] how to port to cmake a project using gnulib
>>>
>>> Hello,
>>>
>>> I'm new to Cmake.
>>>
>>> I would like to port to cmake a project that is currently built with the
>>> Autotools and depends on gnulib, the GNU Portability Library:
>>> https://www.gnu.org/software/gnulib/
>>>
>>> (The project in question is https://www.freetype.org/ttfautohint/)
>>>
>>> It appears that gnulib itself is very much tied with
>>> autoconf/automake/libtool.
>>>
>>> In fact I couldn't find any examples of other CMake based projects that
>>> use gnulib.
>>>
>>> Does anyone has any tips or examples on how I could proceed?
>>>
>>> Thank you,
>>>
>>> Cosimo Lupo
>>>
>>>
>>> --
>>> Cosimo Lupo
>>>
>>
>>
>> --
>> Cosimo Lupo
>>
>
>
> --
> Cosimo Lupo
>


-- 
Cosimo Lupo
-- 

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:
https://cmake.org/mailman/listinfo/cmake

Re: [CMake] how to port to cmake a project using gnulib

[Cosimo Lupo]

Thanks for your help, Alfred.

The problem is that very concept of "external dependency" seems to be at
odds with the way gnulib is supposed to work.

And the docs are clear that "Gnulib assumes that your project uses
Autoconf. When using Gnulib, you will need to have Autoconf among your
build tools."

https://www.gnu.org/software/gnulib/manual/html_node//Initial-import.html#Initial-import

Anyway, let's see if others have any more clues.

Cheers

Cosimo



On Tue, Jan 9, 2018 at 12:36 PM Alfred Sawaya  wrote:

> Sorry, I did not got this hint.
>
> Well, you might still use gnulib as an external dependency (
> https://www.gnu.org/software/gnulib/manual/html_node/POSIX-Substitutes-Library.html#POSIX-Substitutes-Library).
> Maybe be it worth considering a better separation if the build tool is
> different.
>
> I need to read more about gnulib to give you a better answer. Maybe
> someone already has a clue on the list.
>
> Regards,
>
> Cordialement,
>
> Alfred Sawaya
> *De:* cos...@anthrotype.com
> *Envoyé:* 9 janvier 2018 1:17 PM
> *À:* alf...@huji.fr
> *Cc:* cmake@cmake.org
> *Objet:* Re: [CMake] how to port to cmake a project using gnulib
>
> Thanks.
> However, that's not exactly what I was looking for. The gnulib, by design,
> is not an external library that you link with, but a collection of modules
> that are meant to be copied into one's project.
> I would like to build ttfautohint with cmake (and ninja), not just adding
> ttfautohint as an external project built with autotools and GNU make.
>
>
> On Tue, Jan 9, 2018 at 12:10 PM Alfred Sawaya  wrote:
>
>> Hello,
>>
>> I have some CMake projects that depend on autotools bases libs.
>> I compile them as External project.
>>
>> https://cmake.org/cmake/help/latest/module/ExternalProject.html
>>
>> Regards
>>
>> Cordialement,
>>
>> Alfred Sawaya
>> *De:* cos...@anthrotype.com
>> *Envoyé:* 9 janvier 2018 1:01 PM
>> *À:* cmake@cmake.org
>> *Objet:* [CMake] how to port to cmake a project using gnulib
>>
>> Hello,
>>
>> I'm new to Cmake.
>>
>> I would like to port to cmake a project that is currently built with the
>> Autotools and depends on gnulib, the GNU Portability Library:
>> https://www.gnu.org/software/gnulib/
>>
>> (The project in question is https://www.freetype.org/ttfautohint/)
>>
>> It appears that gnulib itself is very much tied with
>> autoconf/automake/libtool.
>>
>> In fact I couldn't find any examples of other CMake based projects that
>> use gnulib.
>>
>> Does anyone has any tips or examples on how I could proceed?
>>
>> Thank you,
>>
>> Cosimo Lupo
>>
>>
>> --
>> Cosimo Lupo
>>
>
>
> --
> Cosimo Lupo
>


-- 
Cosimo Lupo
-- 

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:
https://cmake.org/mailman/listinfo/cmake

Re: [CMake] how to port to cmake a project using gnulib

[Alfred Sawaya]

  Sorry, I did not got this hint.Well, you might still use gnulib as an external dependency (https://www.gnu.org/software/gnulib/manual/html_node/POSIX-Substitutes-Library.html#POSIX-Substitutes-Library). Maybe be it worth considering a better separation if the build tool is different.I need to read more about gnulib to give you a better answer. Maybe someone already has a clue on the list. Regards,Cordialement,Alfred Sawaya   De: cos...@anthrotype.comEnvoyé: 9 janvier 2018 1:17 PMÀ: alf...@huji.frCc: cmake@cmake.orgObjet: Re: [CMake] how to port to cmake a project using gnulib  Thanks.However, that's not exactly what I was looking for. The gnulib, by design, is not an external library that you link with, but a collection of modules that are meant to be copied into one's project.I would like to build ttfautohint with cmake (and ninja), not just adding ttfautohint as an external project built with autotools and GNU make.On Tue, Jan 9, 2018 at 12:10 PM Alfred Sawaya  wrote:  Hello,I have some CMake projects that depend on autotools bases libs.I compile them as External project.https://cmake.org/cmake/help/latest/module/ExternalProject.htmlRegardsCordialement,Alfred Sawaya   De: cos...@anthrotype.comEnvoyé: 9 janvier 2018 1:01 PMÀ: cmake@cmake.orgObjet: [CMake] how to port to cmake a project using gnulib  Hello,I'm new to Cmake.I would like to port to cmake a project that is currently built with the Autotools and depends on gnulib, the GNU Portability Library: https://www.gnu.org/software/gnulib/(The project in question is https://www.freetype.org/ttfautohint/)It appears that gnulib itself is very much tied with autoconf/automake/libtool.In fact I couldn't find any examples of other CMake based projects that use gnulib.Does anyone has any tips or examples on how I could proceed?Thank you,Cosimo Lupo-- Cosimo Lupo
-- Cosimo Lupo
-- 

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:
https://cmake.org/mailman/listinfo/cmake

Re: [CMake] how to port to cmake a project using gnulib

[Cosimo Lupo]

Thanks.
However, that's not exactly what I was looking for. The gnulib, by design,
is not an external library that you link with, but a collection of modules
that are meant to be copied into one's project.
I would like to build ttfautohint with cmake (and ninja), not just adding
ttfautohint as an external project built with autotools and GNU make.


On Tue, Jan 9, 2018 at 12:10 PM Alfred Sawaya  wrote:

> Hello,
>
> I have some CMake projects that depend on autotools bases libs.
> I compile them as External project.
>
> https://cmake.org/cmake/help/latest/module/ExternalProject.html
>
> Regards
>
> Cordialement,
>
> Alfred Sawaya
> *De:* cos...@anthrotype.com
> *Envoyé:* 9 janvier 2018 1:01 PM
> *À:* cmake@cmake.org
> *Objet:* [CMake] how to port to cmake a project using gnulib
>
> Hello,
>
> I'm new to Cmake.
>
> I would like to port to cmake a project that is currently built with the
> Autotools and depends on gnulib, the GNU Portability Library:
> https://www.gnu.org/software/gnulib/
>
> (The project in question is https://www.freetype.org/ttfautohint/)
>
> It appears that gnulib itself is very much tied with
> autoconf/automake/libtool.
>
> In fact I couldn't find any examples of other CMake based projects that
> use gnulib.
>
> Does anyone has any tips or examples on how I could proceed?
>
> Thank you,
>
> Cosimo Lupo
>
>
> --
> Cosimo Lupo
>


-- 
Cosimo Lupo
-- 

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:
https://cmake.org/mailman/listinfo/cmake

Re: [CMake] how to port to cmake a project using gnulib

[Alfred Sawaya]

  Hello,I have some CMake projects that depend on autotools bases libs.I compile them as External project.https://cmake.org/cmake/help/latest/module/ExternalProject.htmlRegardsCordialement,Alfred Sawaya   De: cos...@anthrotype.comEnvoyé: 9 janvier 2018 1:01 PMÀ: cmake@cmake.orgObjet: [CMake] how to port to cmake a project using gnulib  Hello,I'm new to Cmake.I would like to port to cmake a project that is currently built with the Autotools and depends on gnulib, the GNU Portability Library: https://www.gnu.org/software/gnulib/(The project in question is https://www.freetype.org/ttfautohint/)It appears that gnulib itself is very much tied with autoconf/automake/libtool.In fact I couldn't find any examples of other CMake based projects that use gnulib.Does anyone has any tips or examples on how I could proceed?Thank you,Cosimo Lupo-- Cosimo Lupo
-- 

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:
https://cmake.org/mailman/listinfo/cmake

[CMake] how to port to cmake a project using gnulib

[Cosimo Lupo]

Hello,

I'm new to Cmake.

I would like to port to cmake a project that is currently built with the
Autotools and depends on gnulib, the GNU Portability Library:
https://www.gnu.org/software/gnulib/

(The project in question is https://www.freetype.org/ttfautohint/)

It appears that gnulib itself is very much tied with
autoconf/automake/libtool.

In fact I couldn't find any examples of other CMake based projects that use
gnulib.

Does anyone has any tips or examples on how I could proceed?

Thank you,

Cosimo Lupo


-- 
Cosimo Lupo
-- 

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:
https://cmake.org/mailman/listinfo/cmake

Re: [CMake] configure_file: escaping (single) quotes

[Franck Houssen]

OK. Got it to work ! Thanks 

- Mail original -

> De: "Marc CHEVRIER" 
> À: "Franck Houssen" 
> Cc: "CMake Mail List" 
> Envoyé: Mardi 9 Janvier 2018 11:26:55
> Objet: Re: [CMake] configure_file: escaping (single) quotes

> Yes, you have to rewrite your line as:

> CMD="mpirun -n @ MPIEXEC_PREFLAGS @ @ MPIEXEC_NUMPROC_FLAG @ @
> MPIEXEC_MAX_NUMPROCS @ @ MPIEXEC_POSTFLAGS @ "

> From: Franck Houssen 
> Date: Tuesday 9 January 2018 at 11:23
> To: "CHEVRIER, Marc" 
> Cc: CMake Mail List 
> Subject: Re: [CMake] configure_file: escaping (single) quotes

> - Mail original -

> > De: "Marc CHEVRIER" 
> 
> > À: "Franck Houssen" , "CMake Mail List"
> > 
> 
> > Envoyé: Mardi 9 Janvier 2018 10:29:30
> 
> > Objet: Re: [CMake] configure_file: escaping (single) quotes
> 

> > The problem comes from CMake evaluating variable VAR (i.e. expression
> > ${VAR…}) and detect wrong syntax.
> 

> > The solution is to specify option @ONLY to command configure_file to avoid
> > ${} evaluation.
> 

> The line after VAR is something like:

> VAR="${VAR// ' # ' /}"

> CMD="mpirun -n ${MPIEXEC_PREFLAGS} ${MPIEXEC_NUMPROC_FLAG}
> ${MPIEXEC_MAX_NUMPROCS} ${MPIEXEC_POSTFLAGS}"

> I need MPIEXEC_* to be replaced. So, I need to use @ONLY and set all MPIEXEC
> variables with @ (but not $). Correct ?

> > From: CMake  on behalf of Franck Houssen
> > 
> 
> > Date: Tuesday 9 January 2018 at 10:24
> 
> > To: CMake Mail List 
> 
> > Subject: [CMake] configure_file: escaping (single) quotes
> 

> > VAR="${VAR// ' # ' /}"
> 
-- 

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:
https://cmake.org/mailman/listinfo/cmake

Re: [cmake-developers] Optionally disabling static lib dependencies with COMPILE_DEPENDS

[Craig Scott]

Perhaps keep an eye on the work going on in merge request 1524
, which may
allow you to use object libraries in target_link_libraries(). Not sure if
it would cut the dependencies in the way you are seeking, but maybe take a
look and see.

On Fri, Jan 5, 2018 at 8:08 PM, John Wordsworth 
wrote:

> First of all - thanks for the suggestions. I intend to look into ccache
> for our Linux builds in the future and there are some useful tips here for
> me to look into. I wasn't aware of clcache and it looks very interesting,
> especially combined with network sharing.
>
> I realise I wasn't very clear in my previous explanation. Hopefully this
> paints a better picture;
>
> - We have 40 or so developers spread across Visual Studio 2015 (MSBuild -
> Windows), Xcode (macOS) and Make/Clang (Linux). 80% use Windows.
> - We have a core set of libs in use by a number of projects (~30 static
> libs and ~10 different projects), but the projects mix and match which libs
> they use - merging the static libs (beyond a few of them) isn't something
> we want to do.
> - I have recently been revising our CMake structure and have boiled it
> down to a fairly simple "add_library(x), target_link_libraries(x,
> default_compile_settings, dependencies)" which means compile settings,
> include directories and macros propagate through the libs nicely.
> - We sometimes want to build and use certain libs as shared libs instead
> of static libs.
>
> With regards to the COMPILE_DEPENDS feature that I have mocked up and
> started testing with our team;
>
> - If and only if COMPILE_DEPENDS is set for a STATIC library, then when
> building the target dependencies for that library, it uses the list of
> provided targets instead of those that would have been inferred from
> previous calls to "target_link_libraries" or "add_dependencies".
>
> The reality is, the libs which are being built statically can nearly all
> build in parallel with only one or two "real" dependencies. I understand
> that our case is rather specific, but having implemented "COMPILE_DEPENDS"
> and written ~10 lines of CMake in our project (hard coding the one or two
> actual build order dependencies and disabling the rest), our compile graph
> looks much nicer and saves a significant amount of time building on a
> single machine (see https://www.johnwordsworth.com/temp/cmake_compile_
> depends.jpg). We see similar savings on macOS using Xcode but have not
> tested on Linux yet. When we allow Incredibuild to distribute building of
> compilation units across 15-20 agents, the proportional build time drops
> more dramatically between the two (the same project goes from ~2.6mins ->
> ~1.6mins).
>
> I understand that just "hard overriding" the target dependencies is a bit
> messy, but I'd also be happy to explore other ways I could add a similar
> feature to CMake if there is a potentially better way to do this. What I am
> ideally looking for in a solution is that I can continue to propagate
> include directories / compile settings / preprocessor macros through the
> chain of libs and that it improves building static libs in parallel across
> all our build systems (MSVC / XCode / make). Ideally, I wouldn't have to
> restructure my CMake project too much either - as the draft I have for our
> new structure feels super clean now and refactoring it just to remove build
> order dependencies would be shame. If there are any alternative ideas for
> how to implement this, I'd love to discuss. I'm no CMake expert, but maybe
> if we could use "target_link_libraries" with OBJECT libraries to grab
> compile settings, or perhaps I could look into a mechanism for not adding
> build order dependencies on VS2015/Xcode if there is no need too?
>
> Thanks again for the feedback and discussion so far.
>
> // John W
>
> On Thu, Jan 4, 2018 at 12:16 PM, Eric Noulard 
> wrote:
>
>>
>> 2018-01-04 10:48 GMT+01:00 Craig Scott :
>>
>>>
>>>
>>> On Thu, Jan 4, 2018 at 8:27 AM, John Wordsworth >> > wrote:
>>>
 I have recently been reviewing ways to improve build times for our
 project, which is comprised of a number of static libraries. I stumbled
 across this post on the CMake tracker from 2012/13 (
 https://cmake.org/Bug/view.php?id=13799). It suggests adding a
 COMPILE_DEPENDS target property to to explicitly set dependencies for
 STATIC libraries instead of always using all linked libraries as
 build-order dependencies.

 Having done a draft implementation in a local CMake repository it has
 shaved off  20% of our 120s build time. I expect the savings to be much
 more dramatic when I test with Incredibuild (approximately 50% based on
 tests done previously from just deleting dependencies manually in Visual
 Studio).

>>>
>> You said you tested with Incredibuild but with what kind of 

Re: [CMake] configure_file: escaping (single) quotes

[CHEVRIER, Marc]

Yes, you have to rewrite your line as:
CMD="mpirun -n @MPIEXEC_PREFLAGS@ @MPIEXEC_NUMPROC_FLAG@ @MPIEXEC_MAX_NUMPROCS@ 
@MPIEXEC_POSTFLAGS@"


From: Franck Houssen 
Date: Tuesday 9 January 2018 at 11:23
To: "CHEVRIER, Marc" 
Cc: CMake Mail List 
Subject: Re: [CMake] configure_file: escaping (single) quotes


De: "Marc CHEVRIER" 
À: "Franck Houssen" , "CMake Mail List" 

Envoyé: Mardi 9 Janvier 2018 10:29:30
Objet: Re: [CMake] configure_file: escaping (single) quotes

The problem comes from CMake evaluating variable VAR (i.e. expression ${VAR…}) 
and detect wrong syntax.
The solution is to specify option @ONLY to command configure_file to avoid ${} 
evaluation.

The line after VAR is something like:

VAR="${VAR//'#'/}"

CMD="mpirun -n ${MPIEXEC_PREFLAGS} ${MPIEXEC_NUMPROC_FLAG} 
${MPIEXEC_MAX_NUMPROCS} ${MPIEXEC_POSTFLAGS}"



I need MPIEXEC_* to be replaced. So, I need to use @ONLY and set all MPIEXEC 
variables with @ (but not $). Correct ?




From: CMake  on behalf of Franck Houssen 

Date: Tuesday 9 January 2018 at 10:24
To: CMake Mail List 
Subject: [CMake] configure_file: escaping (single) quotes
VAR="${VAR//'#'/}"

-- 

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:
https://cmake.org/mailman/listinfo/cmake

Re: [CMake] configure_file: escaping (single) quotes

[Franck Houssen]

- Mail original -


De: "Marc CHEVRIER"  
À: "Franck Houssen" , "CMake Mail List" 
 
Envoyé: Mardi 9 Janvier 2018 10:29:30 
Objet: Re: [CMake] configure_file: escaping (single) quotes 



The problem comes from CMake evaluating variable VAR (i.e. expression ${VAR…}) 
and detect wrong syntax. 

The solution is to specify option @ONLY to command configure_file to avoid ${} 
evaluation. 




The line after VAR is something like: 


VAR="${VAR// ' # ' /}" 

CMD="mpirun -n ${MPIEXEC_PREFLAGS} ${MPIEXEC_NUMPROC_FLAG} 
${MPIEXEC_MAX_NUMPROCS} ${MPIEXEC_POSTFLAGS}" 




I need MPIEXEC_ * to be replaced. So, I need to use @ONLY and set all MPIEXEC 
variables with @ (but not $). Correct ? 











From: CMake  on behalf of Franck Houssen 
 
Date: Tuesday 9 January 2018 at 10:24 
To: CMake Mail List  
Subject: [CMake] configure_file: escaping (single) quotes 


VAR="${VAR// ' # ' /}" 




-- 

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:
https://cmake.org/mailman/listinfo/cmake

[Cmake-commits] CMake branch, master, updated. v3.10.1-721-g89d1274

[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  89d12746306571a323549ad0f8d11284999053d5 (commit)
   via  11615b297fcb34fe1e51f74a66e72cc70efdf703 (commit)
  from  b9bada655ec1a68d65a2536f300c9d6f9cd7aabc (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=89d12746306571a323549ad0f8d11284999053d5
commit 89d12746306571a323549ad0f8d11284999053d5
Merge: b9bada6 11615b2
Author: Craig Scott 
AuthorDate: Tue Jan 9 10:05:32 2018 +
Commit: Kitware Robot 
CommitDate: Tue Jan 9 05:05:41 2018 -0500

Merge topic 'improve_generated_property_docs'

11615b29 GENERATED: Improve the documentation of the GENERATED file property

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


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=11615b297fcb34fe1e51f74a66e72cc70efdf703
commit 11615b297fcb34fe1e51f74a66e72cc70efdf703
Author: Robert Maynard 
AuthorDate: Wed Jan 3 09:38:20 2018 -0500
Commit: Robert Maynard 
CommitDate: Mon Jan 8 09:12:33 2018 -0500

GENERATED: Improve the documentation of the GENERATED file property

diff --git a/Help/prop_sf/GENERATED.rst b/Help/prop_sf/GENERATED.rst
index a3aa127..d430ee2 100644
--- a/Help/prop_sf/GENERATED.rst
+++ b/Help/prop_sf/GENERATED.rst
@@ -1,8 +1,23 @@
 GENERATED
 -
 
-Is this source file generated as part of the build process.
+Is this source file generated as part of the build or CMake process.
 
-If a source file is generated by the build process CMake will handle
-it differently in terms of dependency checking etc.  Otherwise having
-a non-existent source file could create problems.
+Tells the internal CMake engine that a source file is generated by an outside
+process such as another build step, or the execution of CMake itself. This
+information is then used to exempt the file from any existence or validity
+checks. Generated files are created by the execution of commands such as
+:command:`add_custom_command` and :command:`file(GENERATE)`.
+
+When a generated file created by an :command:`add_custom_command` command
+is explicitly listed as a source file for any target in the same
+directory scope (which usually means the same ``CMakeLists.txt`` file),
+CMake will automatically create a dependency to make sure the file is
+generated before building that target.
+
+Generated sources may be hidden in some IDE tools, while in others they might
+be shown. For the special case of sources generated by CMake's 
:prop_tgt:`AUTOMOC`
+or :prop_tgt:`AUTORCC` functionality, the :prop_gbl:`AUTOGEN_SOURCE_GROUP`,
+:prop_gbl:`AUTOMOC_SOURCE_GROUP` and :prop_gbl:`AUTORCC_SOURCE_GROUP` target
+properties may influence where the generated sources are grouped in the 
project's
+file lists.

---

Summary of changes:
 Help/prop_sf/GENERATED.rst |   23 +++
 1 file changed, 19 insertions(+), 4 deletions(-)


hooks/post-receive
-- 
CMake
___
Cmake-commits mailing list
Cmake-commits@cmake.org
https://cmake.org/mailman/listinfo/cmake-commits

Re: [CMake] configure_file: escaping (single) quotes

[J Decker]

On Tue, Jan 9, 2018 at 1:29 AM, J Decker  wrote:

>
>
> On Tue, Jan 9, 2018 at 1:24 AM, Franck Houssen 
> wrote:
>
>> Hello,
>>
>> I need configure_file to produce a bash file containing this line:
>> VAR="${VAR//*'*#*'*/}"
>>
>>
> maybe
>
> VAR="$" "{VAR//*'*#*'*/}"
>
Oh nevermind I was doing that sort of thing using FILE( APPEND ... )


>
>
>
>> I tried without success VAR="${VAR//*'*#*'*/}" and VAR="${VAR//*\'*#*\'*/}"
>> with and without ESCAPE_QUOTES in configure_file : always get an error
>> like "Syntax error in cmake code when parsing string".
>> Not a bash guru, and, can't get if the problem comes from bash or
>> cmake... Can somebody help on this ?
>>
>> Franck
>>
>> --
>>
>> 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:
>> https://cmake.org/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:
https://cmake.org/mailman/listinfo/cmake

Re: [CMake] configure_file: escaping (single) quotes

[CHEVRIER, Marc]

The problem comes from CMake evaluating variable VAR (i.e. expression ${VAR…}) 
and detect wrong syntax.
The solution is to specify option @ONLY to command configure_file to avoid ${} 
evaluation.


From: CMake  on behalf of Franck Houssen 

Date: Tuesday 9 January 2018 at 10:24
To: CMake Mail List 
Subject: [CMake] configure_file: escaping (single) quotes

VAR="${VAR//'#'/}"
-- 

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:
https://cmake.org/mailman/listinfo/cmake

Re: [CMake] configure_file: escaping (single) quotes

[J Decker]

On Tue, Jan 9, 2018 at 1:24 AM, Franck Houssen 
wrote:

> Hello,
>
> I need configure_file to produce a bash file containing this line:
> VAR="${VAR//*'*#*'*/}"
>
>
maybe

VAR="$" "{VAR//*'*#*'*/}"


> I tried without success VAR="${VAR//*'*#*'*/}" and VAR="${VAR//*\'*#*\'*/}"
> with and without ESCAPE_QUOTES in configure_file : always get an error
> like "Syntax error in cmake code when parsing string".
> Not a bash guru, and, can't get if the problem comes from bash or cmake...
> Can somebody help on this ?
>
> Franck
>
> --
>
> 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:
> https://cmake.org/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:
https://cmake.org/mailman/listinfo/cmake

[CMake] configure_file: escaping (single) quotes

[Franck Houssen]

Hello, 

I need configure_file to produce a bash file containing this line: 
VAR="${VAR// ' # ' /}" 

I tried without success VAR="${VAR// ' # ' /}" and VAR="${VAR// \' # \' /}" 
with and without ESCAPE_QUOTES in configure_file : always get an error like 
"Syntax error in cmake code when parsing string". 
Not a bash guru, and, can't get if the problem comes from bash or cmake... Can 
somebody help on this ? 

Franck 
-- 

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:
https://cmake.org/mailman/listinfo/cmake