Building CEED for Windows - Revision history

Ident: /* Installing boost binaries */

2016-10-02T12:20:53Z

‎Installing boost binaries

2016-08-21T14:11:50Z

‎Installing Python

2015-11-09T21:21:14Z

‎Installing the prerequisites

2015-11-09T21:19:46Z

‎Installing the prerequisites

2015-04-03T11:44:16Z

2015-04-03T10:19:36Z

Undo revision 5657 by Ident (talk)

2015-04-03T10:18:59Z

2015-04-03T00:55:04Z

2015-04-02T23:47:19Z

2015-04-02T23:45:48Z

@@ Line 37: / Line 37: @@
 == Installing boost binaries ==
-* We also need to install boost. You can use an .exe file for this that will install the necessary binaries from this download page:
+* We also need to install boost. We recommend using version boost 1.55, later versions are known to cause issues. You can use an .exe file for this that will install the necessary binaries from this download page:
       http://sourceforge.net/projects/boost/files/boost-binaries/1.55.0-build2/
 (Be sure to get the version which matches the version of msvc you intend to build with. If use MSVC2008, then get the download with 'msvc-9.0' in the name, if you use MSVC2010 get the version with 'msvc-10.0' in the name, etc...)
 * Note : If you have multiple versions of MSVS on your machine, it is safe to install different versions of these boost distributions into the same root folder (e.g C:/boost_1_55_0/), as the *.h and *.hpp files are all identical, and the pre-compiled binary libs all get installed to sub-folders specific to different versions of msvc. (It is these folders and libs that we will be manually pointing cmake to in the next section.)
 == Configuring a PyCEGUI build with cmake ==

@@ Line 11: / Line 11: @@
 == Installing Python ==
-* Get Python 2.7.7 (32 bit version) for Windows  and install it:
+* Get Python 2.7.12 (32 bit version) for Windows  and install it:
       https://www.python.org/downloads/
 * Add your Python install folder path to the PATH variable in your Windows environment variables, e.g.: C:Projects\Python27
 * Now add the Scripts folder to the PATH environment variable, e.g.: C:\Projects\Python27\Scripts & C:\Projects\Python27\Tools\Scripts (depending on which of those folders exists in your install)
-* Open up a dos-command-prompt (cmd.exe) with admin rights and type "python" - See if you get something written into the console, such as "Python 2.7.6 (default [...]", if this is the case then the install worked.
+* Open up a dos-command-prompt (cmd.exe) with admin rights and type "python" - See if you get something written into the console, such as "Python 2.7.12 (default [...]", if this is the case then the install worked.
-−
 == Installing pip ==

@@ Line 8: / Line 8: @@
 == Installing the prerequisites ==
-When downloading/installing binaries, be sure to get the version which matches your version of visual studio, for instance choose the 32-bit and VC10 (visual studio 2010) versions of the binaries if that is what you are using to build. (or VC9 / VC11 / VC12 / ... if you are building with those.) If you use VC14 and not for example VC9 then be sure that the paths also match this. Don't get confused about the '''paths''' listed in this article, they are '''exemplatory''' and based on VC9. '''Do not mix VC9 binaries with VC10 or VC11, etc.'''
+When downloading/installing binaries, be sure to get the version which matches your version of visual studio, for instance choose the 32-bit and VC10 (visual studio 2010) versions of the binaries if that is what you are using to build. (or VC9 / VC11 / VC12 / ... if you are building with those.) If you use VC14 and not for example VC9 then be sure that the paths also match this. Don't get confused about the '''paths''' listed in this article, they are '''exemplatory''' and based on VC9. '''Do not mix VC9 binaries with VC10 or VC11, etc.''' We recommend using VC9 to build CEED because this one is assured to work.
 == Installing Python ==

@@ Line 8: / Line 8: @@
 == Installing the prerequisites ==
-When downloading/installing binaries, be sure to get the version which matches your version of visual studio, for instance choose the 32-bit and VC10 (visual studio 2010) versions of the binaries if that is what you are using to build. (or VC9 / VC11 / VC12 / ... if you are building with those.)
+When downloading/installing binaries, be sure to get the version which matches your version of visual studio, for instance choose the 32-bit and VC10 (visual studio 2010) versions of the binaries if that is what you are using to build. (or VC9 / VC11 / VC12 / ... if you are building with those.) If you use VC14 and not for example VC9 then be sure that the paths also match this. Don't get confused about the '''paths''' listed in this article, they are '''exemplatory''' and based on VC9. '''Do not mix VC9 binaries with VC10 or VC11, etc.'''
 == Installing Python ==

@@ Line 1: / Line 1: @@
 {{VersionBadge|0.8}}
-Test'''Written by Ident (Lukas Meindl) & Nickenstein79 (Working correctly as of 11th June, 2014)'''
+'''Written by Ident (Lukas Meindl) & Nickenstein79 (Working correctly as of 11th June, 2014)'''
 The following instructions need to be done in the presented order and are created for the currently available version of CEED and could therefore be outdated at some point. Please notify us if you think this is outdated.

← Older revision		Revision as of 00:55, 3 April 2015
Line 126:		Line 126:

	[[Using CEED-Migrate]]		[[Using CEED-Migrate]]
−	[[Category:HowTo~~]] [[Category:Tutorials~~]]	+	[[Category:HowTo]]

← Older revision		Revision as of 23:47, 2 April 2015
Line 126:		Line 126:

	[[Using CEED-Migrate]]		[[Using CEED-Migrate]]
−	[[Category:HowTo]]	+	[[Category:HowTo]] [[Category:Tutorials]]

← Older revision		Revision as of 23:45, 2 April 2015
Line 123:		Line 123:
	== Using Python-CEED-Migrate ==		== Using Python-CEED-Migrate ==
	You can also use the ceed-migrate tool for convert your old cegui-datafiles to the newer formats. See this page for some examples of the parameters ceed-migrate takes: [[Using CEED-Migrate]]		You can also use the ceed-migrate tool for convert your old cegui-datafiles to the newer formats. See this page for some examples of the parameters ceed-migrate takes: [[Using CEED-Migrate]]
		+
		+
		+	[[Using CEED-Migrate]]
		+	[[Category:HowTo]]