[Cmake-commits] CMake branch, master, updated. v3.7.0-rc1-276-ge46350f

_VERSION_MINOR 7) -set(CMake_VERSION_PATCH 20161017) +set(CMake_VERSION_PATCH 20161018) #set(CMake_VERSION_RC 1) --- Summary of changes: Source/CMakeVersion.cmake |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/

[CMake] cmake doesn't find QtCore

Hi, I'm trying to install PySide. With "pip install PySide", I get the warning... CMake Warning at c:/Program Files (x86)/Cmake/share/cmake-3.7/Modules/FindQt4.cmake:618 (message): C:/Qt/4.8.5/bin/qmake.exe reported QT_INSTALL_LIBS as "C:/Qt/4.8.5/lib" but QtCore could not be found there. Qt

[Cmake-commits] CMake branch, next, updated. v3.7.0-rc1-576-g237866b

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, next has been updated via 237866b8bdb6d39992e3f77cd56e82e4181d5947 (commit) via

[Cmake-commits] CMake branch, next, updated. v3.7.0-rc1-574-gf923940

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, next has been updated via f923940b7c9c93179b7ea6356c32c8a7beedebe2 (commit) via

Re: [CMake] Single Letter Omissions From File Path In Linker

Hi Randy, The missing character issue is likely due to some stage of your build process hitting a command line length limit on Windows. Similar problems have been described in 3D Slicer builds [1] [2], although in that case the problems were related to (a) many include directories and (b)

Re: [CMake] Single Letter Omissions From File Path In Linker

Can you create a small example that shows the problem? Even a small full example with the code you have below so I can better understand it. -Bill On 10/17/2016 10:59 AM, Randy Turner wrote: Thanks, Andrew, Bill, and Zan! I'm not completely certain that reinstalling Windows is the only or

[Cmake-commits] CMake branch, next, updated. v3.7.0-rc1-572-g2f779b2

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, next has been updated via 2f779b24d65321dc05974c46a69cc3150f3d09cd (commit) via

[Cmake-commits] CMake branch, next, updated. v3.7.0-rc1-570-g6b400f5

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, next has been updated via 6b400f503118e894685bb88f7b18ade37bca5dfe (commit) via

Re: [CMake] Single Letter Omissions From File Path In Linker

Thanks, Andrew, Bill, and Zan! I'm not completely certain that reinstalling Windows is the only or even the best solution, but once we all moved our repositories into our root directories I have not found another solution, even temporary. Of our six dev machines, it is a recurring problem on two

[Cmake-commits] CMake branch, master, updated. v3.7.0-rc1-238-g248527e

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 248527ed930ea69f9d6953a47b708044c48d5921 (commit) via

[Cmake-commits] CMake branch, next, updated. v3.7.0-rc1-564-gc7f69a3

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, next has been updated via c7f69a3ee6d693e6fb6d563d7914afb12abdca82 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.7.0-rc1-255-g9a2048f

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 9a2048f1ea6687530e209992c3f5eafcbc02b2a9 (commit) via

[Cmake-commits] CMake branch, next, updated. v3.7.0-rc1-551-gf014b34

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, next has been updated via f014b3408a942ed1be8e0bbe7767ec8e6f092f5f (commit) via

[Cmake-commits] CMake branch, master, updated. v3.7.0-rc1-232-g69be823

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 69be82394dcd9044c9aa392e0aa078a6e09ec460 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.7.0-rc1-228-g6f7c02a

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 6f7c02ab0ac83fcb23f147a41902d5ac97d4a299 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.7.0-rc1-236-g274ff52

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 274ff520925deea9bf9532673c15b96616521615 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.7.0-rc1-275-g188c762

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 188c762f8a5f690708109a3cb8d44693e599adb1 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.7.0-rc1-230-g5fdee6d

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 5fdee6d402798545280f8dc2955b21d4fe61605c (commit) via

[Cmake-commits] CMake branch, next, updated. v3.7.0-rc1-568-ga954000

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, next has been updated via a9540002c5101e533e1896a4150462f20ceac68f (commit) via

[Cmake-commits] CMake branch, next, updated. v3.7.0-rc1-555-gb09b420

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, next has been updated via b09b42069ca7cfe9510fafbf8e5282a49bb45e93 (commit) via

[Cmake-commits] CMake branch, next, updated. v3.7.0-rc1-553-gfddd061

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, next has been updated via fddd06191565ba067f82b0baa6f33beabe78ccab (commit) via

Re: [cmake-developers] Java_INCLUDE_DIRS not populated by FindJava.cmake

On Mon, Oct 17, 2016 at 15:32:06 +1100, Craig Scott wrote: > In case anyone is wondering, the use case for me is when implementing a > SWIG custom command to generate java wrappers, the jni.h header needs to be > found by the generated sources. There's FindJNI for that. --Ben -- Powered by

Re: [cmake-developers] Java_INCLUDE_DIRS not populated by FindJava.cmake

On 10/17/2016 12:32 AM, Craig Scott wrote: > Unless I'm missing something, it would seem that even though > the documentation says FindJava.cmake sets Java_INCLUDE_DIRS The documentation was wrong and was fixed in 3.7: FindJava: Do not document variables we do not provide

[CMake] Support for Visual Studio Linux cross-compiling extension

Hi, Microsoft has added support for remote-compiling and -debugging on Linux from within Visual Studio through an official VS extension: https://blogs.msdn.microsoft.com/vcblog/2016/03/30/visual-c-for-linux-development/ My question: is it already possible to generate a Visual Studio solution for

Re: [CMake] Cannot get automoc to work properly with recommended Qt5 support method

On 2016-10-16 18:40-0700 Alan W. Irwin wrote: To be explicit suppose you have some source code named fooqt.cpp which contains #include "barqt.h" which declares some classes for the software package that refer to Q_OBJECT and some classes that do not refer to Q_OBJECT. What is the #include