Building Malmo from Source MacOS

[yala]

Hey everyone,

I'm having trouble building Malmo from source.
I've managed to run the MacOS release just fine, but i'd like to build from source so
I can try to solve #11.

I'm having the same issue as describe in #35

Here is my error message:
make
[ 1%] Generating C++ from XSD files...
Unknown option -generate-polymorphic
[ 2%] Building CXX object Malmo/src/CMakeFiles/Malmo.dir/AgentHost.cpp.o
In file included from /Users/Yala/Dropbox/MIT/MEng/malmo-repo/Malmo/src/AgentHost.cpp:6:
In file included from /Users/Yala/Dropbox/MIT/MEng/malmo-repo/Malmo/src/AgentHost.h:12:
In file included from /Users/Yala/Dropbox/MIT/MEng/malmo-repo/Malmo/src/MissionInitSpec.h:10:
/Users/Yala/Dropbox/MIT/MEng/malmo-repo/Malmo/src/MissionSpec.h:12:10: fatal error: 'Mission.h' file not found
#include <Mission.h>
^
1 error generated.
make[2]: *** [Malmo/src/CMakeFiles/Malmo.dir/AgentHost.cpp.o] Error 1
make[1]: *** [Malmo/src/CMakeFiles/Malmo.dir/all] Error 2
make: *** [all] Error 2

I've followed the instructions as shown in the travis script

[timhutton]

Hi Adam,

The build instructions for MacOSX changed recently: https://github.com/Microsoft/malmo/blob/master/doc/build_macosx.md

When you type xsd version what does it print?

For me:

CodeSynthesis XSD XML Schema to C++ compiler 4.0.0
Copyright (c) 2005-2014 Code Synthesis Tools CC
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

If you have the wrong xsd installed (for example the mono one) then you will get something different and this will likely cause the Mission.h problem.

Did these steps in the instructions give any error?

brew install xsd
brew unlink xsd
brew install mono
brew link --overwrite xsd

This bit of awkwardness is because the homebrew packages for mono and xsd both ship with an executable named 'xsd'.

Tim

[yala]

Ahh, I didn't notice that failed.

Force uninstalling mono and xsd and re-going through those instructions fixed it.

Thanks!