Brad King wrote:
> Can you modify the project file through the IDE by hand to chose the
> linker you want?
s/chose/choose/
To be more clear, if it is possible to modify the project in the IDE
by hand to change the linker, then we can teach CMake to generate the
project file accordingly. If it is
Andreas Mohr wrote:
> On Fri, Jun 25, 2010 at 08:23:06AM -0400, cmake-requ...@cmake.org wrote:
>> So is there any way in cmake to enforce Visual Studio to use link.exe
>> instead of xilink.exe?
>
> grep -i LINK /usr/share/cmake-2.8/Modules/Platform/*|less
>
> yields a ton of link-related CMake v
Marcus Sindermann wrote:
> Now we want to use update 65 of the Fortran compiler. This update
> enforces Visual Studio to use the Intel Fortran xilink for linking
> Fortran projects.
CMake just generates the .vfproj file and then VS is responsible for
the actual build. If the Fortran plugin is cho
On Fri, Jun 25, 2010 at 08:23:06AM -0400, cmake-requ...@cmake.org wrote:
> So is there any way in cmake to enforce Visual Studio to use link.exe instead
> of xilink.exe?
grep -i LINK /usr/share/cmake-2.8/Modules/Platform/*|less
yields a ton of link-related CMake variables during platform setup,
Hi!
We have a problem on Windows with Visual Studio projects and the Intel Fortran
11.1 compiler.
We have a project the contains Fortran sources and links a static C++ library. So in Visual Studio this project is a Fortran project. With update 38
of the Fortran compiler this was working without