Re: [CMake] Cannot prevent import library from being created with VS generator

On Tue, 10 Jul 2018 at 09:57, J. Caleb Wherry wrote: > Side note 1: Things like this eventually lead me to have a post process (a python script) on all my VS project files to “fix” any issues like this. It might interest you to know that I've worked around it a bit by tweaking the IMPORT_PREFIX p

Re: [CMake] Cannot prevent import library from being created with VS generator

I’m also interested in this. Side note 1: Things like this eventually lead me to have a post process (a python script) on all my VS project files to “fix” any issues like this. If I can’t figure out a way to do something specific in a VS project, I just add it to my post process until I eventually

[CMake] Cannot prevent import library from being created with VS generator

I'm using CMake 3.12-rc1 on Windows 10. I have the following `CMakeLists.txt`: cmake_minimum_required(VERSION 3.8) project(cmake_test) unset(CMAKE_IMPORT_LIBRARY_SUFFIX) add_library(main MODULE "main.c") The generator is Visual Studio 15 2017. I would like to suppress the "/IMPLIB" argument crea

Re: [CMake] groups of ascii nul ('\0) characters inserted into make output but this just occurs for parallel builds (SOLVED)

On 2018-07-09 09:10+0200 Nils Gladitz wrote: On Sun, Jul 8, 2018 at 11:00 PM Alan W. Irwin wrote: My parallel builds on my Linux OS (currently Debian Buster, but this also happened for Debian Jessie so this is a long-standing problem) have ascii null ('\0) characters inserted in the output wh

Re: [CMake] How to specify library dir for imported interface?

Le mer. 4 juil. 2018 à 10:43, Marc CHEVRIER a écrit : > Next version of CMake (3.13) will supports properties LINK_OPTIONS as well > as INTERFACE_LINK_OPTIONS. > Interesting, will it fix the issue with pkg-config? When installed in a non-standard directory, pkg-config will return the library dir

[CMake] When is the TARGET_NAME generator expression necessary?

Hello, I was reading the CMake documentation regarding generator expressions, and I found the following: "$ Marks ... as being the name of a target. This is required if exporting targets to multiple dependent export sets. The ... must be a literal name of a target- it may not contain generator

Re: [CMake] Eclipse CDT4 - Unix Makefiles / Ninja Generator

Am Sonntag, 8. Juli 2018, 23:17:27 CEST schrieb Alexander Neundorf: > On 2018 M07 7, Sat 19:09:18 CEST Martin Weber wrote: > > Hi all, > > > > FYI, according to this [1], those generators do no longer work with the > > new > > core build introduced in CDT 9.5. > > > > Martin > > > > [1] http://d

Re: [CMake] specifying path for license file for commercial compiler?

On 2018-07-09 12:48- Clune, Thomas L. (GSFC-6101) wrote: [...] Based upon conversations with colleagues in other institutions, the most frustrating compiler is always the one you don’t do your development with. Because of my clients, I mostly start with Intel and then get frustrated

Re: [CMake] find_package: keyword REQUIRED ignored

Am Montag, 9. Juli 2018, 09:45:25 CEST schrieb Mark De Wit: > I thought that the find script itself was responsible for checking the > required flag? That's what find_package_handle_standard_args() does. Eike signature.asc Description: This is a digitally signed message part. -- Powered by www

[CMake] [ANNOUNCE] CMake 3.12.0-rc3 is ready for testing

I am proud to announce the third CMake 3.12 release candidate. https://cmake.org/download/ The first two 3.12.0 release candidates included a change to allow the target_link_libraries command to modify targets created outside the current directory. This has been reverted in rc3 due to problems w

Re: [CMake] CMake tried to pass all flags from gcc into nvcc when trying to add CUDA extension to current CPP project

The `CUDA_PROPAGATE_HOST_FLAGS` and `CUDA_SEPARABLE_COMPILATION` are global variables ( use `set` ) not a target properties. You can find more documentation on the legacy cuda support variable in the find cuda module ( https://cmake.org/cmake/help/latest/module/FindCUDA.html ). On Mon, Jul 9, 2018

Re: [CMake] wix msi csharp dotnet project type

If you set the WIN32_EXECUTABLE property on your WPF target then it will have the behavior you are looking for. -Caleb On Mon, Jul 9, 2018 at 10:58 AM Petar Petrov wrote: > I have gone through the cmake wix docs and in particular anything special > about dotnet csharp projects, however I failed

[CMake] wix msi csharp dotnet project type

I have gone through the cmake wix docs and in particular anything special about dotnet csharp projects, however I failed to find anything related to influencing the 'Output Type' of project's settings window inside visual studio! The options are: 'Console Application, Windows Application and Class

[CMake] CMake tried to pass all flags from gcc into nvcc when trying to add CUDA extension to current CPP project

Hi all, The situation I am currently in is as followed. This is the directory for my project: project |--CMakeLists.txt |--app ||CMakeLists.txt ||test_cuda | |CMakeLists.txt | |--

Re: [CMake] specifying path for license file for commercial compiler?

Mark and Juan, Thanks! Between your two suggestions I was able to make something work.My first attempt at using -DCMAKE_TOOLCHAIN_FILE resulted in some error messages that I completely misinterpreted as needing to “re-teach” CMAKE about the Intel compiler.A simple wrapper for the com

Re: [CMake] specifying path for license file for commercial compiler?

> On Jul 9, 2018, at 1:04 AM, Alan W. Irwin wrote: > > On 2018-07-06 20:34- Clune, Thomas L. (GSFC-6101) wrote: > >> To use the Intel compiler, one must use an environment variable that >> specifies the path to the license file. E.g., >> >> export INTEL_LICENSE_FILE=/usr/local/intel/l

Re: [CMake] specifying path for license file for commercial compiler?

You have just to put set command (not cache) for your compiler (CMAKE_Fortran_COMPILER) and environment variable in a file and specify this file on cmake command line with option -DCMAKE_TOOLCHAIN_FILE=your-file. Le lun. 9 juil. 2018 à 03:32, Clune, Thomas L. (GSFC-6101) < thomas.l.cl...@nasa.gov>

Re: [CMake] find_package: keyword REQUIRED ignored

I thought that the find script itself was responsible for checking the required flag? Our own find scripts do something along the lines of (note that we named ours sqlite, not sqlite3!) if(NOT sqlite_FIND_QUIETLY) MESSAGE(STATUS "Looking for sqlite...") endif() … look for package here … if

Re: [CMake] groups of ascii nul ('\0) characters inserted into make output but this just occurs for parallel builds

On Sun, Jul 8, 2018 at 11:00 PM Alan W. Irwin wrote: > My parallel builds on my Linux OS (currently Debian Buster, but this > also happened for Debian Jessie so this is a long-standing problem) > have ascii null ('\0) characters inserted in the output while the > corresponding non-parallel build

Re: [CMake] find_package: keyword REQUIRED ignored

Am 2018-07-08 23:34, schrieb Quaquaraquà: Hi there, I'm using a custom script [1] to look for the library sqlite3. However, the keyword "REQUIRED" (as quietly) is ignored by find_package. That is even if the library is not found, the script continues is processing: // CMakeLists.txt cmake_mini