Maybe use WAF build system?

[forcecore]

• https://pypi.python.org/pypi/waftools
  Windows support would be hard implement using current Makefile and script system. I tried Babun to run them but it wasn't that simple. Since the SDK is meant to "build" things in order, I think we need a customizable build system that runs on both Windows and Linux to reduce the effort to keeping two build systems. I think WAF might be one candidate.

• It lets you use all the Python stuff, including os.path.exists(), ZIP archiving, os.system()

• It is a build framework that knows how to build things in dependency order.

• Installable on Windows (they say, haven't tried it yet)

• Supports invocation of another WAF build script, unifying packaging/package-all.sh, make.cmd, Makefile.

The down side is that WAF isn't popular on Linux and doesn't come by default. But mod Devs should be able to go through the installation!

[pchote]

Our recommended and preferred solution for generating installers will be to have Travis-CI automatically generate installers when a git tag is pushed to GitHub (#12). If people want to run the packaging scripts manually on Windows, then they have the option to use the Windows subsystem for Linux to run the standard scripts.

It looks like WAF only supports generating windows installers via NSIS, but doesn't provide any of the support that we will need to properly package dmg's for macOS, deb's for Ubuntu, or other Linux packages. It's never going to be viable to run those from Windows, and it would hurt our goal of making mods more accessible for players if we gave modders a simple solution that only generated installers for Windows.

[forcecore]

Maybe docker is the way to go hmmm