Building with Windows - Revision history

Luchs: new clone screenshot!

2018-05-13T17:13:25Z

new clone screenshot!

← Older revision		Revision as of 17:13, 13 May 2018
Line 39:		Line 39:
	[[File:build_windows_tgit6.png]]		[[File:build_windows_tgit6.png]]

	A dialog will appear asking for the repository URL and the destination path. In our case, we want the source to be the OpenClonk repository. The URL you need is normally "https://github.com/openclonk/openclonk". Here's how it should look like ~~(''note that the screenshot is showing an outdated URL'')~~:		A dialog will appear asking for the repository URL and the destination path. In our case, we want the source to be the OpenClonk repository. The URL you need is normally "https://github.com/openclonk/openclonk". Here's how it should look like:

	''OpenClonk team members:'' Use "git@github.com:openclonk/openclonk" instead and activate the option to auto-load the PuTTY key for maximum convenience.		''OpenClonk team members:'' Use "git@github.com:openclonk/openclonk" instead and activate the option to auto-load the PuTTY key for maximum convenience.

Luchs: Update links, replacing git.openclonk.org with github

2018-05-13T17:01:33Z

Update links, replacing git.openclonk.org with github

← Older revision		Revision as of 17:01, 13 May 2018
Line 39:		Line 39:
	[[File:build_windows_tgit6.png]]		[[File:build_windows_tgit6.png]]

	A dialog will appear asking for the repository URL and the destination path. In our case, we want the source to be the OpenClonk repository. The URL you need is normally "~~git~~://~~git~~.openclonk~~.org~~/openclonk~~.git~~". Here's how it should look like:		A dialog will appear asking for the repository URL and the destination path. In our case, we want the source to be the OpenClonk repository. The URL you need is normally "https://github.com/openclonk/openclonk". Here's how it should look like (''note that the screenshot is showing an outdated URL''):

	''OpenClonk team members:'' Use "~~ssh://~~git@~~git~~.openclonk~~.org~~/openclonk~~.git~~" instead and activate the option to auto-load the PuTTY key for maximum convenience.		''OpenClonk team members:'' Use "git@github.com:openclonk/openclonk" instead and activate the option to auto-load the PuTTY key for maximum convenience.

	[[File:build_windows_tgit_pub.png]]		[[File:build_windows_tgit_pub.png]]

PeterW: Image sizes

2015-10-04T19:06:14Z

Image sizes

← Older revision		Revision as of 19:06, 4 October 2015
Line 48:		Line 48:
	After pressing "OK", TortoiseGit will work for a while. After watching a progress bar for a while, it should finish. Congratulations, you now have the bleeding edge of OpenClonk development on your hard drive!		After pressing "OK", TortoiseGit will work for a while. After watching a progress bar for a while, it should finish. Congratulations, you now have the bleeding edge of OpenClonk development on your hard drive!

	[[File:build_windows_tgit_finish.png]]		[[File:build_windows_tgit_finish.png\|860px]]

	There is a lot of stuff and most likely you won't understand much of it. Here's a quick orientation guide of the actually important bits:		There is a lot of stuff and most likely you won't understand much of it. Here's a quick orientation guide of the actually important bits:
Line 113:		Line 113:
	Okay, now we have everything needed to make OpenClonk run for the first time. Go into the source directory and double-click on the "openclonk.sln" file that should now have appeared:		Okay, now we have everything needed to make OpenClonk run for the first time. Go into the source directory and double-click on the "openclonk.sln" file that should now have appeared:

	[[File:build_windows_build1.png]]		[[File:build_windows_build1.png\|860px]]


	Visual C++ should open and look similar to this:		Visual C++ should open and look similar to this:

	[[File:build_windows_build2.png]]		[[File:build_windows_build2.png\|860px]]

PeterW: Windows 10 / MSVC 2015 version

2015-10-04T19:04:53Z

Windows 10 / MSVC 2015 version

