Difference between revisions of "Installation"
m (Ru link) |
Gongminmin (Talk | contribs) m |
||
| Line 1: | Line 1: | ||
| − | Before compiling [[KlayGE]], you can run build_external.py to build and install [[Third-party | + | Before compiling [[KlayGE]], you can run build_external.py to build and install [[Third-party libraries and tools|third-party libraries and tools]]. |
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]] 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. | ||
Revision as of 11:51, 13 May 2012
Before compiling KlayGE, you can run build_external.py to build and install third-party libraries and tools.
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 itself can be built directly. Or you can run build_all.py to do that job.
Notes for MinGW users:
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.
