aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/libraries/irrlicht-1.8/source/Irrlicht/source.txt
diff options
context:
space:
mode:
Diffstat (limited to '')
-rw-r--r--libraries/irrlicht-1.8/source/Irrlicht/source.txt80
1 files changed, 40 insertions, 40 deletions
diff --git a/libraries/irrlicht-1.8/source/Irrlicht/source.txt b/libraries/irrlicht-1.8/source/Irrlicht/source.txt
index f90ea06..0b90f10 100644
--- a/libraries/irrlicht-1.8/source/Irrlicht/source.txt
+++ b/libraries/irrlicht-1.8/source/Irrlicht/source.txt
@@ -1,40 +1,40 @@
1Source code of the Irrlicht Engine 1Source code of the Irrlicht Engine
2 2
3The complete source of the Irrlicht Engine can be found when decompressing 3The complete source of the Irrlicht Engine can be found when decompressing
4the .zip file included in this directory. 4the .zip file included in this directory.
5Please note that YOU DO NOT NEED THIS SOURCE to develop 3d applications with 5Please note that YOU DO NOT NEED THIS SOURCE to develop 3d applications with
6the Irrlicht Engine. Instead, please use the .dll in the \bin directory, the 6the Irrlicht Engine. Instead, please use the .dll in the \bin directory, the
7.lib in the \lib directory and the header files in the \include directory. 7.lib in the \lib directory and the header files in the \include directory.
8 8
9You will find a good tutorial how to set up your development environment and to 9You will find a good tutorial how to set up your development environment and to
10use the engine in the \examples directory. (Try 1.helloworld) 10use the engine in the \examples directory. (Try 1.helloworld)
11 11
12The source of the engine is only included because of the following reasons: 12The source of the engine is only included because of the following reasons:
13 13
14 - To let developers be able to debug the engine. 14 - To let developers be able to debug the engine.
15 - To let developers be able to make changes to the engine. 15 - To let developers be able to make changes to the engine.
16 - To let developers be able to compile their own versions of the engine. 16 - To let developers be able to compile their own versions of the engine.
17 17
18 18
19 19
20HOW TO COMPILE THE ENGINE WITH LINUX 20HOW TO COMPILE THE ENGINE WITH LINUX
21 21
22If you wish to compile the engine in linux yourself, unzip the source source.zip 22If you wish to compile the engine in linux yourself, unzip the source source.zip
23file in the \source directory. Run a 'make' in the now existing new subfolder 'Irrlicht'. 23file in the \source directory. Run a 'make' in the now existing new subfolder 'Irrlicht'.
24After this, you should be able to make all example applications in \examples. 24After this, you should be able to make all example applications in \examples.
25Then just start an X Server and run them, from the directory where they are. 25Then just start an X Server and run them, from the directory where they are.
26 26
27If you get a compiling/linking problem like 27If you get a compiling/linking problem like
28 28
29 undefined reference to `glXGetProcAddress' 29 undefined reference to `glXGetProcAddress'
30 30
31Then there are several solutions: 31Then there are several solutions:
32A) This disables the use of OpenGL extensions: 32A) This disables the use of OpenGL extensions:
33 Open the file IrrCompileConfig.h, comment out _IRR_OPENGL_USE_EXTPOINTER_, 33 Open the file IrrCompileConfig.h, comment out _IRR_OPENGL_USE_EXTPOINTER_,
34 and recompile Irrlicht using 34 and recompile Irrlicht using
35 make clean 35 make clean
36 make 36 make
37B) Replace all occurrences of 'glXGetProcAddress' with 'glXGetProcAddressARB' and run a 37B) Replace all occurrences of 'glXGetProcAddress' with 'glXGetProcAddressARB' and run a
38 make 38 make
39 This will solve the issue but keep the OpenGL extension enabled. 39 This will solve the issue but keep the OpenGL extension enabled.
40 40