diff options
Diffstat (limited to '')
-rw-r--r-- | libraries/irrlicht-1.8/source/source.txt | 106 |
1 files changed, 53 insertions, 53 deletions
diff --git a/libraries/irrlicht-1.8/source/source.txt b/libraries/irrlicht-1.8/source/source.txt index 5581244..ff7ce32 100644 --- a/libraries/irrlicht-1.8/source/source.txt +++ b/libraries/irrlicht-1.8/source/source.txt | |||
@@ -1,53 +1,53 @@ | |||
1 | Source code of the Irrlicht Engine | 1 | Source code of the Irrlicht Engine |
2 | 2 | ||
3 | The complete source of the Irrlicht Engine can be found in this directory. | 3 | The complete source of the Irrlicht Engine can be found in this directory. |
4 | Please note that YOU DO NOT NEED THIS SOURCE to develop 3d applications with | 4 | Please note that YOU DO NOT NEED THIS SOURCE to develop 3d applications with |
5 | the Irrlicht Engine. Instead, please use the .dll in the \bin directory, the | 5 | the Irrlicht Engine. Instead, please use the .dll in the \bin directory, the |
6 | .lib in the \lib directory and the header files in the \include directory. | 6 | .lib in the \lib directory and the header files in the \include directory. |
7 | 7 | ||
8 | You will find a good tutorial how to set up your development environment and to | 8 | You will find a good tutorial how to set up your development environment and to |
9 | use the engine in the \examples directory. (Try 01.helloworld) | 9 | use the engine in the \examples directory. (Try 01.helloworld) |
10 | 10 | ||
11 | The source of the engine is included because for the following reasons: | 11 | The source of the engine is included because for the following reasons: |
12 | 12 | ||
13 | - To let developers be able to debug the engine. | 13 | - To let developers be able to debug the engine. |
14 | - To let developers be able to make changes to the engine. | 14 | - To let developers be able to make changes to the engine. |
15 | - To let developers be able to compile their own versions of the engine. | 15 | - To let developers be able to compile their own versions of the engine. |
16 | 16 | ||
17 | 17 | ||
18 | 18 | ||
19 | HOW TO COMPILE THE ENGINE WITH LINUX | 19 | HOW TO COMPILE THE ENGINE WITH LINUX |
20 | 20 | ||
21 | If you wish to compile the engine for Linux yourself, run a 'make' in the | 21 | If you wish to compile the engine for Linux yourself, run a 'make' in the |
22 | folder 'source/Irrlicht'. After this, you should be able to make all example | 22 | folder 'source/Irrlicht'. After this, you should be able to make all example |
23 | applications in examples. Then just run them from the directory where they are | 23 | applications in examples. Then just run them from the directory where they are |
24 | built. | 24 | built. |
25 | For the necessary compiler and linker flags please check the provided Makefiles | 25 | For the necessary compiler and linker flags please check the provided Makefiles |
26 | in the examples directories. | 26 | in the examples directories. |
27 | 27 | ||
28 | Only the Software Drivers and the Null Driver will work on all Linux machines, | 28 | Only the Software Drivers and the Null Driver will work on all Linux machines, |
29 | while OpenGL support requires either GLX support of the X11 server (try glxinfo) | 29 | while OpenGL support requires either GLX support of the X11 server (try glxinfo) |
30 | or a software OpenGL solution such as Mesa. | 30 | or a software OpenGL solution such as Mesa. |
31 | 31 | ||
32 | If you get a compiling/linking problem like | 32 | If you get a compiling/linking problem like |
33 | 33 | ||
34 | undefined reference to `glXGetProcAddress' | 34 | undefined reference to `glXGetProcAddress' |
35 | 35 | ||
36 | This is a problem introduced by the NVidia drivers. There are several solutions: | 36 | This is a problem introduced by the NVidia drivers. There are several solutions: |
37 | A) Update your drivers. All versions with GLX 1.4 support (i.e. beginning with | 37 | A) Update your drivers. All versions with GLX 1.4 support (i.e. beginning with |
38 | 12/2005) will work. | 38 | 12/2005) will work. |
39 | B) Define the symbol _IRR_GETPROCADDRESS_WORKAROUND_ during compilation of | 39 | B) Define the symbol _IRR_GETPROCADDRESS_WORKAROUND_ during compilation of |
40 | COpenGLDriver.cpp, either by adding it to the compiler command line or by | 40 | COpenGLDriver.cpp, either by adding it to the compiler command line or by |
41 | uncommenting the line defining this symbol inside the OpenGL driver source. | 41 | uncommenting the line defining this symbol inside the OpenGL driver source. |
42 | This will force the use of glXGetProcAddressARB which has better chances to | 42 | This will force the use of glXGetProcAddressARB which has better chances to |
43 | work on older systems. | 43 | work on older systems. |
44 | 44 | ||
45 | If you get compiling or runtime problems regarding XF86VidMode, Xxf86vm.so, or | 45 | If you get compiling or runtime problems regarding XF86VidMode, Xxf86vm.so, or |
46 | the XFree86 VidMode extension you have also several solutions: | 46 | the XFree86 VidMode extension you have also several solutions: |
47 | A) Install the extension for your X server or the developer package in case of | 47 | A) Install the extension for your X server or the developer package in case of |
48 | compiler/linker problems. | 48 | compiler/linker problems. |
49 | B) Disable the VidMode usage by disabling the define _IRR_LINUX_X11_VIDMODE_ in | 49 | B) Disable the VidMode usage by disabling the define _IRR_LINUX_X11_VIDMODE_ in |
50 | include/IrrCompileConfig.h | 50 | include/IrrCompileConfig.h |
51 | In this case you might give the RandR extension a try (by enabling the | 51 | In this case you might give the RandR extension a try (by enabling the |
52 | next define in that file) which also provides fullscreen support under Linux. | 52 | next define in that file) which also provides fullscreen support under Linux. |
53 | If both extensions fail you won't have fullscreen support for Irrlicht. | 53 | If both extensions fail you won't have fullscreen support for Irrlicht. |