← Older revision		Revision as of 19:04, 4 October 2015
Line 3:		Line 3:
	= Get the sources =		= Get the sources =

	The source of OpenClonk is hold in a so-called version control system. Put simply, this is something that allows programmers to coordinate their work ~~(see~~ [[Git Workflow\|the Git article]] ~~for~~ how that works). For the moment, it's just a couple of files you want to download.		The source of OpenClonk is hold in a so-called version control system. Put simply, this is something that allows programmers to coordinate their work - if you want, you can afterwards read [[Git Workflow\|the Git article]] to see how that works. For the moment, it's just a couple of files you want to download.

	== Install TortoiseGit ==		== Install TortoiseGit ==

	The notable difference to a simple download is that you need a special program to do it. Our version control system is Git, and we will use the [~~http~~://~~code~~.~~google.com/p/tortoisegit~~/ TortoiseGit] client. Follow that link and click "Download".		The notable difference to a simple download is that you need a special program to do it. Our version control system is Git, and we will use the [https://tortoisegit.org/ TortoiseGit] client. Follow that link and click "Download".

	[[File:build_windows_tgit.png\|860px]]		[[File:build_windows_tgit.png\|860px]]

	As the ~~website tells you,~~ the ~~installation of TortoiseGit has two parts: TortoiseGit and msysGit~~. ~~It also says that~~ you ~~should start with TortoiseGit, so let us get that installer first. Make sure to choose~~ the ~~right architecture for your~~ version ~~of Windows~~:		Proceed to the "Download" page and select the appropriate installer. If unsure, you probably want the 64-bit version:

	[[File:build_windows_tgit2.png\|860px]]		[[File:build_windows_tgit2.png\|860px]]

	And walk through the installation. Just selecting the default options should get you through ~~alright~~.		And walk through the installation. Just selecting the default options should get you through.

	''OpenClonk team members:'' If you want to use [http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html PuTTY] to push commits, make sure to select the appropriate option along the way. Do it again for the msysGit installation below.		''OpenClonk team members:'' If you want to use [http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html PuTTY] to push commits, make sure to select the appropriate option along the way. Do it again for the msysGit installation below.
Line 21:		Line 21:
	[[File:build_windows_tgit4.png]]		[[File:build_windows_tgit4.png]]

	~~Next, you~~ need ~~msysGit~~, which is what actually does all the work behind the scenes. Following ~~the [http://code.google.com/p/msysgit/downloads/list?can=2&q=%22Full+installer+for+official+Git+for+Windows%22 "Full installer for official Git"]~~ link will get you to another download page:		You also need to install [https://git-for-windows.github.io/ Git for Windows], which is what actually does all the work behind the scenes. Following this link will get you to another download page:

	[[File:build_windows_tgit3.png\|860px]]		[[File:build_windows_tgit3.png\|860px]]
Line 33:		Line 33:
	== Clone ==		== Clone ==

	Okay, now we are going to download the sources. Git calls this "cloning" because it's actually a lot more than just the sources ~~you get~~. After you're done, you can check the [[Git Workflow]] page for how to work with your clone.		Okay, now we are going to download the sources. Git calls this "cloning" because it's actually a lot more than just the sources. After you're done, you can check the [[Git Workflow]] page for how to work with your clone.

	For now, just find a place where you want the source to be, open the context menu by right-click and select "Git Clone..." from the TortoiseGit menu:		For now, just find a place where you want the source to be, open the context menu by right-click and select "Git Clone..." from the TortoiseGit menu:

	[[File:build_windows_tgit6.png]]		[[File:build_windows_tgit6.png]]


	A dialog will appear asking for the repository URL and the destination path. In our case, we want the source to be the OpenClonk repository. The URL you need is normally "git://git.openclonk.org/openclonk.git". Here's how it should look like:		A dialog will appear asking for the repository URL and the destination path. In our case, we want the source to be the OpenClonk repository. The URL you need is normally "git://git.openclonk.org/openclonk.git". Here's how it should look like:
Line 47:		Line 46:


			After pressing "OK", TortoiseGit will work for a while. After watching a progress bar for a while, it should finish. Congratulations, you now have the bleeding edge of OpenClonk development on your hard drive!
	After pressing "OK", TortoiseGit will work for a while. After watching a ~~tortoise somersaulting~~ for a while, it should finish. Congratulations, you now have the bleeding edge of OpenClonk development on your hard drive!

	[[File:build_windows_tgit_finish.png]]		[[File:build_windows_tgit_finish.png]]

	~~This~~ a lot of stuff and most likely you won't understand much of it. Here's a quick orientation guide of the actually important bits:		There is a lot of stuff and most likely you won't understand much of it. Here's a quick orientation guide of the actually important bits:
	* "docs" - the sources of our [http://docs.openclonk.org/en/sdk/ documentation]		* "docs" - the sources of our [http://docs.openclonk.org/en/sdk/ documentation]
	* "planet" - these are the game resources - scripts, graphics and everything to explain how to make a game out of them		* "planet" - these are the game resources - scripts, graphics and everything to explain how to make a game out of them
Line 63:		Line 61:
	== Get Microsoft Visual Studio ==		== Get Microsoft Visual Studio ==

	You can say what you want about Microsoft, but they sure make nice development environments. And they are even giving a lot of it away for free. We will use [~~http~~://www.~~microsoft~~.com/~~visualstudio~~/~~eng/downloads#d~~-~~2012~~-~~express~~ Visual Studio ~~C++ 2012~~]. Follow that link, ~~find the 2012~~ Express ~~Edition '''~~for ~~Windows~~ Desktop~~''', then download the [http://go.microsoft.com/?linkid=9816758 web installer]~~:		You can say what you want about Microsoft, but they sure make nice development environments. And they are even giving a lot of it away for free. We will use [https://www.visualstudio.com/downloads/download-visual-studio-vs# Visual Studio 2015 Express for Desktop]. Follow that link, then click on "Visual Studio 2015" and "Express 2015 for Desktop":

	~~[[File:msvc11_web_download.png\|860px\|Make extra sure you got the "Windows Desktop" variant.]]~~

	~~Run it, accept the licensing terms, click~~ the ~~big "Install~~" ~~link and accept the UAC prompt~~.		[[File:Build_windows_msvc2015.png\|860px\|Make extra sure you got the "Express 2015 for Desktop.]]

	Then go make a coffee because the install will probably take a while~~. If the setup asks you to restart your computer, do so; it will continue when you log back in~~.		Run it, accept the licensing terms, click the big "Install" link and accept the UAC prompt. Then go make a coffee because the install will probably take a while.

	== Get Dependencies ==		== Get Dependencies ==
Line 75:		Line 72:
	Like most big programs, OpenClonk doesn't stand on its own. Some things (like opening PNG images) were already programmed by other programers far better than we could ever do. This is why we have to get a few so-called "libraries" before Clonk can be built.		Like most big programs, OpenClonk doesn't stand on its own. Some things (like opening PNG images) were already programmed by other programers far better than we could ever do. This is why we have to get a few so-called "libraries" before Clonk can be built.

	You could expend some effort try to find, download, and compile all those libraries by yourself, but that would take quite some time. Instead, just download one of the packages we've provided for your convenience. If you~~'re trying to build~~ a ~~32-bit binary~~ of ~~OpenClonk or~~ you ~~don't really know what this is all about~~, use [~~http~~://www.nosebud.de/~nh/openclonk/openclonk-deps-~~vc110~~-i386.~~zip the~~ x86 ~~package~~]~~; for a 64-bit binary, use~~ [~~http~~://www.nosebud.de/~nh/openclonk/openclonk-deps-~~vc110~~-amd64.~~zip the~~ amd64 ~~package~~]~~. Then unpack the .zip archive and put the "deps" folder into the directory where you also want your build files~~.		You could expend some effort try to find, download, and compile all those libraries by yourself, but that would take quite some time. Instead, just download one of the packages we've provided for your convenience:

			* [http://people.ds.cam.ac.uk/pw410/out/openclonk-deps-vs140-i386-easy.7z the x86 package] (we'll assume this one)
			* [http://people.ds.cam.ac.uk/pw410/out/openclonk-deps-vs140-amd64-easy2.7z the amd64 package]

			These packages are made for unpacking directly into the "openclonk" folder you created above, which will put a couple of DLL files into the root and create a "deps" folder. If you would like to organise the dependencies yourself, use the original dependency files provided by Isilkor ([https://www.nosebud.de/~nh/openclonk/openclonk-deps-vs140-i386.7z x86] and [https://www.nosebud.de/~nh/openclonk/openclonk-deps-vs140-amd64.7z amd64]).

	== Get CMake ==		== Get CMake ==
Line 99:		Line 101:


	Now click the "Configure" button in the lower left. It will ask what compiler we want to use. Select the compiler you want to use; either "Visual Studio 11" if you downloaded the 32-bit library package above, or "Visual Studio 11 Win64" if you got the 64-bit package.		Now click the "Configure" button in the lower left. It will ask what compiler we want to use. Select the compiler you want to use; either "Visual Studio 14 2015" if you downloaded the x86-bit library package above, or "Visual Studio 14 2015 Win64" if you got the amd64-bit package.

	[[File:build_windows_cmake4.png]]		[[File:build_windows_cmake4.png]]

Armin: /* Your First Build */

2014-10-19T12:26:00Z

Your First Build

← Older revision		Revision as of 12:26, 19 October 2014
Line 119:		Line 119:


	We only want to build the engine, so select "openclonk" from the list, right-click and select "Set as Start-Up project"		We only want to build the engine, so select "openclonk" from the list, right-click and select "Set as Start-Up project".

	[[File:build_windows_build3.png]]		[[File:build_windows_build3.png]]

Andriel: /* Get CMake */

2014-04-19T09:50:51Z

Get CMake

← Older revision		Revision as of 09:50, 19 April 2014
Line 94:		Line 94:

	After the installation, start the CMake GUI from the start menu. Put the path you cloned the repository into the source code path field.		After the installation, start the CMake GUI from the start menu. Put the path you cloned the repository into the source code path field.
			You can set the build path to any directory you want, but it is important that the "deps" folder from the last step is also in that directory.

	[[File:build_windows_cmake3.png]]		[[File:build_windows_cmake3.png]]

Andriel: /* Get Dependencies */

2014-04-19T09:48:10Z

Get Dependencies

← Older revision		Revision as of 09:48, 19 April 2014
Line 75:		Line 75:
	Like most big programs, OpenClonk doesn't stand on its own. Some things (like opening PNG images) were already programmed by other programers far better than we could ever do. This is why we have to get a few so-called "libraries" before Clonk can be built.		Like most big programs, OpenClonk doesn't stand on its own. Some things (like opening PNG images) were already programmed by other programers far better than we could ever do. This is why we have to get a few so-called "libraries" before Clonk can be built.

	You could expend some effort try to find, download, and compile all those libraries by yourself, but that would take quite some time. Instead, just download one of the packages we've provided for your convenience. If you're trying to build a 32-bit binary of OpenClonk or you don't really know what this is all about, use [http://www.nosebud.de/~nh/openclonk/openclonk-deps-vc110-i386.zip the x86 package]; for a 64-bit binary, use [http://www.nosebud.de/~nh/openclonk/openclonk-deps-vc110-amd64.zip the amd64 package]. Then unpack ~~its contents into~~ the ~~same directory you~~ put ~~all the other files (but keep~~ the "deps" folder ~~intact)~~.		You could expend some effort try to find, download, and compile all those libraries by yourself, but that would take quite some time. Instead, just download one of the packages we've provided for your convenience. If you're trying to build a 32-bit binary of OpenClonk or you don't really know what this is all about, use [http://www.nosebud.de/~nh/openclonk/openclonk-deps-vc110-i386.zip the x86 package]; for a 64-bit binary, use [http://www.nosebud.de/~nh/openclonk/openclonk-deps-vc110-amd64.zip the amd64 package]. Then unpack the .zip archive and put the "deps" folder into the directory where you also want your build files.

	== Get CMake ==		== Get CMake ==

Newton at 21:37, 30 April 2013

2013-04-30T21:37:02Z

← Older revision		Revision as of 21:37, 30 April 2013
Line 1:		Line 1:
			[[DE:Kompilieren unter Windows\|German Version here]]

	= Get the sources =		= Get the sources =

Isilkor: /* Get Dependencies */ How about I get the URLs right this time?

2013-03-31T22:11:31Z

Get Dependencies: How about I get the URLs right this time?

← Older revision		Revision as of 22:11, 31 March 2013
Line 73:		Line 73:
	Like most big programs, OpenClonk doesn't stand on its own. Some things (like opening PNG images) were already programmed by other programers far better than we could ever do. This is why we have to get a few so-called "libraries" before Clonk can be built.		Like most big programs, OpenClonk doesn't stand on its own. Some things (like opening PNG images) were already programmed by other programers far better than we could ever do. This is why we have to get a few so-called "libraries" before Clonk can be built.

	You could expend some effort try to find, download, and compile all those libraries by yourself, but that would take quite some time. Instead, just download one of the packages we've provided for your convenience. If you're trying to build a 32-bit binary of OpenClonk or you don't really know what this is all about, use [http://www.nosebud.de/~nh/openclonk-deps-vc110-i386.zip the x86 package]; for a 64-bit binary, use [http://www.nosebud.de/~nh/openclonk-deps-vc110-amd64.zip the amd64 package]. Then unpack its contents into the same directory you put all the other files (but keep the "deps" folder intact).		You could expend some effort try to find, download, and compile all those libraries by yourself, but that would take quite some time. Instead, just download one of the packages we've provided for your convenience. If you're trying to build a 32-bit binary of OpenClonk or you don't really know what this is all about, use [http://www.nosebud.de/~nh/openclonk/openclonk-deps-vc110-i386.zip the x86 package]; for a 64-bit binary, use [http://www.nosebud.de/~nh/openclonk/openclonk-deps-vc110-amd64.zip the amd64 package]. Then unpack its contents into the same directory you put all the other files (but keep the "deps" folder intact).

	== Get CMake ==		== Get CMake ==

Isilkor: /* Get Dependencies */ Update packages for VS2012

2013-03-31T21:48:10Z

Get Dependencies: Update packages for VS2012

← Older revision		Revision as of 21:48, 31 March 2013
Line 73:		Line 73:
	Like most big programs, OpenClonk doesn't stand on its own. Some things (like opening PNG images) were already programmed by other programers far better than we could ever do. This is why we have to get a few so-called "libraries" before Clonk can be built.		Like most big programs, OpenClonk doesn't stand on its own. Some things (like opening PNG images) were already programmed by other programers far better than we could ever do. This is why we have to get a few so-called "libraries" before Clonk can be built.

	You could try to ~~search~~ and ~~download~~ all those libraries by ~~hand~~, but that would ~~be pretty boring~~. Instead, just download [http://www.~~openclonk~~.~~org~~/openclonk-deps-~~vc90~~.zip ~~this~~ package] ~~that contains everything you need to build Clonk.~~		You could expend some effort try to find, download, and compile all those libraries by yourself, but that would take quite some time. Instead, just download one of the packages we've provided for your convenience. If you're trying to build a 32-bit binary of OpenClonk or you don't really know what this is all about, use [http://www.nosebud.de/~nh/openclonk-deps-vc110-i386.zip the x86 package]; for a 64-bit binary, use [http://www.nosebud.de/~nh/openclonk-deps-vc110-amd64.zip the amd64 package]. Then unpack its contents into the same directory you put all the other files (but keep the "deps" folder intact).

	[~~[File~~:~~build_windows_deps~~.~~png~~]]


	~~Unpack both directories~~ into the same ~~path~~ you put all the other files~~. Don't worry, nothing will get overwritten in~~ "~~planet~~".

	== Get CMake ==		== Get CMake ==