Need a Way to Compile the FAST Dynamic Library for Calling OpenFAST within Simulink about openfast HOT 7 CLOSED

Wouldn't turning on shared library ON in CMake allow using openfastlib.so with Simulink?

from openfast.

@sayerhs, yes you are correct (I didn't know this until reading your comment), for cmake builds, but there is currently no equivalent build for visual studio. (The vs-build of the FASTlib, does not include the FAST_Library.f90 file, and the vs-build output is only a static library)

from openfast.

A couple of differences with the openfastlib.so as it seems to be implemented in CMake:

• It should use the Matlab libmex library so that all messages that normally get written to the screen appear in the Matlab command window. On Windows with Intel Fortran, we replace SysIVF.f90 with SysMatlab.f90 (which calls Matlab routines for printing) and link with libmex.lib from the Matlab installation. As far as I know, no one has modified the other Sys*.f90 files for other platforms/compilers.
• It should use the COMPILE_SIMULINK preprocessor directive.

Instructions for how this is supposed to work are on pages 54-55 of the FAST8 ReadMe

from openfast.

One other thing to note here is that FAST_Library.h is used in FAST_SFunc.c (which gets compiled in MATLAB as a mex file). It looks like the interfaces defined in the header file have changed, but the code that calls those routines in FAST_SFunc.c has not.

from openfast.

Thanks @bjonkman.

@ghaymanNREL This may have to be addressed to have Simulink work again with OpenFAST. I was not aware that Simulink uses the "OpenFOAM" module in OpenFAST.

from openfast.

@gantech Simulink doesn't use the OpenFOAM module. However, it does use some of the same FAST_Library.f90 interface routines (e.g., the Sizes, Start, Update, and End routines). FAST_Library.f90 and FAST_Library.h were originally created for the Simulink interface; I just expanded them a bit when we needed a similar interface to link with OpenFOAM.

from openfast.

@rafmudaf , since this has been merged into OpenFAST/dev I think this issue can be closed.

from openfast.