Why is my OpenStudio with Python bindings build not working?
Following on from this question, I'm getting around to trying to build OpenStudio myself and not succeeding (I'm new to Visual Studio and CMake). I have the environment set up for Windows as explained here. The steps I've followed are:
Installed the software listed (though with VisualStudio 2015 Community Edition instead of Visual Studio 2013).
Added
C:\Qt\Qt5.3.2\5.3\msvc2013_64_opengl\bin
to the SystemPath
.Clone the repository, and created a
build
directory.Launched CMake and set the path to the source code
C:\OpenStudio
and the build path toC:\OpenStudio\build
That's where the instructions stop, but pressing on...
Hit
Configure
and selectedVisual Studio 14 2015 Win64
(since I'm using 2015 Community Edition) from the dropdown, left the radio button on the default,Use default native compilers
This seems to run ok for a while before reporting:
Could NOT find SWIG (missing: SWIG_EXECUTABLE SWIG_DIR) (Required is at least version "3.0.0")
Set
SWIG_EXECUTABLE
in CMake and reranConfigure
- success!Hit
Generate
- success!Open up Visual Studio 2015 and open the new
OpenStudio.sln
fileRan
Build > Build solution
, which runs for a long time and then fails with this error:
Code
MSB006
Description"cmd.exe" exited with code 1.
ProjectOSCore
FileC:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.CppCommon.targets
Line171
It's taken me a long time to get to this point so I'd hate to give up now. Can anyone explain how to find out what's going wrong and how to fix it?
The Output contents are here.
Edit
I've added BOOST_LIBRARYDIR
as C:\local\boost_1_55_0\lib64-msvc-12.0
and BOOST_ROOT
as C:\local\boost_1_55_0
but they don't seem to be getting picked up.
@Jamie Bull I spent many (many) hours earlier this week trying to get a working build as well. I had a working build (to generate the python bindings) before, but I think when I upgraded to Visual Studio 2015 it broke my build for some reason. I would try to build with Visual Studio 2013. I will keep trying to troubleshoot the VS2015 builds.
@MarkAdams I appreciate the effort. One more try then with VS 2013... here goes nothing!
Jamie, in case you succeed, could you make it a detailed tutorial please? It seems that it would be definitely useful...
Yes, I will do. It seems to have built correctly on Visual Studio 2013 but I've not had a chance to test it yet.
(unrelated, but speaking about awful and terrible things to do... installing iruby (Ipython notebook with ruby kernel) on windows. I gave up)