Re: [cmake-developers] CMake for 64Win7

Good day! You can try the experimental installer (based on IFW generator) from my website: http://ifw.podsvirov.pro/cmake/files/v3.5/cmake-3.5.0-rc3-win64-x64.exe You can also try the online version, which is based on code from branch "master":

Re: [CMake] Compile shared library and call it's functions

Hi, On Mon, Mar 7, 2016 at 9:29 PM, Ivan wrote: > Hello! > > Here is my CMakeLists.txt: > > cmake_minimum_required(VERSION 3.3) > project(untitled19) > > set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -std=c++11") > > set(LIBRARY_SRC library.cpp) > > add_library(libra SHARED

[CMake] Fwd: Create main and sub-projects; be able to compile them together and individually.

Hi, I am new to cmake and really hope am doing this correctly. I asked stackoverflow but didn't get a good enough answer for my specific problem here; If I want root/sub-directories/ as separate sub-projects that can be compiled using the individualCMakeLists.txts in their folders I find myself

Re: [CMake] Best way to show/include CMake files in IDE

On 3/7/16, Eric Wing wrote: > On 3/7/16, David Cole wrote: >> If you include those files in the source list for a library, executable, >> or >> custom target, they should show up in IDE projects, and they should be >> ignored by Makefile type projects. Have

Re: [CMake] Best way to show/include CMake files in IDE

On 3/7/16, David Cole wrote: > If you include those files in the source list for a library, executable, or > custom target, they should show up in IDE projects, and they should be > ignored by Makefile type projects. Have you tried that? > > > David > I haven't tried it yet

[cmake-developers] CMake for 64Win7

