Windows Development - Revision history

Goose: /* Satisfying Dependencies */ Wrong way around.

2026-06-27T16:03:55Z

Satisfying Dependencies: Wrong way around.

← Older revision		Revision as of 12:03, 27 June 2026
Line 26:		Line 26:
	== Satisfying Dependencies ==		== Satisfying Dependencies ==

	Satisfying dependencies in Windows is very easy. You just download the most recent release of the [[winlibs.zip file~~\|Winlibs Collection~~]] to build the trunk, generally. Sometimes that won't work, such as when the trunk requires new libraries that aren't required by the most recent release. If you're building from the 0.4/master, you'll want to checkout the winlibs module from BZR to go along with the current sources.		Satisfying dependencies in Windows is very easy. You just download the most recent release of the [[Winlibs Collection\|winlibs.zip file]] to build the trunk, generally. Sometimes that won't work, such as when the trunk requires new libraries that aren't required by the most recent release. If you're building from the 0.4/master, you'll want to checkout the winlibs module from BZR to go along with the current sources.

	This is early to talk about checking out the source, but it's needed. The directory structure you need looks like this:		This is early to talk about checking out the source, but it's needed. The directory structure you need looks like this:

Goose: /* Satisfying Dependencies */ Added a link.

2026-06-27T16:03:26Z

Satisfying Dependencies: Added a link.

← Older revision		Revision as of 12:03, 27 June 2026
Line 26:		Line 26:
	== Satisfying Dependencies ==		== Satisfying Dependencies ==

	Satisfying dependencies in Windows is very easy. You just download the most recent release of the winlibs.zip file to build the trunk, generally. Sometimes that won't work, such as when the trunk requires new libraries that aren't required by the most recent release. If you're building from the 0.4/master, you'll want to checkout the winlibs module from BZR to go along with the current sources.		Satisfying dependencies in Windows is very easy. You just download the most recent release of the [[winlibs.zip file\|Winlibs Collection]] to build the trunk, generally. Sometimes that won't work, such as when the trunk requires new libraries that aren't required by the most recent release. If you're building from the 0.4/master, you'll want to checkout the winlibs module from BZR to go along with the current sources.

	This is early to talk about checking out the source, but it's needed. The directory structure you need looks like this:		This is early to talk about checking out the source, but it's needed. The directory structure you need looks like this:

Cadillac at 18:19, 24 August 2021

2021-08-24T18:19:13Z

