184.108.40.206. Building OpenFAST on Windows with Visual Studio¶
These instructions are specifically for the standalone Visual Studio project at openfast/vs-build. Separate CMake documentation is provided for Windows users at Section 2.2.6.
A version of Visual Studio (VS).
- Currently VS 2013 Professional and VS 2015 Community Edition have been tested with OpenFAST.
- A list of Intel Fortran compatible VS versions and specific installation notes are found here.
- The included C/C++ project files for MAP++ and the Registry are compatible with VS 2013, but will upgrade seemlessly to a newer version of VS.
- If you download and install Visual Studio 2015 Community Edition, you will need to be sure and select the
C/C++ componentusing the
Intel Fortran Compiler
- Currently only version 2017.1 has been tested with OpenFAST, but any newer version should be compatible.
- You can download an Intel Fortran compiler here.
- Only install Intel Fortran after you have completed your Visual Studio installation.
Git for Windows
- Download and install git for Windows.
Python 3.x for Windows (for regression/unit testing)
220.127.116.11.2. Compiling OpenFAST¶
A command prompt, or
git bashshell from the
Create a directory where you will clone OpenFAST repository (change
codeto your preferred name)
mkdir code cd code
Clone the OpenFAST repository
git clone https://github.com/openfast/openfast.git
This will create a directory called
openfast within the
- Using Windows Explorer, navigate to the directory
openfast\vs-build\FASTand double-click on the
FAST.slnVisual Studio solution file. This will open Visual Studio with the FAST solution and its associated projects.
NOTE: If you are using Visual Studio 2015 or newer, you will be asked to upgrade
Fast_Registry.vcxproj and the
MAP_dll.vcxproj files to a newer
format. Go ahead and accept the upgrade on those files.
- Select the desired Solution Configuration, such as
Release, and the desired Solution Platform, such as
x64by using the drop down boxes located below the menubar.
- Build the solution using the
Build->Build Solutionmenu option.
- If the solution built without errors, the executable will be located under the