Latest Posts

Changes in BuildingWidelandsWIN10

Revision Differences of Revision 5

# Building Widelands on Windows-10 ¶

As of some, mhh, issue I lost access to my OSX computer and had to fall back to some cheap WIN-10 machine. But of course I wanted to develop Wideands there, too. ¶
So I started by installing the [Bash on ubunto on Windows](https://msdn.microsoft.com/commandline/wsl/about) for Windows-10. This is not only a bash ¶
but a complete (?) Ubuntu like subsytem. I started installing bzr which worked like on Ubutu and is described in the [[ BzrPrimer ]], that was easy. ¶

using ./comiple.sh I checked the missing pieces and got: ¶
~~~~ ¶
sudo apt-get install bzr cmake g++ gcc gettext libboost-dbg libboost-regex-dev libboost-test-dev libglew-dev libpng-dev libsdl2-dev libsdl2-image-dev libsdl2-mixer-dev libsdl2-ttf-dev python zlib1g-dev ninja-build ¶
~~~~ ¶
which is actually the same as described for Ubuntu in [[ Building Widelands ]]- ¶

after that ./compile.sh worked with ninja and did its job like a charm. (That Mac MBoo has 8 virtual cores, this machine just 4, well) ¶

after compilig when calling ./widelands I got: ¶

~~~~ ¶
what(): [../src/wlapplication.cc:332] Failed to initialize SDL, no valid video driver: Failed to connect to the Mir Server ¶
~~~~ ¶

Whats is missing is some kind of Display Driver so I went along this Artilce [How To Run graphical....](http://thehackernews.com/2016/07/ubuntu-gui-windows-10.html) which starts with a [[VcXsrov Windomws X Server]] (https://sourceforge.net/projects/vcxsrv/) startimng this with ¶

~~~~ ¶
ex
port DISPLAY=lovcalhost:0 ¶
~~~~ ¶

I can start widelands, but get an ugly default X-Window pointer and can not us
emr any input. So I weant ahaead and installed xfwm4, this allowed me to start widelands and :-)enter some text.

More to come
...