OpenMW Windows Development Environment Setup - Appveyor scripts

gistfile1.md

NB; (An updated version of this guide can be found on the wiki)

OpenMW Windows Dev-Env

What you need?

• Visual Studio 2013 or 2015 (Community edition is enough)
• MSYSGit or Git for Windows as it's also called (cinst git.install if you have Chocolatey)
• Note that WSL does not work for this, as it needs to execute windows executables.
• 7-zip in your path (cinst 7zip.install works, if you have Chocolatey)
• CMake in your path (cinst cmake.install for Chocolatey)
• ~10GB of free space per build platform (32/64-bit), for all the build artefacts.
• Time. An hour or two most likely for full release and debug builds.

What you do?

• Clone the OpenMW repo. git://github.com/OpenMW/openmw.git
• Open a Git Bash shell in the repo.
• Run the following command: CI/before_script.msvc.sh -k -p Win64 -v 2015. (Substitute Win64 with Win32 if doing a 32-bit build, 2015 can also be substituted with 2013 for VS2013)
• Wait for the build environment to be set up.
• ???
• Develop.

@R1ZR: Do you have spaces in your path? If so, that's probably why. Either change your paths, or go through the script and quote things. I'd suggest you use a simple, short path with no spaces (e.g. C:\Projects\openmw).

when this creates a project, just looking at the cs project, it loses its organization (folders), and just dumps everything under Source Files , the project name folder, i.e. openmw-cs.

An updated version of this guide is available at https://wiki.openmw.org/index.php?title=Development_Environment_Setup#Visual_Studio_2013.2F2015.2F2017_scripted_way

Among other things:

• It tells you not to do some things that break the script that these instructions don't mention.
• It explains some things that were vague or absent in this guide, such as how to get configurations other than Debug working.