[CMake] Dealing with .def and .rc files needed on Windows.

We have a project that gets built on a variety of platforms, but it mostly boils down to "windows" and "not windows". For our libraries to build on Windows, we need to also specify a .def and a .rc file in the library source files list. We have a strategy for adding these in using an extra platfo

Re: [CMake] How to install the command line tools on OSX with 3.0.2

On Tue, 30 Sep 2014 10:28:43 +1300, Glenn Ramsey said: >With CMake 3.0.2 on OSX when I try to install the command line tools I get the >following message: > >"Failed create symlink installation may be incomplete: /usr/bin/" > >With the 2.8.* versions I was able to workaround this by manually delet

[CMake] How to install the command line tools on OSX with 3.0.2

Hi, With CMake 3.0.2 on OSX when I try to install the command line tools I get the following message: "Failed create symlink installation may be incomplete: /usr/bin/" With the 2.8.* versions I was able to workaround this by manually deleting the symlinks in /usr/bin as recommended here: http:/

[CMake] CMake 3.0.1 missing CMakeLists.txt error

Dear List: I recently upgraded to CMake 3.0.1, and I am now getting the error: CMake Error at packages/stratimikos/CMakeLists.txt:15 (ADD_SUBDIRECTORY): The source directory /lore/ghansen/nightly/repos/publicTrilinos/packages/stratimikos/doc does not contain a CMakeLists.txt file.

Re: [CMake] @ONLY and nested variables

All good suggestions; thanks! –Nico On Mon, Sep 29, 2014 at 12:41 PM, Ruslan Baratov wrote: > You can run configure_package_config_file twice with code: > > SET(@PACKAGE@_LIBS @@PACKAGE@_LIBRARIES@) > > Also you can use configure_file command to create one file and include it > with config file

[CMake] EFFECTIVE_PLATFORM_NAME for iOS not in $

Hi all, I am currently working on a project for iOS and run into a problem when linking/running custom commands. My setup is xcode 5.1.1 with cmake 2.8.12.2 (but I also tried with xcode 6 and cmake 3.0.1 - same issue). On iOS the EFFECTIVE_PLATFORM_NAME happens to be appended to the target path

Re: [CMake] cmake 3.0.0 generating VS sln file default target machine type x86 (UNCLASSIFIED)

automatic selection 1) use a batch file and test things like %PROCESSOR_ARCHITECTURE% and generate a cmake -g "" 2) write a cmake script that does the test. and runs an appropraite cmake command specifying the generator instead of using msbuild, you can use 'cmake --build . --config Debug --target

Re: [CMake] cmake 3.0.0 generating VS sln file default target machine type x86 (UNCLASSIFIED)

Also, the default in cmake-gui is to prompt the user with "the same generator you used last time" as the default value for 2nd and subsequent runs of cmake-gui on any given machine by a given user... So if you choose Win64 once in cmake-gui, and you always use cmake-gui... you'll get it as the def

Re: [CMake] cmake 3.0.0 generating VS sln file default target machine type x86 (UNCLASSIFIED)

Classification: UNCLASSIFIED Caveats: NONE Thanks -simon -Original Message- From: Nils Gladitz [mailto:nilsglad...@gmail.com] Sent: Monday, September 29, 2014 10:10 AM To: Su, Simon M CTR USARMY ARL (US); Eric Wing Cc: cmake@cmake.org Subject: Re: [CMake] cmake 3.0.0 generating VS sln fi

Re: [CMake] cmake 3.0.0 generating VS sln file default target machine type x86 (UNCLASSIFIED)

On 09/29/2014 04:02 PM, Su, Simon M CTR USARMY ARL (US) wrote: Classification: UNCLASSIFIED Caveats: NONE You are right Nils. I just tried cmake vtk projects with VS2013 x64 Cross Tools Command Prompt and it is not picking the "Visual Studio 12 2013 Win64" generator. But why some of them do? Ac

Re: [CMake] cmake 3.0.0 generating VS sln file default target machine type x86 (UNCLASSIFIED)

Classification: UNCLASSIFIED Caveats: NONE You are right Nils. I just tried cmake vtk projects with VS2013 x64 Cross Tools Command Prompt and it is not picking the "Visual Studio 12 2013 Win64" generator. But why some of them do? Actually out of 10 cmake projects I build, 8 of them actually picke

Re: [CMake] cmake 3.0.0 generating VS sln file default target machine type x86 (UNCLASSIFIED)

On 09/29/2014 03:46 PM, Su, Simon M CTR USARMY ARL (US) wrote: Classification: UNCLASSIFIED Caveats: NONE Thanks for sharing. I guess I originally wanted to ask if there is a switch to cmake that will allow picking 64-bit by default if 64-bit version is available. My understanding is that (for

Re: [CMake] cmake 3.0.0 generating VS sln file default target machine type x86 (UNCLASSIFIED)

Classification: UNCLASSIFIED Caveats: NONE Thanks for sharing. I guess I originally wanted to ask if there is a switch to cmake that will allow picking 64-bit by default if 64-bit version is available. My understanding is that (for VS2013 Express), if you run things from a VS2013 x64 Cross Tools

Re: [CMake] @ONLY and nested variables

You can run configure_package_config_file twice with code: SET(@PACKAGE@_LIBS @@PACKAGE@_LIBRARIES@) Also you can use configure_file command to create one file and include it with config file that was made by configure_package_config_file: # CMakeLists.txt configure_file(FooVars.cmake.in FooV