[Cmake-commits] CMake branch, master, updated. v3.9.0-rc5-244-g0ba4a4c

[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  0ba4a4c36fd8da36b3f4691ea74dab6fc6372704 (commit)
  from  2ef3527dfe03ac6e5f5c49d13d99b2304381b0a8 (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=0ba4a4c36fd8da36b3f4691ea74dab6fc6372704
commit 0ba4a4c36fd8da36b3f4691ea74dab6fc6372704
Author: Kitware Robot <kwro...@kitware.com>
AuthorDate: Sat Jul 8 00:01:05 2017 -0400
Commit: Kitware Robot <kwro...@kitware.com>
CommitDate: Sat Jul 8 00:01:05 2017 -0400

CMake Nightly Date Stamp

diff --git a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake
index 7495ba5..a0f8e56 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 9)
-set(CMake_VERSION_PATCH 20170707)
+set(CMake_VERSION_PATCH 20170708)
 #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] FindDoxygen is doing find_package() when it is included

[Robert Dailey]

Apologies for the confusion and spam: I figured out that when you do a
find_package(), it also implicitly includes the contents of that
module into your list file so you can access its functions. I was
under the impression I had to include FindDoxygen.cmake explicitly to
access the functions it provides.

I'm guessing this is supported behavior. If so, I'll rely on it.

On Fri, Jul 7, 2017 at 1:20 PM, Robert Dailey  wrote:
> I actually confused myself a bit... I think the issue is not that
> finding happens when including it, but that doxygen_add_docs() is
> bundled with the find module. What is the intended usage of this? If I
> do find_package() will that also make doxygen_add_docs() available? Or
> do I have to explicitly include FindDoxygen to get access to the
> function?
>
> On Fri, Jul 7, 2017 at 1:13 PM, Robert Dailey  
> wrote:
>> When I do this:
>>
>>
>> message( "blah1" )
>> include( FindDoxygen )
>>
>> message( "blah2" )
>> find_package( Doxygen 1.8.6 OPTIONAL_COMPONENTS dot )
>> message( "blah3" )
>>
>>
>> I get this output:
>>
>>
>> blah1
>> -- Found Doxygen: C:/Program Files/doxygen/bin/doxygen.exe (found
>> version "1.8.13") found components:  doxygen missing components:  dot
>> blah2
>> -- Found Doxygen: C:/Program Files/doxygen/bin/doxygen.exe (found
>> suitable version "1.8.13", minimum required is "1.8.6") found
>> components:  doxygen missing components:  dot
>> blah3
>>
>>
>> Two questions:
>>
>> 1. Why is find_package() happening automatically when I include the
>> find module? This is contrary to the behavior of other find modules. I
>> do not want it to find doxygen for me, as I have some minimum version
>> requirements and I do not want it to find dot. How can I disable this
>> implied search behavior?
>>
>> 2. Each time I run my scripts, it keeps searching for doxygen. Even
>> though I've specified dot as an optional component. I do not want it
>> to keep searching for doxygen each time I generate. It should find it
>> once and be done. How can I fix this behavior?
-- 

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] FindDoxygen is doing find_package() when it is included

[Robert Dailey]

Apologies for the confusion and spam: I figured out that when you do a
find_package(), it also implicitly includes the contents of that
module into your list file so you can access its functions. I was
under the impression I had to include FindDoxygen.cmake explicitly to
access the functions it provides.

I'm guessing this is supported behavior. If so, I'll rely on it.

On Fri, Jul 7, 2017 at 1:20 PM, Robert Dailey  wrote:
> I actually confused myself a bit... I think the issue is not that
> finding happens when including it, but that doxygen_add_docs() is
> bundled with the find module. What is the intended usage of this? If I
> do find_package() will that also make doxygen_add_docs() available? Or
> do I have to explicitly include FindDoxygen to get access to the
> function?
>
> On Fri, Jul 7, 2017 at 1:13 PM, Robert Dailey  
> wrote:
>> When I do this:
>>
>>
>> message( "blah1" )
>> include( FindDoxygen )
>>
>> message( "blah2" )
>> find_package( Doxygen 1.8.6 OPTIONAL_COMPONENTS dot )
>> message( "blah3" )
>>
>>
>> I get this output:
>>
>>
>> blah1
>> -- Found Doxygen: C:/Program Files/doxygen/bin/doxygen.exe (found
>> version "1.8.13") found components:  doxygen missing components:  dot
>> blah2
>> -- Found Doxygen: C:/Program Files/doxygen/bin/doxygen.exe (found
>> suitable version "1.8.13", minimum required is "1.8.6") found
>> components:  doxygen missing components:  dot
>> blah3
>>
>>
>> Two questions:
>>
>> 1. Why is find_package() happening automatically when I include the
>> find module? This is contrary to the behavior of other find modules. I
>> do not want it to find doxygen for me, as I have some minimum version
>> requirements and I do not want it to find dot. How can I disable this
>> implied search behavior?
>>
>> 2. Each time I run my scripts, it keeps searching for doxygen. Even
>> though I've specified dot as an optional component. I do not want it
>> to keep searching for doxygen each time I generate. It should find it
>> once and be done. How can I fix this behavior?
-- 

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] FindDoxygen is doing find_package() when it is included