← Older revision		Revision as of 14:19, 24 August 2021
Line 90:		Line 90:

	These video tutorials are provided by [http://wiki.armagetronad.org/index.php/User:LOVER$BOY LOVER$BOY]		These video tutorials are provided by [http://wiki.armagetronad.org/index.php/User:LOVER$BOY LOVER$BOY]

			[[Category:Development]]

Armanelgtron: /* Satisfying Dependencies */ Setting to the more up-to-date non "-work" paths.

2020-05-03T04:38:42Z

Satisfying Dependencies: Setting to the more up-to-date non "-work" paths.

← Older revision		Revision as of 00:38, 3 May 2020
Line 37:		Line 37:

	*armagetronad		*armagetronad
	**bzr: https://code.launchpad.net/~armagetronad-dev/armagetronad/0.4-armagetronad~~-work~~		**bzr: https://code.launchpad.net/~armagetronad-dev/armagetronad/0.4-armagetronad
	**git: https://gitlab.com/armagetronad/armagetronad.git		**git: https://gitlab.com/armagetronad/armagetronad.git
	*winlibs		*winlibs
	**bzr: https://code.launchpad.net/~armagetronad-dev/armagetronad/0.4-winlibs~~-work~~		**bzr: https://code.launchpad.net/~armagetronad-dev/armagetronad/0.4-winlibs
	**git: https://gitlab.com/armagetronad/winlibs.git		**git: https://gitlab.com/armagetronad/winlibs.git

Armanelgtron at 04:35, 3 May 2020

2020-05-03T04:35:42Z

← Older revision		Revision as of 00:35, 3 May 2020
Line 22:		Line 22:
	** [http://bazaar.canonical.com/ bazaar]. The Tortiose-BZR shell extension can be selected as a GUI in the installer (recomended)		** [http://bazaar.canonical.com/ bazaar]. The Tortiose-BZR shell extension can be selected as a GUI in the installer (recomended)
	** (Outdated, for archive access only) [http://subversion.apache.org/ Subversion] client. [http://tortoisesvn.net/ Tortoise-SVN] gives you a nice GUI around SVN, but is considered optional. Note however that svn support on the trunk is on its way out and you should rather pick git for that.		** (Outdated, for archive access only) [http://subversion.apache.org/ Subversion] client. [http://tortoisesvn.net/ Tortoise-SVN] gives you a nice GUI around SVN, but is considered optional. Note however that svn support on the trunk is on its way out and you should rather pick git for that.
	* Old entry: "You'll need gcc, bison, and swig, at the very least to build the trunk. A release tarball may not need bison and swig." Z-Man can't remember installing bison, gcc is part of mingw which comes with code::blocks, and swig is not currently needed. So feel free to ignore this.		* Old entry: <strike>"You'll need gcc, bison, and swig, at the very least to build the trunk. A release tarball may not need bison and swig."</strike> Z-Man can't remember installing bison, gcc is part of mingw which comes with code::blocks, and swig is not currently needed. So feel free to ignore this.

	== Satisfying Dependencies ==		== Satisfying Dependencies ==

Z-man: /* Satisfying Dependencies */

2019-09-29T19:05:46Z

Satisfying Dependencies

← Older revision		Revision as of 15:05, 29 September 2019
Line 26:		Line 26:
	== Satisfying Dependencies ==		== Satisfying Dependencies ==

	Satisfying dependencies in Windows is very easy. You just download the most recent release of the winlibs.zip file to build the trunk, generally. Sometimes that won't work, such as when the trunk requires new libraries that aren't required by the most recent release. If you're building from the 0.4, you'll want to checkout the winlibs module from BZR to go along with the current sources.		Satisfying dependencies in Windows is very easy. You just download the most recent release of the winlibs.zip file to build the trunk, generally. Sometimes that won't work, such as when the trunk requires new libraries that aren't required by the most recent release. If you're building from the 0.4/master, you'll want to checkout the winlibs module from BZR to go along with the current sources.

	This is early to talk about checking out the source, but it's needed. The directory structure you need looks like this:		This is early to talk about checking out the source, but it's needed. The directory structure you need looks like this:
Line 38:		Line 38:
	*armagetronad		*armagetronad
	**bzr: https://code.launchpad.net/~armagetronad-dev/armagetronad/0.4-armagetronad-work		**bzr: https://code.launchpad.net/~armagetronad-dev/armagetronad/0.4-armagetronad-work
			**git: https://gitlab.com/armagetronad/armagetronad.git
	*winlibs		*winlibs
	**bzr: https://code.launchpad.net/~armagetronad-dev/armagetronad/0.4-winlibs-work		**bzr: https://code.launchpad.net/~armagetronad-dev/armagetronad/0.4-winlibs-work
			**git: https://gitlab.com/armagetronad/winlibs.git

	You will need to rename 0.4-winlibs-work to winlibs if you get it over bzr.		You will need to rename 0.4-winlibs-work to winlibs if you get it over bzr.

	All that only works when someone actually cares about the Windows build process enough to keep it running. Most developers work on Unix ~~or the Mac.~~		All that only works when someone actually cares about the Windows build process enough to keep it running. Most developers work on Unix.

	~~If you want trunk builds (much less likely to work), replace "0.4" with "trunk" in the above~~.

	== Building Armagetron Advanced ==		== Building Armagetron Advanced ==

Z-man: /* Installing the IDE */

2019-09-29T08:49:24Z

Installing the IDE

← Older revision		Revision as of 04:49, 29 September 2019
Line 21:		Line 21:
	** [https://git-scm.com/download/win git].		** [https://git-scm.com/download/win git].
	** [http://bazaar.canonical.com/ bazaar]. The Tortiose-BZR shell extension can be selected as a GUI in the installer (recomended)		** [http://bazaar.canonical.com/ bazaar]. The Tortiose-BZR shell extension can be selected as a GUI in the installer (recomended)
	** (Outdated, for archive access only) [http://subversion.apache.org/ Subversion] client. [http://tortoisesvn.net/ Tortoise-SVN] gives you a nice GUI around SVN, but is considered optional. Note however that svn support on the trunk is on its way out and you should rather pick		** (Outdated, for archive access only) [http://subversion.apache.org/ Subversion] client. [http://tortoisesvn.net/ Tortoise-SVN] gives you a nice GUI around SVN, but is considered optional. Note however that svn support on the trunk is on its way out and you should rather pick git for that.
	* Old entry: "You'll need gcc, bison, and swig, at the very least to build the trunk. A release tarball may not need bison and swig." Z-Man can't remember installing bison, gcc is part of mingw which comes with code::blocks, and swig is not currently needed. So feel free to ignore this.		* Old entry: "You'll need gcc, bison, and swig, at the very least to build the trunk. A release tarball may not need bison and swig." Z-Man can't remember installing bison, gcc is part of mingw which comes with code::blocks, and swig is not currently needed. So feel free to ignore this.

Z-man: /* Installing the IDE */

2019-09-28T20:49:25Z

Installing the IDE

← Older revision		Revision as of 16:49, 28 September 2019
Line 19:		Line 19:
	* [http://nsis.sourceforge.net/Download NSIS] is needed to build installers.		* [http://nsis.sourceforge.net/Download NSIS] is needed to build installers.
	* If you don't want to be restricted to building released, zipped sources, a way to fetch our current source. Two choices:		* If you don't want to be restricted to building released, zipped sources, a way to fetch our current source. Two choices:
	** [http://subversion.apache.org/ Subversion] client. [http://tortoisesvn.net/ Tortoise-SVN] gives you a nice GUI around SVN, but is considered optional. Note however that svn support on the trunk is on its way out and you should rather pick		** [https://git-scm.com/download/win git].
	** [http://bazaar.canonical.com/ bazaar]. Again, [http://wiki.bazaar.canonical.com/TortoiseBzr Tortiose-BZR] is a GUI you can use.		** [http://bazaar.canonical.com/ bazaar]. The Tortiose-BZR shell extension can be selected as a GUI in the installer (recomended)
			** (Outdated, for archive access only) [http://subversion.apache.org/ Subversion] client. [http://tortoisesvn.net/ Tortoise-SVN] gives you a nice GUI around SVN, but is considered optional. Note however that svn support on the trunk is on its way out and you should rather pick
	* Old entry: "You'll need gcc, bison, and swig, at the very least to build the trunk. A release tarball may not need bison and swig." Z-Man can't remember installing bison, gcc is part of mingw which comes with code::blocks, and swig is not currently needed. So feel free to ignore this.		* Old entry: "You'll need gcc, bison, and swig, at the very least to build the trunk. A release tarball may not need bison and swig." Z-Man can't remember installing bison, gcc is part of mingw which comes with code::blocks, and swig is not currently needed. So feel free to ignore this.

Z-man: /* Installing the IDE */

2017-02-10T05:22:47Z

Installing the IDE

← Older revision		Revision as of 01:22, 10 February 2017
Line 7:		Line 7:
	We use Code::Blocks. The trunk, 0.4 and 0.2.8 branches should be built with [http://www.codeblocks.org/downloads/26 13.12].		We use Code::Blocks. The trunk, 0.4 and 0.2.8 branches should be built with [http://www.codeblocks.org/downloads/26 13.12].

	Pre-sdl2 versions of 0.4 and used [http://sourceforge.net/projects/codeblocks/files/Binaries/10.05/Windows/ 10.05]).		(Pre-sdl2 versions of 0.4 and older 0.2.8 used [http://sourceforge.net/projects/codeblocks/files/Binaries/10.05/Windows/ 10.05]).

	0.2.8.3 and 0.2.8 builds before 2016/11/15 are done with the ancient 1.0RC2; The original instructions can be found [[Windows_Development_System#IDEs_.28You_need_only_one.29\|here]].		0.2.8.3 and 0.2.8 builds before 2016/11/15 are done with the ancient 1.0RC2; The original instructions can be found [[Windows_Development_System#IDEs_.28You_need_only_one.29\|here]].

Z-man: Updated version information to current state

2016-11-16T22:32:29Z

Updated version information to current state

← Older revision		Revision as of 18:32, 16 November 2016
Line 5:		Line 5:
	== Installing the IDE ==		== Installing the IDE ==

	We use Code::Blocks. The trunk and 0.4 should be built with ~~the latest available version (currently~~ [http://www.codeblocks.org/downloads/26 13.12]~~, probably best to stick to that one. Pre-sdl2 versions used [http://sourceforge.net/projects/codeblocks/files/Binaries/10.05/Windows/ 10.05])~~.		We use Code::Blocks. The trunk, 0.4 and 0.2.8 branches should be built with [http://www.codeblocks.org/downloads/26 13.12].

	0.2.8 builds are done with the ancient 1.0RC2; The original instructions can be found [[Windows_Development_System#IDEs_.28You_need_only_one.29\|here]].		Pre-sdl2 versions of 0.4 and used [http://sourceforge.net/projects/codeblocks/files/Binaries/10.05/Windows/ 10.05]).

			0.2.8.3 and 0.2.8 builds before 2016/11/15 are done with the ancient 1.0RC2; The original instructions can be found [[Windows_Development_System#IDEs_.28You_need_only_one.29\|here]].

			0.2.8 versions typically can also be built with later versions of Code::Blocks, but for 0.4, winlibs contains binary C++ library files built against a specific version of mingw and are typically incompatible with any other mingw (and therefore Code::Blocks) version.

	To build and run the game, you will need Python and Code::Blocks. Code::Blocks itself requires MingW, and additional tools available from MingW will be needed to build the trunk. Here's a list, in no particular order.		To build and run the game, you will need Python and Code::Blocks. Code::Blocks itself requires MingW, and additional tools available from MingW will be needed to build the trunk. Here's a list, in no particular order.