fortran-lang/vscode-fortran-support

bug: incorrect interfacing with Intel compilers on Windows

gnikit opened this issue · 1 comments

gnikit commented

Is there an existing issue for this?

  • I have searched the existing issues

Description

Options for Intel compilers on Windows do not use the same types of flags or syntax as in UNIX which leads to problems.
See for example the module output directory flag module on Windows it should be /module:

https://www.intel.com/content/www/us/en/docs/fortran-compiler/developer-guide-reference/2023-1/module-001.html

This is a problem since the existing linter API interfaces expect that the compiler flags to be constant and os independent

Screenshots

No response

Expected Behaviour

Version of Modern Fortran

v3.4.2023053001

Version of Visual Studio Code

v1.80.0-insiders

Platform and Architecture

Windows

Additional Information

No response

emanspeaks commented

My temporary workaround for this is:

"fortran.linter.modOutput": " ",
"fortran.linter.extraArgs": [
	"/I\"${workspaceFolder}\\tmpmod\"",
	"/module:\"${workspaceFolder}\\tmpmod\""
],

You will still get a nuisance error message about the extra -module flag being ignored, but it suppresses further error messages due to improper handling of the default argument for this setting where it attempts to lint files in the temp location rather than recognizing the path in "modOutput" is the argument to the flag. The manually-supplied /module is then used by ifort as the fallback.

  • 👍1