[Cmake-commits] CMake branch, master, updated. v3.13.0-rc3-373-g206ce3c

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

The branch, master has been updated
   via  206ce3c0ba730f3a8627d6a4f261bf60fc92 (commit)
  from  94744965f810958b58d94d4b3e4f67566b392396 (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=206ce3c0ba730f3a8627d6a4f261bf60fc92
commit 206ce3c0ba730f3a8627d6a4f261bf60fc92
Author: Kitware Robot 
AuthorDate: Sun Nov 11 00:01:03 2018 -0500
Commit: Kitware Robot 
CommitDate: Sun Nov 11 00:01:03 2018 -0500

CMake Nightly Date Stamp

diff --git a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake
index d164a6d..9df722c 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 13)
-set(CMake_VERSION_PATCH 20181110)
+set(CMake_VERSION_PATCH 2018)
 #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


[CMake] Unknown CMake command: "_Boost_UPDATE_WINDOWS_LIBRARY_SEARCH_DIRS_WITH_PREBUILT_PATHS".

2018-11-10 Thread Heng Zhou
Environment:
- Windows 10
- CMake 3.12.4
- Boost 1.68.0 installed from pre-compiled binary
"boost_1_68_0-msvc-14.0-64.exe" downloaded from
https://urldefense.proofpoint.com/v2/url?u=https-3A__sourceforge.net_projects_boost_files_boost-2Dbinaries_1.68.0_=DwIBaQ=Ngd-ta5yRYsqeUsEDgxhcqsYYY1Xs5ogLxWPA_2Wlc4=P9ZPbJehUz3WrP9d5HF3ig=y_dArCwaPPPEMXAhzXGHIXtIHnvmBjSk-KKWHHowVh0=A4TV6vHIws_vrs4gnW-pc70Z_nLlRHyBUL8uBmTkXWg=.

Problem:
When calling find_package(Boost COMPONENTS ...), FindBoost.cmake reports
error:
CMake Error at C:/Program
Files/CMake/share/cmake-3.12/Modules/FindBoost.cmake:1535
(_Boost_UPDATE_WINDOWS_LIBRARY_SEARCH_DIRS_WITH_PREBUILT_PATHS):
  Unknown CMake command
  "_Boost_UPDATE_WINDOWS_LIBRARY_SEARCH_DIRS_WITH_PREBUILT_PATHS".
Call Stack (most recent call first):
-- omitted --

So does the problem occur only when CMake is working with Boost 1.68.0
pre-compiled
binary? How to fix it? Should I downgrade Boost or upgrade CMake? Please
let me know if you need other information for troubleshooting. Thanks.
-- 

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] .ui Files are listed under the _autogen target in Visual Studio instead of the target to which they belong. Is this a bug or feature?

2018-11-10 Thread Ulrich Hierl

Hello cmake community,

I have a project that uses Qt 5.9.1 and cmake 3.12.4 and Visual Studio 
2017. I have targets for which I use


set(CMAKE_AUTOMOC ON)

I do not use CMAKE_AUTOUIC or CMAKE_AUTORC

Switching the CMAKE_AUTOMOC option on causes the _autogen 
targets to be created. My problem is that in the Visual Studio solution 
explorer the .ui files are listed in the _autogen target and not in the 
target to which they belong. Can you reproduce this behavior? I this how 
it should be?


Thank you for your time!

Knitschi

--

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] dependencies of cross compiliations

2018-11-10 Thread Torsten Robitzki


> Am 09.11.2018 um 15:55 schrieb Miller Henry :
> 
> There are two options. Each with pros and cons.
> 
> The first what you are doing now, except you use external project 
> https://cmake.org/cmake/help/v3.12/module/ExternalProject.html to build the 
> host tools instead of add_custom_command. It otherwise has all the cons you 
> mention, but are they significant (this is a question that is different for 
> each project)?  Going back to the manual build for host before the target 
> isn’t bad, though it is harder to teach.

I think for the example use case, this will work best. Especially, if there are 
source files (for example constants) are shared among both platforms.

Thanks,

Torsten
-- 

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