- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
we have the following problem:
A program that is written mainly in Fortran has a C++ main program to take care some
start-up tasks. Because of thisthe linker does not automatically include the Fortran
runtime libraries and we need to specify the directory where these are located explicitly.
However that is dependent on the particular installation and the particular version.
Is there a macro we can use (like $(ConfigurationName)or something else to make
the project file that describes the program and the associated build process in a way
that does not depend on the exact directory where the libraries are stored?
(I thought IFIDEInstallDir might do the trick, but Visual Studio does not know
about it. We are using Intel Fortran 11.x)
Regards,
Arjen
we have the following problem:
A program that is written mainly in Fortran has a C++ main program to take care some
start-up tasks. Because of thisthe linker does not automatically include the Fortran
runtime libraries and we need to specify the directory where these are located explicitly.
However that is dependent on the particular installation and the particular version.
Is there a macro we can use (like $(ConfigurationName)or something else to make
the project file that describes the program and the associated build process in a way
that does not depend on the exact directory where the libraries are stored?
(I thought IFIDEInstallDir might do the trick, but Visual Studio does not know
about it. We are using Intel Fortran 11.x)
Regards,
Arjen
Link Copied
4 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
$(IFORT_COMPILER11) is what you want. This will get you to the 11.1\nnn folder.
Edited to correct name.
Edited to correct name.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I'm sure Steve meant to enter $(IFORT_COMPILER11). And if you're using ifort 12.n, it'll be $(IFORT_COMPILER12).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Indeed it is - thanks, Jeff. I'll also note that the subfolder structure changed in version 12, so you can't just switch the environment variable names.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks for this information - it does indeed compile and link properly.
Regards,
Arjen
Regards,
Arjen

Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page