[CMake] Problem building fortran project on Windows using
Intel Fortran 10 compiler
Dunlavy, Daniel M
dmdunla at sandia.gov
Thu Oct 25 16:01:14 EDT 2007
Everything works if I add the following line to Windows-ifort.cmake:
LINK_DIRECTORIES(C:/Intel/Compiler/Fortran/10.0.025/IA32/Lib)
This is the path to the Intel Fortran Compiler libraries. Is this a bug
that this directory is not being incorporated automatically once the
ifort compiler is found?
--Danny
> -----Original Message-----
> From: cmake-bounces+dmdunla=sandia.gov at cmake.org
> [mailto:cmake-bounces+dmdunla=sandia.gov at cmake.org] On Behalf
> Of Marie-Christine Vallet
> Sent: Thursday, October 25, 2007 10:06 AM
> To: cmake at cmake.org
> Subject: Re: [CMake] Problem building fortran project on
> Windows using Intel Fortran 10 compiler
>
> Dunlavy, Daniel M wrote:
> > I have tried all of the great suggestions on this list and I still
> > have the same problems. As I mentioned before, I have tried to
> > configure the Cmake Fortran test and get the same errors. I really
> > think these errors are path related, as the specific error
> states that
> > the Fortran libraries cannot be found when linking. Is anyone using
> > Intel Fortran 10.0 and have had to do something path
> related in order
> > for Cmake to work properly?
> >
> >
> I am using it under Linux and mac, and have not problem with it.
> > I have tracked one problem down, finally, to a path issue.
> Because of
> > the space in the name of the library path, the path is
> split when it
> > is added to the link line:
> >
> > ifort.exe /nologo /W1 testFortranCompiler.obj
> /FecmTryCompileExec.exe
> > -link /INCREMENTAL:YES /subsystem:console -LIBPATH:c:\Program
> > -LIBPATH:Files\Intel\Compiler\Fortran\10.0.025\IA32\Lib user32.lib
> >
> > I have tried to re-install the Intel Fortran Compiler in a
> directory
> > without spaces, but it always resorts to installing in the same
> > directory: C:\Program Files\Intel\... I have tried to move
> the files,
> > but there must be something in the compiler setup that
> points to the
> > original directory, because it keeps choosing that
> directory for the
> > argument of -LIBPATH: in Cmake (even when the directory is gone).
> >
> Did you clean the cmake generated files? If not, I think it
> may still be using the same configuration. Like when you
> specify the compiler you want to use you have to clean up the
> files previously generated by cmake for the change to be
> taken into account.
> > Does anyone know of a workaround for handling library paths
> (or paths
> > in
> > general) containing spaces on Windows? Can this be handled
> in one of
> > the Fortran modules (CMakeTestFortranCompiler.cmake or
> > Platform\Windows-ifort.cmake or some other)?
> >
> > Thanks,
> > Danny
>
> _______________________________________________
> CMake mailing list
> CMake at cmake.org
> http://www.cmake.org/mailman/listinfo/cmake
>
>
More information about the CMake
mailing list