What I had to do to build aseprite on windows

[Emma Krantz]

I had a few problems getting aseprite compiling on windows. Here are the steps I followed to get a working build, using Visual Studio Community 2015.

1) Compile Skia: for whatever reason, using the standard ninja -C out/Release dm method didn't work. Instead:

a) Open Command Prompt. Run "C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\bin\vcvars32.bat".

b) In the same Command Prompt, run python make.py. Note that you must use python 2, and not python 3.

2) Compile Aseprite: I couldn't get aseprite compiling with MinGW and gcc. I ran into all sorts of errors, including c++ 11 code not being compiled with -std=c++11, and gcc not being able to find the winsock libraries. These are probably problems with the cmake settings, but I couldn't be bothered trying to learn cmake to fix them. So:

a) Get cmake to generate a VS solution: cmake -DUSE_ALLEG4_BACKEND=OFF -DUSE_SKIA_BACKEND=ON -DSKIA_DIR=C:\build\skia -G "Visual Studio 14" ..

b) Open the solution in VS. Right click the aseprite project and click Properties, then go to Linker > Command Line and add  "..\lib\cmark.lib" to the options (see https://github.com/aseprite/aseprite/issues/1351)

c) Build the solution.