[Cmake-commits] CMake branch, master, updated. v3.6.0-rc2-156-gd4283ca

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

[CMake] QT + CMake + Visual Studio = ui files refresh

Hi, I am currently using QT + CMake + Visual Studio and everything works great. Problem I am having is that if I change a .ui file Visual Studio does not seem to capture that during the build. If I just "touch" the header file, them everything works fine (moc gets triggered). Is there a way to

Re: [CMake] cmake install target doesn't run ldconfig after installing library

Thanks! This command really solve my problem. But I still get a problem about the command order now. I have some sub directories. For e.g. One of them is called "src" and there is also a CMakeLists.txt in it. And the shared library installation instructions are in it. So I have

Re: [CMake] oversubscribing OpenMPI in tests

Excellent, this is far better than any of the approaches I had thought of... cheers! On Thu, Jun 16, 2016 at 4:45 PM Thompson, KT wrote: > Zaak, > > > > I use ‘execute_process (${MPIEXEC} --version)’ and match the output to a > string (Open MPI, ALPS, MPICH). This isn’t the most

[Cmake-commits] CMake branch, next, updated. v3.6.0-rc2-356-g85bdd35

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 85bdd3582b2a771107b1552c978aac50deff0868 (commit) via

Re: [CMake] oversubscribing OpenMPI in tests

Zaak, I use ‘execute_process (${MPIEXEC} --version)’ and match the output to a string (Open MPI, ALPS, MPICH). This isn’t the most elegant solution, but it seems fairly robust. -kt From: CMake [mailto:cmake-boun...@cmake.org] On Behalf Of Zaak Beekman Sent: Thursday, June 16, 2016 9:14 AM

[Cmake-commits] CMake branch, next, updated. v3.6.0-rc2-352-g6493db0

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 6493db09edb969b292538b4011bd9075d956063d (commit) via

[Cmake-commits] CMake branch, next, updated. v3.6.0-rc2-350-gc3e9f73

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

Re: [cmake-developers] Toward a more deterministic ninja generator

On 06/14/2016 11:18 AM, Nicolas Desprès wrote: > It makes the ninja generator more deterministic by sorting the > build edge's inputs/outputs. It does not introduce any > regression on my macbookpro. > > This could help to fix issue #15968. What examples of non-determinism have you observed

Re: [cmake-developers] codeblocks generator: Fix include directories being in unexpected order

On 06/14/2016 11:52 AM, Tobias Hunger wrote: > https://github.com/hunger/CMake/commit/f190b069db2e430fd94b25e6287cd7fbc28661e3 > > Is the same thing updated based on suggestions from Stephen. Thanks, applied: cmExtraCodeBlocksGenerator: Do not shuffle include directories

Re: [CMake] cmake targeting vs2015 error

Update: I tried cmake 3.5.2, and that worked fine. BTW, I am trying to compile llvm+clang 3.5 with VS2015. On Wed, Jun 15, 2016 at 1:36 PM, Kristian wrote: > Could you give us either the CMakeLists.txt or the whole cl command, which > was called? > > Without of

[CMake] What do these CMake error messages mean?

CMake is giving many error messages like the below since we added OpenCV 3.1.0 to our project (and we need that new version). Can anyone help me understand what do about it and/or what the error messages are telling me? None of the 3 hits for this google search were helpful: opencv cmake

[Cmake-commits] CMake branch, next, updated. v3.6.0-rc2-348-g6ba4954

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

[CMake] oversubscribing OpenMPI in tests

Does anyone know a good way to determine if `find_package(MPI REQUIRED)` is returning OpenMPI? I need to know, because OpenMPI does not handle oversubscribed (more ranks than cores) tests well without explicitly telling OpenMPI that you are oversubscribing. This can be done by creating a hosts

[Cmake-commits] CMake branch, next, updated. v3.6.0-rc2-342-g590681a

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 590681ade20a66d7ec2750c4acd510dcdad26e3e (commit) via

[Cmake-commits] CMake branch, next, updated. v3.6.0-rc2-340-g18ebcf2

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 18ebcf28426e7d5b80b5005d1505588566009697 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.6.0-rc2-155-gf3d76a8

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

[Cmake-commits] CMake branch, next, updated. v3.6.0-rc2-338-gb8ae6f1

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

[Cmake-commits] CMake branch, next, updated. v3.6.0-rc2-336-g7e690ba

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

[Cmake-commits] CMake branch, master, updated. v3.6.0-rc2-151-g0e523d0

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 0e523d0612f50373486c2c2360004bb8ce859f92 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.6.0-rc2-144-g290913f

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 290913fab871eddee22e6ebadd3eb7ef48c1485b (commit) via

[Cmake-commits] CMake branch, master, updated. v3.6.0-rc2-138-g84c0fdb

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 84c0fdb192ccdad66dc00064b6113d7a1e63944a (commit) via

[Cmake-commits] CMake branch, master, updated. v3.6.0-rc2-153-ga854e17

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

[Cmake-commits] CMake branch, master, updated. v3.6.0-rc2-135-g2701b51

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 2701b519b17dc59b81bbf573095bfeb6fc03f326 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.6.0-rc2-146-g993991a

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 993991a07de48079233b3a04902a1f34ddfb97df (commit) via

[Cmake-commits] CMake branch, master, updated. v3.6.0-rc2-132-gce62454

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

[Cmake-commits] CMake branch, next, updated. v3.6.0-rc2-328-g6c212eb

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

[Cmake-commits] CMake branch, next, updated. v3.6.0-rc2-324-g99beaa9

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 99beaa936fa48e567cc72311ff2401eb9799820f (commit) via

[cmake-developers] [patch] FindIce updates

I have opened a couple of merge requests here, and also merged these into next for testing: https://gitlab.kitware.com/cmake/cmake/merge_requests/17 https://gitlab.kitware.com/cmake/cmake/merge_requests/19 The first adds support for the latest 3.6.x releases. The second adds support for

[Cmake-commits] CMake branch, next, updated. v3.6.0-rc2-322-g947c899

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 947c899afda22a7b432c85cdf9bec6807b383311 (commit) via

[Cmake-commits] CMake branch, next, updated. v3.6.0-rc2-317-g14050cf

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 14050cfb2b3bb266284f27064cd15d2ef919e79e (commit) via

Re: [CMake] cmake install target doesn't run ldconfig after installing library

CMake won’t and in my opinion shouldn’t implicitly invoke ldconfig for you. There are many scenarios and platforms where this is incorrect behavior and some such as running install to prepare for packaging that CMake wouldn’t reliably be able to detect. If you want to provide the functionality

Re: [cmake-developers] [Patch] Two trivial patches fixing type in CPack/DEB testcase

Am 2016-06-16 13:37, schrieb mail6543210--- via cmake-developers: Hi there, Here're two trivial patches for testing of CPack/DEB. One is for building cmake on SELinux-enabled system, and other is for a typo in the same file form the former one. These patches is based on commit 83ae7944 First

[cmake-developers] [Patch] Two trivial patches fixing type in CPack/DEB testcase

Hi there, Here're two trivial patches for testing of CPack/DEB. One is for building cmake on SELinux-enabled system, and other is for a typo in the same file form the former one. These patches is based on commit 83ae7944 First patch: When building cmake on an SELinux-enabled system, there

[CMake] Target has dependency information when it shouldn't

Hi group. I use CMake 3.3.1 with Visual Studio 2013. I've changed a target from a static library to an INTERFACE library and now I get the following message from CMake: CUSTOMBUILD : CMake error : Target <...> has dependency information when it shouldn't. Your cache is probably stale. Please