It seems that this special case also applies to LFortran on Windows with MSVC. This PR needs more work.

Thanks Carlos @brocolis! What's the naming convention for *.lib files? Do they always start with lib like on Linux or is it different?

What's the naming convention for *.lib files? Do they always start with lib like on Linux or is it different?

They don't always start with lib, it is different, it is usually name.lib, for example kernel32.lib, shell32.lib, etc.

It seems that this special case also applies to LFortran on Windows with MSVC. This PR needs more work.

This is a separate issue. It requires changes in LFortran.

It seems that this special case also applies to LFortran on Windows with MSVC. This PR needs more work.

This is a separate issue. It requires changes in LFortran.

Maybe LFortran's command line interface could attempt to do a normalization before passing anything through to MSVC's or GCC's linker. This way we don't have to pull any stunts in fpm to check whether the compiler wrapper is currently targeting MSVC or GCC. Not sure how pass-through arguments are currently handled in LFortran, in GCC we have -Wl, to pass arguments to the linker without affecting the compiler wrapper.