Re: [CMake] Visual Studio 2013, increamental builds, intermediate directories and long target names

I appreciate the feedback on this issue. Deterministically generating a GUID sounds like a real solution. ++David->Bjornbak; -Original Message- From: Brad King [mailto:brad.k...@kitware.com] Sent: Monday, June 01, 2015 12:09 PM To: BJORNBAK,DAVID (K-Sonoma,ex1) Cc: Dan Kegel; cmake; Bil

[CMake] Visual Studio 2013, increamental builds, intermediate directories and long target names

Unfortunately, we're hitting an issue migrating from VS 2012 to VS 2103 with Cmake working with long target names. Apparently the only know workarounds to the issues listed below is to shorten target names but, we're working with fairly long set of projects and it's not practical to rename the

[CMake] Is there a setting for Windows DLL file targets that's similar to CMAKE_EXE_LINKER_FLAGS ?

We here are trying to setup VS2010 for generating code coverage dataand for that I need to add a linker flag /PROFILE . For adding that to exe we have a cmake variable CMAKE_EXE_LINKER_FLAGS . But that works only for exe and you add a similar varibale for adding linker flags for DLLs. In ot

[CMake] Doesn't anyone know how to get precompiled headers working under CMake for Visual Studio 2010?

My team has been using precompiled headers under CMake and Visual Studio 2008 for quite a while. Now we've switched to VS 2010, the cmake code we used to support precompiled headers is no longer working. The following is the code in question and we're just using set_source_files_properties to

Re: [CMake] Under Visual Studio , allow developers to hit "F7" to run the INSTALL target

I dug into CMake’s C++ code and found there’s a generic setting named EXCLUDE_FROM_ALL that most “targets” use to decide if a project should be under the default build but, there’s particular target type named “GLOBAL_TARGET” does use this setting and it’s always excluded from all. Based on wh

Re: [CMake] Under Visual Studio , allow developers to hit "F7" to run the INSTALL target

Yuri, Your suggestion is close to what I’m looking for. What I need is a easy way to not this as the “Startup Project” , I need to change the property of the INSTALL target itself. By default, the INSTALL target is not in the “all” or if you open the properties on the Solution , you will find

Re: [CMake] Under Visual Studio , allow developers to hit "F7" to run the INSTALL target

I've tried similar techniques with ADD_DEPENDENCIES to ALL_BUILD and the trouble with this, within a single project these targets are not generated yet and you would have to change CMake's C++ code to change this type of behavior. CMake Error at CMakeLists.txt:231 (set_target_properties): set

Re: [CMake] Under Visual Studio , allow developers to hit "F7" to run the INSTALL target

What I'm asking for is 1) or "Can you set things up so that F7 does a full build and then automatically does the INSTALL target build?" Developers in my team have expressed a need to hit F7 during they're day to day work and the resulting being the INSTALL target. This is not a general change

[CMake] Under Visual Studio , allow developers to hit "F7" to run the INSTALL target

Developers on our team have found issues with the difference between "INSTALL" and the default build or "F7" build all under Visual Studio. My question is, there's a reasonable way to configure cmake or Visual Studio to run the INSTALL target when you hit "F7" or use the default "Build Solution

Re: [CMake] cmake 2.8.6 On Linux , link error and added

The issue has been resolved http://public.kitware.com/Bug/view.php?id=12575 ++David->Bjornbak; -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.c

[CMake] cmake 2.8.6 On Linux , link error and added headers to ..._EXTERNAL_OBJECTS for executables

I'm getting a Link error on Linux when I use CMake 2.8.6 or 2.8.5. If use CMake 2.6.3, with the exact same configuration, the link works. I did a diff on the build.make from 2.8.6 and 2.6.3 and found when I use cmake 2.8.6 On Linux adding headers to ..._EXTERNAL_OBJECTS for executables under

Re: [CMake] Linux shared library suffixes and the soft link that matches

Thanks, I got the following to work for me. set_target_properties( mylibname PROPERTIES VERSION ${GENERIC_LIB_VERSION} SOVERSION ${GENERIC_LIB_SOVERSION} ) -dave b. -Original Message- From: David Cole [mailto:david.c...@kitware.com] Sent: Tuesday, July 26,

[CMake] Linux shared library suffixes and the soft link that matches

Is there's a standard way under CMake to produce Linux shared libraries with the numbered suffix and then soft link that references the library with a numbered suffix. For example, it's common to have a build a library foo with the name libfoo.so.1.2.3 and then have a soft link named libfoo.s

[CMake] From one top level project, is there's a way to produce log files on Linux ( Unix Makefiles) in the same fashion a Windows Visual Studio build does?

>From one top level project, is there's a way to produce log files on Linux ( >Unix Makefiles) in the same fashion a Windows Visual Studio build does? For example, on Windows when you run ALL_BUILD, you will generated the following files ./projectA/source/target1.dir/Debug

Re: [CMake] Cannot add a Dependency to INSTALL Target

Tyler, What I'm really working is, I want to install debian files ( *.deb files ) during an installation or INSTALL target. I tried using INSTALL(CODE [SCRIPT] point to execute_process command but, execute_process does not play nice with this path either. I prefer to have ALL_BUILD just

[CMake] Cannot add a Dependency to INSTALL Target

Under CMakeLists.txt files, I want to add a dependency so Install will run a target add_custom_target(3rd_party_install ALL) ADD_DEPENDENCIES(INSTALL 3rd_party_install ) When I run cmake, it complains INSTALL is not defined yet but, it is if I exclude this new depenency -- Adding 3r