Re: [CMake] 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 Qt Creator, but I help maintain several projects that use Visual Studio and MinGW gfortran via the CMakeAddFortranSubdirectory feature. This feature is somewhat limited and not really maintained (in my exper

[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] List all packages

On 2019 M01 13, Sun 09:43:03 CET Lectem wrote: > Hi, > > Is there a way to list all the packages (both config files and find-modules) > that find_package could find ? Could we even imagine this would also permit > to list the variables and targets created in it ? I think that would be a > very hel

Re: [CMake] List all packages

Thanks for the answers You can visualize dependencies between targets with Graphvis: This is not really what I need, I want to see all the available packages installed on my PC (package registry, Find_XXX modules …), not the hierarchy of targets in a cmakelists.txt Hey, As far as I k

Re: [CMake] List all packages

Hello, Lectem.11:43, 13 January 2019 г., Lectem : Hi, Is there a way to list all the packages (both config files and find-modules) that find_package could find ?Could we even imagine this would also permit to list the variables and targets created in it ?I think that would be a very helpful to have

Re: [CMake] List all packages

Hey, As far as I know there is no such mechanism. But you can write a little script f.e. in python (or cmake itself) which can do that, because it is just a simple file search. Greetings Tonka Am So., 13. Jän. 2019, 09:43 hat Lectem geschrieben: > > > Hi, > > > > Is there a way to list all the

[CMake] List all packages

Hi, Is there a way to list all the packages (both config files and find-modules) that find_package could find ? Could we even imagine this would also permit to list the variables and targets created in it ? I think that would be a very helpful to have for debugging find_package, especially whe