The complain about cl is a surprise! That is part of VS 2017/s VC installation. I can assure that I can build a fortran project on the machine, so there is no issue with licensing. I can see the ifort path(C:/Program Files (x86)/IntelSWTools/compilers_and_libraries_2017.6.270/windows/bin/intel64/ifort.exe) is correct. NET FrameworkĬopyright (C) Microsoft Corporation. Intel Visual Fortran Compiler 11.1. Microsoft (R) Build Engine version 15.8.168+ga8fba1ebd7 for. – Build files have been written to: C:/Users/allen/Desktop/mumps-main/_deps/mumps-subbuild – checking that C and Fortran compilers can link - OK Mit Intel Visual Fortran Compiler 11 funktioniert folgendes nicht mehr. – checking that C and Fortran compilers can link – Check for working Fortran compiler: C:/Program Files (x86)/IntelSWTools/compilers_and_libraries_2017.6.270/windows/bin/intel64/ifort.exe - skipped – Determine Intel Fortran Compiler Implicit Link Path - done – Determine Intel Fortran Compiler Implicit Link Path – Detecting Fortran compiler ABI info - done Mehr Microsoft Visual C++ 2008 Redistributable 0.0.
Intel Corporation - Shareware - mehr Info. – Check for working C compiler: C:/VS2017/VC/Tools/MSVC/6/bin/Hostx86/圆4/cl.exe - skipped intel visual fortran compiler 11 bei UpdateStar Mehr Intel(R) Visual Fortran Compiler Integrations in Microsoft Visual Studio 10.1.13. – The Fortran compiler identification is Intel 17.1215 – The C compiler identification is MSVC 9.0 – Selecting Windows SDK version 4.0 to target Windows 3. The cmake version is the latest stable build v3.22.3.Ĭ:\Users\allen\Desktop\mumps-main>cmake.
I am trying to build mumps packages on Windows using Intel Fortran 2017 / Visual Studio 2017, but I can not let cmake to recognize Intel’s ifort and Microsoft’s cl.
0 kommentar(er)