[Robert Dailey]

I actually confused myself a bit... I think the issue is not that
finding happens when including it, but that doxygen_add_docs() is
bundled with the find module. What is the intended usage of this? If I
do find_package() will that also make doxygen_add_docs() available? Or
do I have to explicitly include FindDoxygen to get access to the
function?

On Fri, Jul 7, 2017 at 1:13 PM, Robert Dailey  wrote:
> When I do this:
>
>
> message( "blah1" )
> include( FindDoxygen )
>
> message( "blah2" )
> find_package( Doxygen 1.8.6 OPTIONAL_COMPONENTS dot )
> message( "blah3" )
>
>
> I get this output:
>
>
> blah1
> -- Found Doxygen: C:/Program Files/doxygen/bin/doxygen.exe (found
> version "1.8.13") found components:  doxygen missing components:  dot
> blah2
> -- Found Doxygen: C:/Program Files/doxygen/bin/doxygen.exe (found
> suitable version "1.8.13", minimum required is "1.8.6") found
> components:  doxygen missing components:  dot
> blah3
>
>
> Two questions:
>
> 1. Why is find_package() happening automatically when I include the
> find module? This is contrary to the behavior of other find modules. I
> do not want it to find doxygen for me, as I have some minimum version
> requirements and I do not want it to find dot. How can I disable this
> implied search behavior?
>
> 2. Each time I run my scripts, it keeps searching for doxygen. Even
> though I've specified dot as an optional component. I do not want it
> to keep searching for doxygen each time I generate. It should find it
> once and be done. How can I fix this behavior?
-- 

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] FindDoxygen is doing find_package() when it is included

[Robert Dailey]

I actually confused myself a bit... I think the issue is not that
finding happens when including it, but that doxygen_add_docs() is
bundled with the find module. What is the intended usage of this? If I
do find_package() will that also make doxygen_add_docs() available? Or
do I have to explicitly include FindDoxygen to get access to the
function?

On Fri, Jul 7, 2017 at 1:13 PM, Robert Dailey  wrote:
> When I do this:
>
>
> message( "blah1" )
> include( FindDoxygen )
>
> message( "blah2" )
> find_package( Doxygen 1.8.6 OPTIONAL_COMPONENTS dot )
> message( "blah3" )
>
>
> I get this output:
>
>
> blah1
> -- Found Doxygen: C:/Program Files/doxygen/bin/doxygen.exe (found
> version "1.8.13") found components:  doxygen missing components:  dot
> blah2
> -- Found Doxygen: C:/Program Files/doxygen/bin/doxygen.exe (found
> suitable version "1.8.13", minimum required is "1.8.6") found
> components:  doxygen missing components:  dot
> blah3
>
>
> Two questions:
>
> 1. Why is find_package() happening automatically when I include the
> find module? This is contrary to the behavior of other find modules. I
> do not want it to find doxygen for me, as I have some minimum version
> requirements and I do not want it to find dot. How can I disable this
> implied search behavior?
>
> 2. Each time I run my scripts, it keeps searching for doxygen. Even
> though I've specified dot as an optional component. I do not want it
> to keep searching for doxygen each time I generate. It should find it
> once and be done. How can I fix this behavior?
-- 

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] FindDoxygen is doing find_package() when it is included

[Robert Dailey]

When I do this:


message( "blah1" )
include( FindDoxygen )

message( "blah2" )
find_package( Doxygen 1.8.6 OPTIONAL_COMPONENTS dot )
message( "blah3" )


I get this output:


