How to configure and compile ogre 1.7.0 + cegui 0.7.1

 

Ogre 1.7.0 download, configuration, and Compilation Guide

-----------------------------------------------

1. https://sourceforge.net/projects/ogre/files/ogre/1.7/ogre-v1-7-0.zip/download of ogre 1.7.0

2. Ogre 1.7.0 dependent Library (occasionally updated, please pay attention to this post): http://www.ogre3d.org/forums/viewtopic.php? F = 1 & t = 54533

3. Decompress ogre, it is recommended to decompress the generated ogre directory to the corresponding version number, for example: F: \ SDK \ ogre-v1-7-0, to distinguish each version

4. decompress the dependent Library to the ogre directory, for example: F: \ SDK \ ogre-v1-7-0 \ Dependencies

5. Open the project vs20xx. sln in the F: \ SDK \ ogre-v1-7-0 \ dependencies \ src directory according to your own VC version

6. Compile the debug and release of the dependent Library

7. download the latest cmake: http://www.cmake.org/cmake/resources/software.html

8. Decompress cmake to any directory, such as: F: \ tools \ cmake-2.8.0-win32-x86

9. Run f: \ tools \ cmake-2.8.0-win32-x86 \ bin \ cmake-gui.exe

10. Set the Ogre decompression path in "where is the source code" and "where to build the binaries", for example, F: \ SDK \ ogre-v1-7-0

11. Click Configure and select the VC version.

12. Click Generate to generate ogre. sln.

13. Compile the debug and release of ogre.

14. If you do not need to run samples, you only need to compile ogremain, rendersystem_direct3d9 (or other) and the required plugin.

 

Cegui 0.7.1 download, configuration, and Compilation Guide

-----------------------------------------------

1. cegui 0.7.1: http://prdownloads.sourceforge.net/crayzedsgui/CEGUI-0.7.1.zip? Download

2. cegui 0.7.1 dependent Library: http://prdownloads.sourceforge.net/crayzedsgui/CEGUI-DEPS-0.7.x-r1-vc9.zip? Download

3. decompress the cegui, it is recommended to decompress the generated cegui directory to change the corresponding version number, for example: F: \ SDK \ cegui-v0-7-1, to distinguish each version

4. decompress the dependent Library to the cegui directory, for example: F: \ SDK \ cegui-v0-7-1 \ Dependencies

5. Go to the directory F: \ SDK \ cegui-v0-7-1 \ projects \ premake

6. Open config. Lua in the directory in notepad and find two variables: ogre_paths and ois_paths.

7. Change it to the corresponding ogre and OIS paths, for example:

Ogre_paths = {"F: \ SDK \ ogre-v1-7-0", "ogremain/include", "lib "}

Ois_paths = {"F: \ SDK \ ogre-v1-7-0/dependencies/include/OIS/", "", "lib "}

8. Find the cegui_old_ois_api variable and set it to false.

9. Find the ogre_renderer variable and set it to true.

10. Find the samples_ogre variable and set it to true.

11. Go to the directory F: \ SDK \ cegui-v0-7-1 \ projects \ premake and run build_vs2008.bat (or another version), you will see cegui. sln

12. Continue to run build_samples_vs2008.bat (or another version). You will see ceguisamples. sln

13. compile cegui. SLN and ceguisamples. if the H or link error still persists during SLN, open the project properties and modify the ogre and OIS-related paths in additional include directories and additional library directories.

14. Note that the Lib of ogre 1.7.0 is generated in the debug and release subdirectories. Remember to change it to the correct link path.

15. before running the sample, remember to copy all the DLL under F: \ SDK \ cegui-v0-7-1 \ dependencies \ bin to F: \ SDK \ cegui-v0-7-1 \ bin, so that no error is reported that the DLL is missing

 

 

Configuration suggestions for various open-source libraries

-----------------------------------------------

1. Right-click my computer and choose Properties> advanced> environment variables.

2. Create the corresponding variable name and PATH value according to the names of different open source libraries, for example: Variable ogre, the value is F: \ SDK \ ogre-v1-7-0

3. Change the previous dead path in the additional include directories and additional library directories of VC to the following: $ (Ogre)/ogremain/include

4. When ogre or cegui is upgraded in the future, you do not need to manually modify the paths one by one. You only need to modify the values (paths) of the corresponding environment variables at a time.

5. Note that when the environment variable changes, VC must restart to identify

 

Good luck, I wish you a good trip on the open source road ~