The ogre official website provides viusual studio running instances called wiki application. For more information, see
Http://www.ogre3d.org/tikiwiki/tiki-index.php? Page = Setting + up + An + application +-+ visual + Studio
AboveArticleIn, we run the sample demo on the Ogre official website, so the runtime environment is solved by the project solution generated by cmake,
We do not need to configure it. Of course, if you do not use cmake to re-generate the project solution, but configure the original project solution by yourself, this will be excluded.
In the link provided above, the official website provides a detailed configuration process, but there are still some issues that need attention:
1. About the environment variable "ogre_home"
The above is the use of Windows batch processing provided by the official website to process the environment variable ogre_home. In fact, this is really unnecessary, because in Visual Studio
The configuration can be completed with the mouse, so it is easy to use the batch processing to configure the environment variable is not necessary, of course, the use of environment variables looks more standard and concise.
2. Dependency libraries in the debug and release phases:
In these two different stages, the ogre dependency libraries are different. This document can be found. The additional dependency libraries we need to add when running the Wiki application:
The environment problem compiled here is almost solved, but it has not been completed yet.
3. How to run the compiledProgram.
If the compilation is based on the above practice and the executable file generated by the final compilation cannot be executed, the system will prompt the missing library in the debug runtime.
Everyone who understands the problem knows how to copy this executable file to the $ ogre_home \ bin \ DEBUG directory.
However, if you configure it on the official website, it is estimated that there is no problem. The official website will solve this problem.
Finally, no image is displayed when running the execution file, because the Wiki application is only a skeleton and does not create a scenario.