blah1
-- Found Doxygen: C:/Program Files/doxygen/bin/doxygen.exe (found
version "1.8.13") found components:  doxygen missing components:  dot
blah2
-- Found Doxygen: C:/Program Files/doxygen/bin/doxygen.exe (found
suitable version "1.8.13", minimum required is "1.8.6") found
components:  doxygen missing components:  dot
blah3


Two questions:

1. Why is find_package() happening automatically when I include the
find module? This is contrary to the behavior of other find modules. I
do not want it to find doxygen for me, as I have some minimum version
requirements and I do not want it to find dot. How can I disable this
implied search behavior?

2. Each time I run my scripts, it keeps searching for doxygen. Even
though I've specified dot as an optional component. I do not want it
to keep searching for doxygen each time I generate. It should find it
once and be done. How can I fix this behavior?
-- 

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] Help on first cmake project

[Gonzalo Garramuño]

El 07/07/17 a las 03:45, Florian Lindner escribió:

* Any other advises you want to give me?
I would advise you try to build out of source tree to keep the source 
clean.  Example:


$ mkdir build-linux64
$ cd build-linux64
$ cmake .. -G'Unix Makefiles'
$ make
$ make install

when done, you can then do:

$ cd ..
$ rm -rf build-linux64


Thanks for helping a beginner!

Florian

No problem.

--
Gonzalo Garramuño

--

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, master, updated. v3.9.0-rc5-243-g2ef3527

