Issue when compiling OpenFAST with VS Code 2022 and IFX Fortran Compiler

[ajmlu]

Dear all,

I am trying to compile OpenFAST following the documentation provided here: https://openfast.readthedocs.io/en/dev/source/install/install_vs_windows.html. I am using VSCode Community 2022 and the IFX Intel Fortran Compiler (as IFORT as recently be deprecated). However I always facing the same error that I don't manage to solve alone (x64\Release\simclist.obj: not a COFF object, bitcode, archive, import library or resource file
FASTlib : error PRJ0019: A tool returned an error code). I attached below the entire build output.

Do you have any insights on how I can solve this?

Thanks for you help.

Error_compiling_OpenFAST.txt

[andrew-platt]

Which version of OpenFAST are you trying to compile?

[ajmlu]

The dev branch of OpenFAST 3.5.4

[deslaughter]

I was able to reproduce the issue on my Windows system, though I'm not sure what's causing it. As a temporary workaround, I was able to get the system to build by opening vs-build/MAPlib/MAP_dll.sln and building that solution first, then building FAST from FAST.sln. Please give this a try and see if it works while we try to come up with a better solution.

[andrew-platt]

@ajmlu, could you try compiling again with the latest dev branch?

[ajmlu]

Thanks a lot for your help!

@andrew-platt I just tried to compile again from the latest dev branch and I still get the same error (
Error_compiling_OpenFAST.txt)... Could that be due to an other thing than using IFX?

@deslaughter Thanks for this workaround! Where can I find this file vs-build/MAPlib/MAP_dll.sln? I could not find it anywhere on the Github repository.

Thanks again for your time and support!

[deslaughter]

@ajmlu I apologize, the MAP_dll.sln that I had was left over from a previous version of OpenFAST. However, I was able to build the full solution with the latest changes to the dev branch. Please try removing the build directory and cleaning the solution before rebuilding. Sometimes Visual Studio will try to reuse files that it thinks haven't changed so it's best to start clean when troubleshooting these issues.

[abhinaygoga1]

Dear FAST Community,

I am experiencing a similar issue (PRJ0019) while compiling the latest Dev 4.0.2 source code using Visual Studio 2022 and the Intel IFX compiler.

Following the recommended steps, I first successfully compiled MAP and Registry. However, when I proceed to build the Library, the process fails. It does not generate the expected .lib file in the build folder, which in turn prevents the compilation of the FAST executable.

I have attached the log file below for reference. Any insights or suggestions on how to resolve this issue would be greatly appreciated.

BuildLog.txt

[andrew-platt]

@abhinaygoga1, I don't see exactly what the error is from your BuildLog.txt. If you clean the solution before building MAP and the registry, then try building the executable, does it work?

[abhinaygoga1]

@andrew-platt

I first built the MAP and Registry projects before proceeding with FASTlib and FAST.

Upon comparing the build process between V3.0.0 (the last stable version that successfully builds on my setup) and V4.0.2, I observed a key difference in the MAP compilation process. In the newer version (V4.0.2), the build generates .pdb and .lib files, but it does not produce .dll and .exp files.

To address this, I examined the old project file and modified the MAP build settings, changing the "StaticLibrary" option to "DynamicLibrary" at lines 29, 35, 41, and 48. After this change, the compilation successfully generated .dll and .pdb files, but still did not produce .lib and .exp files.

Observations and Workarounds
Since the missing .dll, .lib and .exp files from the MAP build caused the FASTlib and FAST compilation to fail, I explored two workarounds:

Copying MAP Build Files from V3.0.0

I copied the compiled MAP build files from V3.0.0 into the V4.0.2 directory.
I then proceeded to build only Registry, FASTlib, and FAST.
The build completed successfully, and the compiled FAST executable functioned as expected.

Two-Step Compilation for MAP

First, I compiled MAP as a StaticLibrary, obtaining .pdb and .lib files.
I backed up these files and then modified the MAP build settings to DynamicLibrary again.
Recompiling MAP now produced the missing .dll file.
Using these three files (.dll, .lib, and .pdb), I then compiled Registry, FASTlib, and FAST, which resulted in a unsuccessful build again. Here .exp file is still missing.

Root Cause
It appears that compiling MAP as either static or dynamic alone prevents the necessary build files from being generated, leading to missing dependencies for FASTlib and FAST. The issue originates from the MAP project settings, affecting the availability of required files in the build process.

I hope this information is helpful in diagnosing and implementing a fix.

Best regards,

[hope111-eng]

Pls is this problem solved？I am also having the exact same problem as you, thank you for your help