open TELEMAC-MASCARET The mathematically superior suite of solvers

While trying to use Intel compilers for the recent version of TELEMAC v8p4r0, the build fails due to hard coded directives for library inclusions that seems to be geared toward GFortran.

For instance, during the linking of executables, every link fails with the following text inside the link command:

which seems not to be accepted by non-GFortran compilers under Windows,

My quick-and-dirty solution was to list real library names (e.g. instead of
-lgaia4telemac2d I've put
libgaia4telemac2d.lib) but this leads to the build of large executables containing code the do not require.

Did anyone had such issue? How did you resolve it?

Hello,

Thanks for reporting this problem. This may be related to a patch I pushed last year to remove hard-coded absolute paths in Telemac binaries generated on Linux. Actually, the linking command that you pointed out is correct on Linux for all compilers, including the Intel Fortran compiler. However, on Windows, Intel relies on MSVC which behaves in a completely different way. Unfortunately, I do not have any solution at the moment, but I'll try to fix this as soon as possible and I'll open a GitLab issue in the mean time to keep track of the problem.

Hello,

That might be the case, as Intel on Windows uses MSVC linker under the hood.

Maybe the solution would be to have something similar to the line in the cfg file:
My suggestion would be to add something like this in the cfg file for Windows:and something like this for Linux:

Thanks for the help, I will have to update my local Intel configuration to test your change and update the build script accordingly. May I ask what version of oneAPI you are using?

My oneAPI version is 2023.0, I think it is the latest version available.