I am trying to compile the latest trunk version of DELFT 3D (8712)
using the following requisites:
- Microsoft Visual Studio 2015 Enterprise (Update 3)
- Intel Parallel Studio XE 2018 (Update 2)
- Microsoft .NET Framework 4.7.02556
- Python 2.7 and 3.6
I successfully generated the solutions using prepare_sln.py using the
configuartion above. I have added the modules below in VS2015:
- "Common Tools for Visual C++ 2015" -
"Microsoft Foundation Classes for C++"
Then, I have opened the delft3d_open solution and started to
compiled, which process went well until I got the following message:
86>------ Skipped Build: Project: flow2d3d_openda, Configuration:
Release x64 ------ 86>Project not selected to build for this
And then the build process didn't go any further. I have stopped the
compilation and killed VS2015 through Task Manager.
I have installed the VS2017 Enterprise with all C, C++ and Fortran
modules and downloaded the source code again from trunk version. I
have followed the same process to generate the solution and opened it
in VS2017, but the build process freezes at the same message. Then I
killed VS 2017 through Task Manager.
The curious thing about this is that I am running all the examples,
but I am not sure if not compiling flow2d3d_openda will change the
I have uninstalled and reinstalled the programs and tried again, but
I am struggling at the same point. Please find attached the Output file.
Please could you give me a hand on this thread?
Many thanks in advance,
It seems that the problem is with flex.exe and byacc.exe. You can
easily check this by runinng one of this file. This causes high CPU
consuming and memory leak.
Kostia is right: flow2d3d_openda finished normally (it should indeed
not be used), but another build step is hanging: the compilation of
the tool "vs". You can see this in your file
"Output-Build.txt"; the las line refers to build step number 29.
Fortunately, you probably will not need the tool "vs". So
you can skip it.
Scanning your file "Output-Build.txt", I do see some
messages that I don't expect, but they don't seem blocking. If the
examples run fine, you can continue.