- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Previously visual studio ~2015, with Intel MPI library 2018 update 3 and Intel Parallel XE 2015 update 1 to run a *.sln with 16 projects all F95. Two of these used MPI and compose >1000 routines. I have moved to vs2022 and the ifx/ifort 2024 packages with the oneAPI background. I found some comments on how to link and run these MPI codes but they did not seem to correlate with the directory structure I was provided. The PATH and ENV variables didn't set up. So I went searching for mpi.mod, impi.lib to link and impi.dll to run and did this manually. I ended up with :
Fortran>Additional Include Libraries : C:\Program Files (x86)\Intel\oneAPI\mpi\2021.11\include\mpi
Linker>Additional Include Libraries : C:\Program Files (x86)\Intel\oneAPI\mpi\2021.11\lib\
Linker>Additional Dependencies : impi.lib
and two PATH additions to locate the debug and release versions of impi.dll, eg C:\Program Files (x86)\Intel\oneAPI\mpi\2021.11\bin for the release version.
These work fine. But I am concerned that I appear to be using the ifx compiler to generate the exes but I am using the mpi.mod and impi.lib files from the ifort release that is going to removed at some point. Is this correct ? or is there a way to link the mpi.mod and impi.lib .syslink versions of these files that are sitting in the ifx 2024 dirs that I'm unaware of ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
It is (should be) always OK to use newer run-time libraries with older compilers. Also, ifort and ifx use the same run-time libraries and module formats.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page