Dear Sirs, There are only 32Win version of CMake( cmake-3.5.0-rc3-win32-x86.msi or cmake-3.5.0-rc3-win32-x86.zip ) on your web page( https://cmake.org/download/ ). When will the version for 64Win available? Thank you for the help! Ning. == LI, Ning. Ph.D.

Re: [CMake] Best way to show/include CMake files in IDE

If you include those files in the source list for a library, executable, or custom target, they should show up in IDE projects, and they should be ignored by Makefile type projects. Have you tried that? David > On Mar 7, 2016, at 6:34 PM, Eric Wing wrote: > > I have a

Re: [cmake-developers] C# support ready for review

Seems to me like C# support should work just fine with other generators: ninja, nmake, and UNIX Makefiles included. Especially with mono on Linux/Mac. David > On Mar 7, 2016, at 2:12 PM, Brad King wrote: > >> On 02/25/2016 05:51 AM, Stuermer, Michael SP/HZA-ZSEP

[CMake] Best way to show/include CMake files in IDE

I have a bunch of .cmake support files in my project that I have split off from CMakeLists.txt (using INCLUDE to combine them) to separate concerns. (Source files, application assets, script files, platform settings, codesigning, etc.) This works, but they don't show up in IDEs (Visual Studio,

Re: [cmake-developers] patch for module GetPrerequisites

We have to call : fixup_bundle("${CMAKE_INSTALL_PREFIX}/../test"... to fix an optional test folder installed near the app. verify_app will later compare a path like C:/program/app/../test to C:/program/test and state they are inequal while they point to the same file. That's why I have to call

Re: [CMake] Support OpenBLAS in FindBLAS module

Hi all, Is there any update on this issue? I believe this addition would be really useful. Best regards, Xavier On Sat, Nov 29, 2014 at 4:12 AM, Rob Zumwalt wrote: > Apologies for the new thread, I just subscribed in order to comment on > this, and didnt know how to

Re: [CMake] how to keep rpath from build to install

Hi Srinath, I guess you will find what you need here: https://cmake.org/Wiki/CMake_RPATH_handling Best regards, Xavier On Mon, Mar 7, 2016 at 4:35 PM, Srinath Vadlamani < srinath.vadlam...@gmail.com> wrote: > Hello All, > How do I keep the rpath used during the build of an executable the

[CMake] Compile shared library and call it's functions

Hello! I hope someone could finally help me. I spent about two days to find solution for my problem, but with no luck. Here is my problem: I want to create a shared library (dll on Windows, .so on Linux, .dylib on OS X) that contains some functions. This library should export only these

Re: [cmake-developers] Proposed patch for 0014140: Ninja generator doesn't set version in dylib

On Mon, Mar 7, 2016 at 8:06 PM, Brad King wrote: > On 03/07/2016 02:49 PM, Bruce Stephens wrote: >> Moving the method into there worked cleanly. > > Thanks. I split that into a separate commit: Thanks. I wondered whether or not to do that separately. -- Powered by

Re: [cmake-developers] Proposed patch for 0014140: Ninja generator doesn't set version in dylib

On 03/07/2016 02:49 PM, Bruce Stephens wrote: > Moving the method into there worked cleanly. Thanks. I split that into a separate commit: cmCommonTargetGenerator: Adopt AppendOSXVerFlag method https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=1f2b39c6 Then I applied the main change:

[Cmake-commits] CMake branch, next, updated. v3.5.0-rc3-346-g575399a

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

Re: [cmake-developers] Proposed patch for 0014140: Ninja generator doesn't set version in dylib

On Mon, Mar 7, 2016 at 6:06 PM, Brad King wrote: > On 03/01/2016 04:58 PM, Bruce Stephens wrote: >> I just copied the relevant code from the Makefiles generator. > > Thanks. Instead of copying, please look at moving the relevant > methods up to cmCommonTargetGenerator so

Re: [cmake-developers] C# support ready for review

On 02/25/2016 05:51 AM, Stuermer, Michael SP/HZA-ZSEP wrote: > The part that probably needs most additional work is all the > C# detection and configuration part in the module scripts. In your branch Modules/CMakeDetermineCSharpCompiler.cmake currently has a lot of logic and environment checks

[Cmake-commits] CMake branch, next, updated. v3.5.0-rc3-343-gb6b5792

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

Re: [cmake-developers] Proposed patch for 0014140: Ninja generator doesn't set version in dylib

On 03/01/2016 04:58 PM, Bruce Stephens wrote: > I just copied the relevant code from the Makefiles generator. Thanks. Instead of copying, please look at moving the relevant methods up to cmCommonTargetGenerator so it can be shared between the two generators instead. Thanks, -Brad -- Powered

Re: [cmake-developers] [PATCH] Enable CMAKE_EXPORT_COMPILE_COMMANDS by default

On 03/02/2016 04:36 AM, Richard Wiedenhöft wrote: > The way I see it there is no downside to this and it spares me (and > hopefully others) from polluting my CMakeLists.txt with > "set(CMAKE_EXPORT_COMPILE_COMMANDS ON)" making them more readable. The down side is it takes longer to generate and

Re: [cmake-developers] [PATCH] FindProtobuf: variable case matches module name

On 03/01/2016 03:15 AM, Antonio Perez Barrero wrote: > Use recommended case for variable names. i.e. matching name of the > module as passed to `find_package`. > > For backwards compatibility, the upper case versions of both input and > output variables are used and defined when appropriate.

Re: [cmake-developers] patch for module GetPrerequisites

On 03/04/2016 12:17 PM, Benjamin Ballet wrote: > The fail occurs during verify_app in the function gp_resolved_file_type > from module GetPrerequisites. This function test if two paths are equal > without translating them to there canonical form before. [snip] >

Re: [cmake-developers] [PATCH v3] Add FindLTTngUST module to find LTTng-UST library

On 02/29/2016 12:35 PM, Philippe Proulx wrote: > This patch adds the FindLTTngUST module which can be used to find > the LTTng-UST library. It sets result variables and creates an > imported target, LTTng::UST. Thanks, applied: Add FindLTTngUST module to find LTTng-UST library

[Cmake-commits] CMake branch, next, updated. v3.5.0-rc3-341-gf10ee09

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

[Cmake-commits] CMake branch, next, updated. v3.5.0-rc3-339-g3b0b7f7

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

[Cmake-commits] CMake branch, next, updated. v3.5.0-rc3-337-gf6b21eb

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

[Cmake-commits] CMake branch, next, updated. v3.5.0-rc3-335-gc8d860b

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

[CMake] how to keep rpath from build to install

Hello All, How do I keep the rpath used during the build of an executable the same when I install that executable using INSTALL(TARGETS )? I do set : SET(CMAKE_INSTALL_RPATH_USE_LINK_PATH TRUE) = Srinath Vadlamani = --

[Cmake-commits] CMake branch, master, updated. v3.5.0-rc3-163-ge0751c4

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

[Cmake-commits] CMake branch, master, updated. v3.5.0-rc3-171-g8256d02

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

[Cmake-commits] CMake branch, next, updated. v3.5.0-rc3-331-gb5652bf

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

[Cmake-commits] CMake branch, next, updated. v3.5.0-rc3-333-g365fb19

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

[Cmake-commits] CMake branch, master, updated. v3.5.0-rc3-169-g7fc8e4d

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

[Cmake-commits] CMake branch, master, updated. v3.5.0-rc3-167-gcfb4d77

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

[Cmake-commits] CMake branch, master, updated. v3.5.0-rc3-165-g9fcc8ff

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

[Cmake-commits] CMake branch, next, updated. v3.5.0-rc3-319-g38a68b7

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

[CMake] install to CMAKE_BINARY_DIR fails if CC=icc

Dear CMakers, I encountered a strange problem with my cmake setup: In my CMakeLists.txt files there is a line install(TARGETS ${PROJECT_NAME} DESTINATION ${CMAKE_BINARY_DIR}) Some of my projects use add_subdirectory, and with make install I "pull" them right to the build directory. This used to

Re: [CMake] Visual Studio + Ninja?

Short version: no. Long version: Visual Studio is heavily built around MSBuild as the back-end of execution of various tasks. While theoretically it could be done that MSBuild only acts as a relay and calls into Ninja scripts, you would lose the entire feature set of Solution Explorer, which