[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  2ef3527dfe03ac6e5f5c49d13d99b2304381b0a8 (commit)
   via  364496e4d284c64c81c622f7ffb3674b9a83507f (commit)
   via  1ff7cd1fe7cdd408d55827bdc10058167a09cf45 (commit)
   via  d2617a28eb9f489d87be88851a313c58d5eaf027 (commit)
   via  a951eb2cb4b354e521bc6b93c7980e7f22ab1174 (commit)
   via  658ecc1a7cab54aeb738a00e7fee24aa4bd18adb (commit)
   via  796b8fcb14072bef72fe324015c0a62e2006b0db (commit)
   via  6c80e958cad73105c44e6b725a8ed7394e04290d (commit)
   via  d1713d8bc580cdfad39b088285afcb92dea417de (commit)
   via  d8e6cd9ed8bfee9073cff26cb654bc01e653b0b9 (commit)
   via  0b1a2876c817a00daf7027570b1976a9e15ff654 (commit)
   via  fea7d69ddeedd72f6a1f8cec5a011696dec832db (commit)
   via  d2a8b5cea6baa0508f9935ac2327fcf63f52c21a (commit)
   via  a2112257df2f255d8aa3584af468b7d30ff90e8c (commit)
   via  8cd28bb0e54f962ab2b189f1b7196c2b014129a7 (commit)
   via  0fc2d78ee97cb0ba73040be353bdedd4fc03c2b9 (commit)
  from  17115f0a5b594e76d6e3fa2df1361224e57ddf0f (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=2ef3527dfe03ac6e5f5c49d13d99b2304381b0a8
commit 2ef3527dfe03ac6e5f5c49d13d99b2304381b0a8
Merge: 364496e 658ecc1
Author: Brad King 
AuthorDate: Fri Jul 7 08:43:39 2017 -0400
Commit: Brad King 
CommitDate: Fri Jul 7 08:43:39 2017 -0400

Merge branch 'release-3.9'


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=364496e4d284c64c81c622f7ffb3674b9a83507f
commit 364496e4d284c64c81c622f7ffb3674b9a83507f
Merge: 1ff7cd1 6c80e95
Author: Brad King 
AuthorDate: Fri Jul 7 12:42:33 2017 +
Commit: Kitware Robot 
CommitDate: Fri Jul 7 08:42:41 2017 -0400

Merge topic 'add-missing-fallthrough'

6c80e958 cmCTest: Add missing switch case fallthrough markup

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


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=1ff7cd1fe7cdd408d55827bdc10058167a09cf45
commit 1ff7cd1fe7cdd408d55827bdc10058167a09cf45
Merge: d2617a2 d8e6cd9
Author: Brad King 
AuthorDate: Fri Jul 7 12:42:16 2017 +
Commit: Kitware Robot 
CommitDate: Fri Jul 7 08:42:22 2017 -0400

Merge topic 'iar_improved'

d8e6cd9e IAR: Improve support for IAR ARM Compiler
0b1a2876 Add a CMAKE__COMPILER_ARCHITECTURE_ID variable
fea7d69d Store CMAKE_ASM_COMPILER_VERSION persistently
d2a8b5ce CMakeDetermineASMCompiler: Fix small copy-paste mistake
a2112257 Add infrastructure to use language extensions without any standard
8cd28bb0 cmLocalGenerator: Switch order of _{EXTENSIONS,STANDARD} 
check
0fc2d78e cmLocalGenerator: Simplify logic for language standard or 
extension flag

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


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=d2617a28eb9f489d87be88851a313c58d5eaf027
commit d2617a28eb9f489d87be88851a313c58d5eaf027
Merge: a951eb2 d1713d8
Author: Brad King 
AuthorDate: Fri Jul 7 12:41:17 2017 +
Commit: Kitware Robot 
CommitDate: Fri Jul 7 08:41:30 2017 -0400

Merge topic 'connect_disablePCH_with_cl_option'

d1713d8b VS: connect /Y- compiler option with "Not Using Precompiled 
Headers"

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


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=a951eb2cb4b354e521bc6b93c7980e7f22ab1174
commit a951eb2cb4b354e521bc6b93c7980e7f22ab1174
Merge: 17115f0 796b8fc
Author: Brad King 
AuthorDate: Fri Jul 7 12:40:54 2017 +
Commit: Kitware Robot 
CommitDate: Fri Jul 7 08:41:04 2017 -0400

Merge topic 'FindDoxygen-create-output-dir'

796b8fcb FindDoxygen: Create DOXYGEN_OUTPUT_DIRECTORY if it doesn't exist

Acked-by: Kitware Robot 
Reviewed-by: Craig Scott 
Merge-request: !1019


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=6c80e958cad73105c44e6b725a8ed7394e04290d
commit 6c80e958cad73105c44e6b725a8ed7394e04290d
Author: Brad King 
AuthorDate: Wed Jul 5 11:36:56 2017 -0400
Commit: Brad King 
CommitDate: Wed Jul 5 11:48:47 2017 -0400

cmCTest: Add missing switch case fallthrough markup

Without this, GCC 7 warns.

Reported-by: Rolf Eike Beer 

diff --git 

[Cmake-commits] CMake branch, release, updated. v3.9.0-rc5-19-g658ecc1

[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  658ecc1a7cab54aeb738a00e7fee24aa4bd18adb (commit)
   via  796b8fcb14072bef72fe324015c0a62e2006b0db (commit)
  from  cf9a994d9a53db02d8ddaa2bf3f9da0bc8f6f19b (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/FindDoxygen.cmake |   14 +++---
 1 file changed, 11 insertions(+), 3 deletions(-)


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

Re: [CMake] Parallel moc for Qt files

[Konstantin Tokarev]

06.07.2017, 23:00, "Michael Jackson" :
> I have a large list of files that need to have Qt's 'moc' run on them
> (107 headers). I use all the normal CMake facilities for Qt based
> projects. I noticed that the generation of the moc files are done
> serially. Is there a flag or anything that I can use to run the
> generation in Parallel? I ask because each file takes about 3 seconds to
> run through moc. The code is heavily C++ templated which I think causes
> 'moc' to run more slowly. We have other places in the code where 'moc'
> must run and it does each file in the "blink of an eye".

Replace use of AUTOMOC with macros like qt5_generate_moc. Each moc file
will be generated by a separate custom command.

For example, I wrote 3 macros that wrap qt5_generate_moc for more
convenience [1], example usage is at [2].

[1] 
https://github.com/annulen/webkit/blob/qtwebkit-stable/Source/cmake/OptionsQt.cmake#L63
[2] 
https://github.com/annulen/webkit/blob/qtwebkit-stable/Source/WebCore/PlatformQt.cmake#L165

>
> Just curious.
>
> --
> Michael A. Jackson
> BlueQuartz Software, LLC
> [e]: mike.jack...@bluequartz.net
> --
>
> 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

-- 
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:
http://public.kitware.com/mailman/listinfo/cmake

Re: [CMake] Parallel moc for Qt files

[Michael Jackson]

Thank you for the suggestions.

It is almost like a Jom for moc needs to be written.

-Mike Jackson

From: Benjamin Ballet 
Sent: Friday, July 7, 2017 5:47:20 AM
To: Michael Jackson
Cc: cmake
Subject: Re: [CMake] Parallel moc for Qt files

I don't know how to parallelize moc with CMake though I previously reduce moc 
time (sometimes it's very slow) :

- by replacing as much #include as possible by forward-declaration

- wrapping some #include around #ifndef Q_MOC_RUN ... #endif

2017-07-06 22:00 GMT+02:00 Michael Jackson 
>:
I have a large list of files that need to have Qt's 'moc' run on them (107 
headers). I use all the normal CMake facilities for Qt based projects. I 
noticed that the generation of the moc files are done serially. Is there a flag 
or anything that I can use to run the generation in Parallel? I ask because 
each file takes about 3 seconds to run through moc. The code is heavily C++ 
templated which I think causes 'moc' to run more slowly. We have other places 
in the code where 'moc' must run and it does each file in the "blink of an eye".

Just curious.

--
Michael A. Jackson
BlueQuartz Software, LLC
[e]: mike.jack...@bluequartz.net
--

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



--
Benjamin Ballet
Ingénieur R

[http://www.activscreen.com/mkg/signature/email_2017/ivs_logo.png]

19 rue Klock - 92110 Clichy - FRANCE
Standard : +33 1 44 69 37 37

www.activisu.com

[http://www.activscreen.com/mkg/signature/Signature_IVS_MAI_17.png]

[http://www.activscreen.com/mkg/signature/email_2017/linkedin.png]
-- 

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] Parallel moc for Qt files

[Michael Jackson]

Looks like an interesting project. After reading  the blog and reading the 
GitHub issue pages there seem to be serious issues with MSVC still which is a 
blocker for us. I will keep an eye on it though.

--
Michael A. Jackson

From: Cristian Adam 
Sent: Thursday, July 6, 2017 6:11:50 PM
To: Michael Jackson
Cc: cmake
Subject: Re: [CMake] Parallel moc for Qt files

On Thu, Jul 6, 2017 at 10:00 PM, Michael Jackson 
> wrote:
I have a large list of files that need to have Qt's 'moc' run on them (107 
headers). I use all the normal CMake facilities for Qt based projects. I 
noticed that the generation of the moc files are done serially. Is there a flag 
or anything that I can use to run the generation in Parallel? I ask because 
each file takes about 3 seconds to run through moc. The code is heavily C++ 
templated which I think causes 'moc' to run more slowly. We have other places 
in the code where 'moc' must run and it does each file in the "blink of an eye".

Just curious.


Have you tried removing moc altogether using 
Verdigris? I'm curious 
how this would speed up your compilation time.

Cheers,
Cristian.
-- 

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] Parallel moc for Qt files

[Benjamin Ballet via CMake]

I don't know how to parallelize moc with CMake though I previously reduce
moc time (sometimes it's very slow) :

- by replacing as much #include as possible by forward-declaration

- wrapping some #include around #ifndef Q_MOC_RUN ... #endif

2017-07-06 22:00 GMT+02:00 Michael Jackson :

> I have a large list of files that need to have Qt's 'moc' run on them (107
> headers). I use all the normal CMake facilities for Qt based projects. I
> noticed that the generation of the moc files are done serially. Is there a
> flag or anything that I can use to run the generation in Parallel? I ask
> because each file takes about 3 seconds to run through moc. The code is
> heavily C++ templated which I think causes 'moc' to run more slowly. We
> have other places in the code where 'moc' must run and it does each file in
> the "blink of an eye".
>
> Just curious.
>
> --
> Michael A. Jackson
> BlueQuartz Software, LLC
> [e]: mike.jack...@bluequartz.net
> --
>
> 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/opensou
> rce/opensource.html
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/cmake
>



-- 
Benjamin Ballet
Ingénieur R



19 rue Klock - 92110 Clichy - FRANCE
Standard : +33 1 44 69 37 37

www.activisu.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] Help on first cmake project

[J Decker]

On Thu, Jul 6, 2017 at 11:45 PM, Florian Lindner 
wrote:

> Hello,
>
> coming from scons I want to take a look into cmake...
>
> My CMakeList.txt looks like:
>
>
> cmake_minimum_required (VERSION 3.0)
> project (ASTE)
>
> add_executable(readMesh readMesh.cpp)
>
> find_library(precice precice PATHS $ENV{PRECICE_ROOT}/build/last)
> target_link_libraries(readMesh ${precice})
> set(CMAKE_LIBRARY_PATH ${CMAKE_LIBRARY_PATH} $ENV{PRECICE_ROOT}/build/last)
>
>
> find_package(Boost 1.60.0
>   COMPONENTS program_options filesystem
>   REQUIRED)
> target_link_libraries(readMesh ${Boost_LIBRARIES})
>
> find_package(MPI REQUIRED)
> target_link_libraries(readMesh ${MPI_LIBRARIES})
> set(COMPILE_FLAGS  ${COMPILE_FLAGS} ${MPI_COMPILE_FLAGS})
> set(LINK_FLAGS ${LINK_FLAGS} ${MPI_LINK_FLAGS})
>
>
> and does it job, i.e. the target builds. precice is out own, independently
> build library.
>
> However, I have several questions:
>
> * Can I make target_link_libraries add a library for all defined targets?
> At the moment, there is only one, but in the
> projekt there are multiple, very similiar targets built.
>
No; each target needs to have target_link_libaries.  You can build a list
of libs to add like set( common_deps ${Boost_LIBRARIES} ${MPI_LIBRARIES} )
; or appending to a variable like you did with COMPILE_FLAGS.


> * Can I make find_library to treat the library as required, as with
> find_package?
>

can add if( -NOTFOUND ) message( ERROR "xxx not found" )
can wrap that in a macro for simplification...

macro( my_find_library var )
  find_library( ${var} ${ARGN} )
  if( ${var}-NOTFOUND )
message( FATAL_ERROR "${ARG2} was not found" )
  endif()
endmacro()

(assumes that you're using the single name version, and not multiple names
using NAME command in find_library)

>
> * Can I reused the value of find_library's PATH setting? Especially if
> there are multiple PATHs, wouldn't it be nice to
> have a precice-LIBPATH that contains the path, where the library was
> found? So I can add this to CMAKE_LIBRARY_PATH? Or
> is there another function that does all that?
>
> Yes, these become available for all sub projects also.
INCLUDE_DIRECTORIES() and LINK_DIRECTORIES() will also get inherited by
child projects.


> * Is there a way to clean cmake cache, other than rm -rf CMakeFiles
> CMakeCache.txt. Would be nice, when playing around
> and frequently changing the CMakeLists.txt
>
> really just remove CMakeCache.txt is sufficient; though generally you
won't have to remove the cache; it redoes the generation if one of the
cmakelists.txt is updated (or included dependancies).  If you're moving
librarites to be found, then yes you will have to remove the cmakecache.


> * I am a bit suprised that finding/or not finding MPI or precice is not
> printed out when executing cmake.
>
> * Any other advises you want to give me?
>
> Thanks for helping a beginner!
>
> Florian
>
> --
>
> 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] Help on first cmake project

[Florian Lindner]

Hello,

coming from scons I want to take a look into cmake...

My CMakeList.txt looks like:


cmake_minimum_required (VERSION 3.0)
project (ASTE)

add_executable(readMesh readMesh.cpp)

find_library(precice precice PATHS $ENV{PRECICE_ROOT}/build/last)
target_link_libraries(readMesh ${precice})
set(CMAKE_LIBRARY_PATH ${CMAKE_LIBRARY_PATH} $ENV{PRECICE_ROOT}/build/last)


find_package(Boost 1.60.0
  COMPONENTS program_options filesystem
  REQUIRED)
target_link_libraries(readMesh ${Boost_LIBRARIES})

find_package(MPI REQUIRED)
target_link_libraries(readMesh ${MPI_LIBRARIES})
set(COMPILE_FLAGS  ${COMPILE_FLAGS} ${MPI_COMPILE_FLAGS})
set(LINK_FLAGS ${LINK_FLAGS} ${MPI_LINK_FLAGS})


and does it job, i.e. the target builds. precice is out own, independently 
build library.

However, I have several questions:

* Can I make target_link_libraries add a library for all defined targets? At 
the moment, there is only one, but in the
projekt there are multiple, very similiar targets built.

* Can I make find_library to treat the library as required, as with 
find_package?

* Can I reused the value of find_library's PATH setting? Especially if there 
are multiple PATHs, wouldn't it be nice to
have a precice-LIBPATH that contains the path, where the library was found? So 
I can add this to CMAKE_LIBRARY_PATH? Or
is there another function that does all that?

* Is there a way to clean cmake cache, other than rm -rf CMakeFiles 
CMakeCache.txt. Would be nice, when playing around
and frequently changing the CMakeLists.txt

* I am a bit suprised that finding/or not finding MPI or precice is not printed 
out when executing cmake.

* Any other advises you want to give me?

Thanks for helping a beginner!

Florian

-- 

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