Re: [CMake] find_library/find_path not working on mingw

Hi Clément, hi Omar, thanks for all you're tipps! It turns out that I had CMAKE_FIND_ROOT_PATH and the PATHS as well as the HINTS are not used if they're not somewhere under CMAKE_FIND_ROOT_PATH. Since all the libs are in a common prefix, I just added that to CMAKE_FIND_ROOT_PATH. On 02/27/2015

[CMake] creating a DLL with an OpenCV dependency

Hi. I can’t divine how to get find_package to look for boost in the various places it might be on the various systems where we do builds. Boost might be in any of these places /usr/local/include/boost /usr/local/boost/1.57.0/include /usr/local/boost/1.56.0/include etc.

[CMake] Linking header-only lib with external lib dependency in a subfolder

I am generating libs from header-only source files, I have a simple header with no dependencies, and a header with boost_filesystem and boost_system dependencies. I am facing linking problems (ld) against boost, when I link the library to the test executable. Tests are in a subdirectory, with

Re: [cmake-developers] Extracting target metadata, IDE integration

On Fri, Aug 29, 2014 at 4:20 AM, Aleix Pol aleix...@kde.org wrote: Dear cmake'rs, I'm rewriting the KDevelop plugin from scratch to fetch the information from the build directory. Now in the first implementation I'm using the compile_commands.json file that cmake already can generate for

Re: [CMake] Linking header-only lib with external lib dependency in a subfolder

By the way, I am using: cmake version 3.2.20150216-gf724a -- 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

[Cmake-commits] CMake branch, master, updated. v3.2.0-rc2-358-g0261198

20150302) +set(CMake_VERSION_PATCH 20150303) #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] CMake branch, next, updated. v3.2.0-rc2-813-g0c438b9

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

[Cmake-commits] CMake branch, next, updated. v3.2.0-rc2-815-gb80f57d

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

[Cmake-commits] CMake branch, release, updated. v3.2.0-rc2-8-g6b6852a

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

[Cmake-commits] CMake branch, next, updated. v3.2.0-rc2-807-gae266f0

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

[Cmake-commits] CMake branch, master, updated. v3.2.0-rc2-351-ge2055b1

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

[Cmake-commits] CMake branch, master, updated. v3.2.0-rc2-355-g5261c35

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

[Cmake-commits] CMake branch, master, updated. v3.2.0-rc2-353-gb3381c5

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

[Cmake-commits] CMake branch, master, updated. v3.2.0-rc2-349-g17b4423

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

Re: [CMake] CMake Version Compatibility Matrix

Hi, Wouldn't it be better to have compability matrix generated automatically? Assuming we can automate process of building CMake and executing tests for any particular version we want, couldn't we create test suite checking if feature X works in version Y of CMake? This way we could maintain

[Cmake-commits] CMake branch, next, updated. v3.2.0-rc2-810-gac5440e

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

[Cmake-commits] CMake branch, master, updated. v3.2.0-rc2-357-g56be75b

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

Re: [CMake] CMake Version Compatibility Matrix

Hi, Is there any chance that the version compatibility matrix will be updated for cmake 3.x features? Short answer: no. Longer answer: I've written and maintained the compatibility matrix before. The reasons I've stopped maintaining the page: (1) Distilling the changes between versions is

[Cmake-commits] CMake branch, next, updated. v3.2.0-rc2-817-gcf240df

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

Re: [CMake] Are CMAKE_CXX_FLAGS supposed to go on the link line?

Apparently, command line to link executable is quite different from a shared library (Modules/CMakeCXXInformation.cmake): if(NOT CMAKE_CXX_LINK_EXECUTABLE) set(CMAKE_CXX_LINK_EXECUTABLE CMAKE_CXX_COMPILER FLAGS CMAKE_CXX_LINK_FLAGS LINK_FLAGS OBJECTS -o TARGET LINK_LIBRARIES) endif()

Re: [CMake] FindMPI.cmake and MS-MPI

Andrew, Thanks for letting me know. Let me know if you have any more issues. Ben: at some point I was the maintainer for FindMPI. Are you the official maintainer now? Do you want to be? I have very limited ability to test on Windows, and that seems to be where most of the problems are.

Re: [CMake] Are CMAKE_CXX_FLAGS supposed to go on the link line?

FYI, I also came across this discrepancy recently, and logged a bug for it. http://www.cmake.org/Bug/view.php?id=15427 With the example provided in the bug report, I am seeing link errors under Xcode which I do not see under Makefiles. Clint On Monday, March 02, 2015 07:33:38 PM Roman

Re: [CMake] FindMPI.cmake and MS-MPI

Ok, sounds good to me! On 3/2/15, 11:10 AM, Ben Boeckel ben.boec...@kitware.com wrote: On Mon, Mar 02, 2015 at 09:19:00 -0800, Todd Gamblin wrote: Thanks for letting me know. Let me know if you have any more issues. Ben: at some point I was the maintainer for FindMPI. Are you the official

Re: [CMake] FindMPI.cmake and MS-MPI

On Mon, Mar 02, 2015 at 09:19:00 -0800, Todd Gamblin wrote: Thanks for letting me know. Let me know if you have any more issues. Ben: at some point I was the maintainer for FindMPI. Are you the official maintainer now? Do you want to be? I have very limited ability to test on Windows,