Difference between revisions of "Third-party libraries and tools"

From KlayGE
Jump to: navigation, search
m
Line 1: Line 1:
[[KlayGE]] depends on these following third-party libraries and tools. Since 3.12.0, the source code of these libraries are included in KlayGE. Users can run build_external.py to build and install them. The only pre-required one is Python.
+
[[KlayGE]]'s code depends on these following third-party libraries and tools. Since 3.12.0, the source code of these libraries are included in KlayGE. Users can run build_external.py to build and install them.
  
 
== Core requires: ==
 
== Core requires: ==
*[http://www.python.org/ Python] 3.2. Debug version pythonxx_d.dll need to be compiled from Python's source yourself.
 
 
*[http://www.boost.org/ Boost] 1.53.0. Recommanded bjam command line please check [[FAQ]]
 
*[http://www.boost.org/ Boost] 1.53.0. Recommanded bjam command line please check [[FAQ]]
 
*[http://rapidxml.sourceforge.net/ RapidXml] 1.13
 
*[http://rapidxml.sourceforge.net/ RapidXml] 1.13
Line 8: Line 7:
  
 
== D3D11 Rendering System, DInput Input System and DSound Audio System require: ==
 
== D3D11 Rendering System, DInput Input System and DSound Audio System require: ==
 +
*Microsoft Windows SDK 8.0 comes with Visual Studio 2012, or
 
*[http://msdn.microsoft.com/directx DirectX SDK] June 2010
 
*[http://msdn.microsoft.com/directx DirectX SDK] June 2010
  
 
== DShow Show System requires: ==
 
== DShow Show System requires: ==
*Microsoft Windows SDK 7.0A comes with Visual Studio 2010, Microsoft Windows SDK 6.0A comes with Visual Studio 2008, or [http://www.microsoft.com/downloads/details.aspx?FamilyID=484269e2-3b89-47e3-8eb7-1f2be6d7123a&displaylang=en Windows(R) Server 2003 R2 Platform SDK]
+
*Microsoft Windows SDK 8.0 comes with Visual Studio 2012, or
 +
*Microsoft Windows SDK 7.0A comes with Visual Studio 2010, or
 +
*Microsoft Windows SDK 6.0A comes with Visual Studio 2008, or
 +
*[http://www.microsoft.com/downloads/details.aspx?FamilyID=484269e2-3b89-47e3-8eb7-1f2be6d7123a&displaylang=en Windows(R) Server 2003 R2 Platform SDK]
  
  
 
== OggVorbis Audio Datasource requires: ==
 
== OggVorbis Audio Datasource requires: ==
 
*[http://xiph.org/downloads/ libogg] 1.3.0 and [http://xiph.org/downloads/ libvorbis] 1.3.3, must be compiled to static library
 
*[http://xiph.org/downloads/ libogg] 1.3.0 and [http://xiph.org/downloads/ libvorbis] 1.3.3, must be compiled to static library
 
  
 
== OpenAL Audio System requires: ==
 
== OpenAL Audio System requires: ==
 
*[http://www.openal.org/downloads.html OpenAL SDK] 1.1
 
*[http://www.openal.org/downloads.html OpenAL SDK] 1.1
 
  
 
== OpenGL Rendering System requires: ==
 
== OpenGL Rendering System requires: ==
 
*[http://developer.nvidia.com/object/cg_toolkit.html NVIDIA Cg] 3.0
 
*[http://developer.nvidia.com/object/cg_toolkit.html NVIDIA Cg] 3.0
  
 
+
== OpenGL ES Rendering System requires: ==
== OpenGL ES 2 Rendering System requires: ==
+
*[http://developer.nvidia.com/tegra-resources-archive x86 Windows OpenGL ES 2.0 Emulator], or
*[http://developer.nvidia.com/tegra-resources-archive x86 Windows OpenGL ES 2.0 Emulator] Or
+
*[http://www.imgtec.com/powervr/insider/sdk/KhronosOpenGLES2xSGX.asp PowerVR Insider SDK] v2.9, or
*[http://www.imgtec.com/powervr/insider/sdk/KhronosOpenGLES2xSGX.asp PowerVR Insider SDK] v2.9 Or
+
 
*[http://www.malideveloper.com/tools/software-development/opengl-es-20-emulator.php ARM Mali OpenGL ES 2.0 Emulator] v1.3
 
*[http://www.malideveloper.com/tools/software-development/opengl-es-20-emulator.php ARM Mali OpenGL ES 2.0 Emulator] v1.3
  
 +
== Python Script System requires: ==
 +
*[http://www.python.org/ Python] 3.2. Debug version pythonxx_d.dll need to be compiled from Python's source yourself.
  
 
== KFontGen tool requires: ==
 
== KFontGen tool requires: ==
Line 38: Line 40:
 
= Notes =
 
= Notes =
  
As mentioned previously, before the first compilation of KlayGE, run the env_vars.py Python script to set the required environment variables.
+
Before running building script, Python and [http://www.cmake.org/ CMake] must be installed.
  
 
As KlayGE uses VC Multi-threaded DLL runtime library, it needs ALL libs that linked to exes change to use Multi-threaded DLL runtime library (Project->Properties->Configuration Properties->C/C++->Code Generation->Runtime Library, select Multi-threaded Debug DLL/Multi-threaded DLL).
 
As KlayGE uses VC Multi-threaded DLL runtime library, it needs ALL libs that linked to exes change to use Multi-threaded DLL runtime library (Project->Properties->Configuration Properties->C/C++->Code Generation->Runtime Library, select Multi-threaded Debug DLL/Multi-threaded DLL).

Revision as of 05:20, 31 March 2013

KlayGE's code depends on these following third-party libraries and tools. Since 3.12.0, the source code of these libraries are included in KlayGE. Users can run build_external.py to build and install them.

Core requires:

D3D11 Rendering System, DInput Input System and DSound Audio System require:

  • Microsoft Windows SDK 8.0 comes with Visual Studio 2012, or
  • DirectX SDK June 2010

DShow Show System requires:

  • Microsoft Windows SDK 8.0 comes with Visual Studio 2012, or
  • Microsoft Windows SDK 7.0A comes with Visual Studio 2010, or
  • Microsoft Windows SDK 6.0A comes with Visual Studio 2008, or
  • Windows(R) Server 2003 R2 Platform SDK


OggVorbis Audio Datasource requires:

OpenAL Audio System requires:

OpenGL Rendering System requires:

OpenGL ES Rendering System requires:

Python Script System requires:

  • Python 3.2. Debug version pythonxx_d.dll need to be compiled from Python's source yourself.

KFontGen tool requires:

  • FreeType 2.4.11, Debug and Release solution configurations should be compiled


Notes

Before running building script, Python and CMake must be installed.

As KlayGE uses VC Multi-threaded DLL runtime library, it needs ALL libs that linked to exes change to use Multi-threaded DLL runtime library (Project->Properties->Configuration Properties->C/C++->Code Generation->Runtime Library, select Multi-threaded Debug DLL/Multi-threaded DLL).

In addition, using VC8 and VC9 to compile Release versions of Boost needs to define the _SECURE_SCL = 0 macro. If you are using Boost Build (bjam) to build the libraries, make sure to add "define=_SECURE_SCL=0" to the bjam command line.