summaryrefslogtreecommitdiffstats
path: root/Templates
diff options
context:
space:
mode:
authorBrad King <brad.king@kitware.com>2009-10-19 19:21:01 (GMT)
committerBrad King <brad.king@kitware.com>2009-10-19 19:21:01 (GMT)
commit0140d293def838fc9e6b67bc6ac48c9ebd40c8de (patch)
treeded2732c0a66ad3be296f595e6a8184cdb4391c3 /Templates
parent91eeb6d941ecb8cffcb8427356c786a2f696d332 (diff)
downloadCMake-0140d293def838fc9e6b67bc6ac48c9ebd40c8de.zip
CMake-0140d293def838fc9e6b67bc6ac48c9ebd40c8de.tar.gz
CMake-0140d293def838fc9e6b67bc6ac48c9ebd40c8de.tar.bz2
Avoid C++ linker language in VS Fortran project
In Visual Studio project files we pass compiler flags to the whole target based on the linker language, which works for MS tools and combinations of C and C++. For the Intel Fortran plugin though the generated .vfproj files should never contain C or C++ options. We generate .vfproj files only for targets consisting only of Fortran code. Now that the linker language is computed transitively through linking it is possible that the linker language is C++ for an otherwise Fortran-only project. This commit forces Fortran as the linker language for the purpose of specifying target-wide flags in .vfproj files. See issue #9719.
Diffstat (limited to 'Templates')
0 files changed, 0 insertions, 0 deletions