[CMake] How to specify gfortran in an MSVC project

I would like to try to use 64-bit gfortran to compile a project in which the rest of the code is compiled with Visual C++ 2017. I've read the netlib article (http://www.netlib.org/lapack/lawnspdf/lawn270.pdf) but it doesn't address my problem, which is how to help CMake select the right Fortran

Re: [CMake] How to specify gfortran in an MSVC project

s for all the other libraries as well. Warm regards, Stephen. From: Thompson, KT Sent: 14 January 2019 04:06 To: Stephen Morris ; cmake@cmake.org Subject: Re: How to specify gfortran in an MSVC project Hi Stephen, I am also interested in Kitware's response to your question. I don't use Q

[CMake] Correct use of VS_DEBUGGER_WORKING_DIRECTORY etc.

I’m trying to use the new VS_DEBUGGER_WORKING_DIRECTORY and VS_DEBUGGER_COMMAND properties to facilitate debugging in a CMake-generated Visual Studio project file (in my case Visual Studio 2013). Everything else in my configuration works except this… I’ve noted from ‘regular’ Visual Studio

Re: [CMake] Correct use of VS_DEBUGGER_WORKING_DIRECTORY etc.

ROPERTIES VS_DEBUGGER_WORKING_DIRECTORY "$" VS_DEBUGGER_COMMAND "$" VS_DEBUGGER_ENVIRONMENT "PATH=%PATH%;${CMAKE_PREFIX_PATH}/bin") From: Stephen Mor

[CMake] Preventing multiple definitions of metaObject methods

Suppose I have a class that derives from QObject, and contains the Q_OBJECT macro in its header file. When I compile it using AUTOMOC enabled, a "moc_myClass.cpp" file is created; if I manually include that file at the end of my 'myClass.cpp" file, then the moc file will be compiled there,

Re: [CMake] Preventing multiple definitions of metaObject methods

-Original Message- From: Kyle Edwards Sent: 13 September 2019 16:54 To: Stephen Morris ; cmake@cmake.org Subject: Re: [CMake] Preventing multiple definitions of metaObject methods >Stephen, >Could you post a minimally reproducible example with CMakeLists.txt and >accompanyi

Re: [CMake] Preventing multiple definitions of metaObject methods

-Original Message- From: Kyle Edwards Sent: 13 September 2019 16:54 To: Stephen Morris ; cmake@cmake.org Subject: Re: [CMake] Preventing multiple definitions of metaObject methods >Stephen, >Could you post a minimally reproducible example with CMakeLists.txt and >accompanyi

Re: [CMake] Stray backslash appearing when CMAKE_CXX_FLAGS_RELEASE used in custom command

On 4 November at 08:43, Eric Doenges wrote: > Welcome to the wonderful world of lists and their interaction with quoting in > CMake ! Since space is used > as a list item separator outside of double quoted strings, CMake is escaping > the space within CXX_FLAGS > to keep it as a single element

[CMake] Accessing -fPIC and -std settings within CMake definitions

I'm setting up a custom build step to build a precompiled header in gcc (yes I know that native support is coming with CMake 3.16, but I need to get something working on an older version). My approach is basically to set up a custom command thus: set_target_properties(mytarget PRIVATE

[CMake] Stray backslash appearing when CMAKE_CXX_FLAGS_RELEASE used in custom command

On 1 November at 10:02, Stephen Morris wrote: > My approach is basically to set up a custom command thus: > set(CXX_FLAGS ${CMAKE_CXX_FLAGS} ${CMAKE_CXX_FLAGS_DEBUG}) .. or whatever, > depending on the current configuration.. > get_target_property(compile_options, mytarget, COM

[CMake] find_package to find Cygwin versions of Flex and Bison in Windows

To compile my application I need to use the Flex and Bison applications. To compile under Linux, all I need to do in my CMakeLists.txt file to find them is find_package(FLEX REQUIRED) find_package(BISON REQUIRED) ...and everything works as expected. In Windows, however, I'm using the

Re: [CMake] find_package to find Cygwin versions of Flex and Bison

Stephen Morris: > To compile my application I need to use the Flex and Bison > applications. To compile under Linux, all I need to do in my > CMakeLists.txt file to find them is > > find_package(FLEX REQUIRED) > find_package(BISON REQUIRED) > > ...and ever