Add a .def file for Windows builds about rosco

[rafmudaf]

I thought thats what this line does. How are you looking to see the other symbols exported in the DLL? I'm not too familiar with building software on Windows, but I can try to find a good solution for this. Ideally, these files are autogenerated by CMake or this information is implicit in the code.

[davidheff]

OK, I may have got this wrong. I'd been building with -DIMPLICIT_DLLEXPORT which I had just picked up from

if(APPLE OR UNIX)
  if (CMAKE_Fortran_COMPILER_ID STREQUAL "Intel")
    set(CMAKE_Fortran_FLAGS "${CMAKE_Fortran_FLAGS} -DIMPLICIT_DLLEXPORT ")
  else()
    set(CMAKE_Fortran_FLAGS "${CMAKE_Fortran_FLAGS} -DIMPLICIT_DLLEXPORT -ffree-line-length-0")
  endif()
endif()

But that results in all symbols being exported, which isn't what you want.

What I will do is look at the openfast CMakeLists.txt as you suggested on my other issue and see if I can come up with something definitive.

[rafmudaf]

Right, my understanding of this was that Windows needs the explicit export preprocessor directive to export any symbols in a DLL. I thought that the default was to export no symbols on Windows, but I may be wrong.

[davidheff]

Yeah, I've confirmed that my mistake was using -DIMPLICIT_DLLEXPORT.

I'm pretty sure that what is needed, at least for an MSYS2 build under mingw-w64 is:

set(CMAKE_Fortran_FLAGS "${CMAKE_Fortran_FLAGS} -ffree-line-length-0 -static-libgcc -static-libgfortran -static")