Installation - Revision history

Gongminmin at 05:22, 4 January 2017

2017-01-04T05:22:33Z

Gongminmin at 05:57, 25 December 2016

2016-12-25T05:57:11Z

Gongminmin at 01:33, 12 September 2016

2016-09-12T01:33:03Z

Gongminmin at 00:56, 12 September 2016

2016-09-12T00:56:18Z

Gongminmin at 04:50, 21 April 2015

2015-04-21T04:50:39Z

Gongminmin at 07:48, 21 July 2014

2014-07-21T07:48:54Z

Gongminmin at 09:04, 28 June 2014

2014-06-28T09:04:07Z

Gongminmin at 07:35, 1 December 2013

2013-12-01T07:35:12Z

Gongminmin at 06:05, 19 November 2013

2013-11-19T06:05:24Z

Gongminmin at 10:24, 13 November 2013

2013-11-13T10:24:08Z

@@ Line 33: / Line 33: @@
 Wine must be installed on OSX, too.
   brew cask install xquartz
-  brew install wine
+  brew install wine --without-win64
- brew install winetricks
-−
-Then run winetricks.
- winetricks
 == See Also ==

@@ Line 1: / Line 1: @@
 == General ==
-Before compiling [[KlayGE/en|KlayGE]], Python 2.7+ and CMake 2.8.6+ must be installed first. Then you can run build_external.py to build and install [[Third-party libraries and tools|third-party libraries and tools]]. [[KlayGE/en|KlayGE]] has been tested on these [[Compilers tested|compilers]].
+Before compiling [[KlayGE/en|KlayGE]], Python 2.7+ and CMake 3.4+ must be installed first. Then you can run build_external.py to build and install [[Third-party libraries and tools|third-party libraries and tools]]. [[KlayGE/en|KlayGE]] has been tested on these [[Compilers tested|compilers]].
 Since [[KlayGE/en|KlayGE]] 3.12.0, include and lib paths are set up inside the project files. After extraction, just open the corresponding project file under "Build" directory, [[KlayGE/en|KlayGE]] itself can be built directly. Or you can run build_all.py to do that job.

@@ Line 34: / Line 34: @@
   brew cask install xquartz
   brew install wine
 Then run winetricks.

@@ Line 27: / Line 27: @@
 == OSX platform ==
 Wine must be installed on OSX, too.
   brew install wine

@@ Line 1: / Line 1: @@
 Before compiling [[KlayGE/en|KlayGE]], Python 2.7+ and CMake 2.8.6+ must be installed first. Then you can run build_external.py to build and install [[Third-party libraries and tools|third-party libraries and tools]]. [[KlayGE/en|KlayGE]] has been tested on these [[Compilers tested|compilers]].
@@ Line 7: / Line 9: @@
 Since [[KlayGE]] 4.4.0, 3rd party libraries uses cmake as project files. You only need to run build_external.py to finish the build, not native project files provided by 3rd party libraries themselves.
-Sincd [[KlayGE]] 4.5.0, Android and WinRT version can be build with the same cmake, too. Before that, you need a Windows version of tools. They are used in the process of building Android and WinRT version.
+Since [[KlayGE]] 4.5.0, Android and WinRT version can be build with the same cmake, too. Before that, you need a Windows version of tools. They are used in the process of building Android and WinRT version.
 During the compilation, if the vc said couldn't find v110_xp toolset, please install Visual Studio 2012 Update or up.
@@ Line 14: / Line 16: @@
 There are some incompatibilities between new versions of the Windows SDK/DirectX SDK and MinGW. When compiling the DirectSound plug-in, and the compiler will report sal.h cannot be found. VC's "sal.h" needs to be copied to "MinGW/include". Then open "MinGW/lib/gcc/mingw32/4.4.1/include/stddef.h", replace "#define NULL __null" by "#define NULL 0". Otherwise, sal.h will define __null to some other token incorrectly.
 == See Also ==

@@ Line 14: / Line 14: @@
 There are some incompatibilities between new versions of the Windows SDK/DirectX SDK and MinGW. When compiling the DirectSound plug-in, and the compiler will report sal.h cannot be found. VC's "sal.h" needs to be copied to "MinGW/include". Then open "MinGW/lib/gcc/mingw32/4.4.1/include/stddef.h", replace "#define NULL __null" by "#define NULL 0". Otherwise, sal.h will define __null to some other token incorrectly.
 [[zh:安装]]
 [[ru:Установка]]

