Some problems in the construction of ogre1.9+vs2012 environment

Recently in learning Ogre, compile ogre encountered a lot of pits, also learned a lot of knowledge, write down for later to view and share.

Environment setting Goal: can run the Ogre Program (nonsense), can be debugged in the source code

Problems encountered:

1, in the CMake ogre when the source of less engineering to rely on:

A: first to compile dependencies. It is also a common practice for open source projects to put other dependent open source repositories (source code or compiled include+dll+lib) in a dependencies file to CMake congfigure and generate. Make sure that the configuration list is white and not red when cmake.

2, CMake dependencies when prompted less SDL2:

A: You need to download the SDL2 source code in the corresponding location in the src of dependencies.

3, compile good dependencies, and then compile Ogre prompt obj file _msc_ver wrong

A: This is because the VS platform toolset used to compile dependencies and compile ogre is different.

4. How to get different versions of the VS Platform Toolset

Answer: You can only download the corresponding VS

5. How to debug across solutions in VS

A: This can be achieved, as long as the compiled Ogre Debug version of the PDB copied to the target solution working directory inside the line

6. How to press F12 in the header file to view the source code across solutions in VS

A: This is not possible because in the target solution, you can only reference another solution's include, LIB, and DLLs that use another solution. Implement press F12 to view the source code only again under the same solution.

Some problems in the construction of ogre1.9+vs2012 environment