← Older revision		Revision as of 09:04, 28 June 2014
Line 4:		Line 4:

	Since [[KlayGE]] 4.1.0, project files are migrated to cmake. Several on-stop compiling scripts written in Python is also included. The build_glloader.py is used for compiling [[glloader/en\|glloader]]; the build_kfont.py for [[kfont/en\|kfont]]; the build_KlayGE.py for [[KlayGE/en\|KlayGE]], [[Samples]], [[Toolset\|Tools]] and [[Tutorials]]. The build_all.py can build all of them. Those .py have two optional parameters. The first one is compiler name, the second one is configuration name. For example, "build_all.py vc10 x64" means uses vc10's x64 configuration for compiling. Currently, compiler names such as vc8, vc9, vc10, vc11, vc12, mingw and gcc are supported. Configuration names such as x86, x64, x86_app, and arm_app are supported. If no parameter in the command line, default parameters inside cfg_build.py will be used.		Since [[KlayGE]] 4.1.0, project files are migrated to cmake. Several on-stop compiling scripts written in Python is also included. The build_glloader.py is used for compiling [[glloader/en\|glloader]]; the build_kfont.py for [[kfont/en\|kfont]]; the build_KlayGE.py for [[KlayGE/en\|KlayGE]], [[Samples]], [[Toolset\|Tools]] and [[Tutorials]]. The build_all.py can build all of them. Those .py have two optional parameters. The first one is compiler name, the second one is configuration name. For example, "build_all.py vc10 x64" means uses vc10's x64 configuration for compiling. Currently, compiler names such as vc8, vc9, vc10, vc11, vc12, mingw and gcc are supported. Configuration names such as x86, x64, x86_app, and arm_app are supported. If no parameter in the command line, default parameters inside cfg_build.py will be used.
		+
		+	Since [[KlayGE]] 4.4.0, 3rd party libraries uses cmake as project files. You only need to run build_external.py to finish the build, not native project files provided by 3rd party libraries themselves.
		+
		+	Sincd [[KlayGE]] 4.5.0, Android and WinRT version can be build with the same cmake, too. Before that, you need a Windows version of tools. They are used in the process of building Android and WinRT version.

	During the compilation, if the vc said couldn't find v110_xp toolset, please install Visual Studio 2012 Update or up.		During the compilation, if the vc said couldn't find v110_xp toolset, please install Visual Studio 2012 Update or up.

@@ Line 3: / Line 3: @@
 Since [[KlayGE/en|KlayGE]] 3.12.0, include and lib paths are set up inside the project files. After extraction, just open the corresponding project file under "Build" directory, [[KlayGE/en|KlayGE]] itself can be built directly. Or you can run build_all.py to do that job.
-Since [[KlayGE]] 4.1.0, project files are migrated to cmake. Several on-stop compiling scripts written in Python is also included. The build_glloader.py is used for compiling [[glloader/en|glloader]]; the build_kfont.py for [[kfont/en|kfont]]; the build_KlayGE.py for [[KlayGE/en|KlayGE]], [[Samples]], [[Tools]] and [[Tutorials]]. The build_all.py can build all of them. Those .py have two optional parameters. The first one is compiler name, the second one is configuration name. For example, "build_all.py vc10 x64" means uses vc10's x64 configuration for compiling. Currently, compiler names such as vc8, vc9, vc10, vc11, vc12, mingw and gcc are supported. Configuration names such as x86, x64, x86_app, and arm_app are supported. If no parameter in the command line, default parameters inside cfg_build.py will be used.
+Since [[KlayGE]] 4.1.0, project files are migrated to cmake. Several on-stop compiling scripts written in Python is also included. The build_glloader.py is used for compiling [[glloader/en|glloader]]; the build_kfont.py for [[kfont/en|kfont]]; the build_KlayGE.py for [[KlayGE/en|KlayGE]], [[Samples]], [[Toolset|Tools]] and [[Tutorials]]. The build_all.py can build all of them. Those .py have two optional parameters. The first one is compiler name, the second one is configuration name. For example, "build_all.py vc10 x64" means uses vc10's x64 configuration for compiling. Currently, compiler names such as vc8, vc9, vc10, vc11, vc12, mingw and gcc are supported. Configuration names such as x86, x64, x86_app, and arm_app are supported. If no parameter in the command line, default parameters inside cfg_build.py will be used.
 During the compilation, if the vc said couldn't find v110_xp toolset, please install Visual Studio 2012 Update or up.

@@ Line 1: / Line 1: @@
-Before compiling [[KlayGE]], Python 2.7+ and CMake 2.8.6+ must be installed first. Then you can run build_external.py to build and install [[Third-party libraries and tools|third-party libraries and tools]]. [[KlayGE]] has been tested on these [[Compilers tested|compilers]].
+Before compiling [[KlayGE\en|KlayGE]], Python 2.7+ and CMake 2.8.6+ must be installed first. Then you can run build_external.py to build and install [[Third-party libraries and tools|third-party libraries and tools]]. [[KlayGE\en|KlayGE]] has been tested on these [[Compilers tested|compilers]].
-Since [[KlayGE]] 3.12.0, include and lib paths are set up inside the project files. After extraction, just open the corresponding project file under "Build" directory, [[KlayGE/en|KlayGE]] itself can be built directly. Or you can run build_all.py to do that job.
+Since [[KlayGE\en|KlayGE]] 3.12.0, include and lib paths are set up inside the project files. After extraction, just open the corresponding project file under "Build" directory, [[KlayGE/en|KlayGE]] itself can be built directly. Or you can run build_all.py to do that job.
 '''Notes for MinGW users:'''