This is my “hold-your-hand” guide to building the latest Ogre with Visual Studio C++, trunk or stable.

13 July 2010: If anyone could test this guide for Visual Studio 2010 and let me know if it works or not, I would appreciate it. I don’t have access to a Windows machine right now.

Prerequisites

• Download and install the latest DirectX9 SDK: http://msdn.microsoft.com/en-us/directx
• Download and install CMake. It is recommended that you install version 2.8.0, later versions are known to have problems with Ogre: http://www.cmake.org/files/v2.8/
• Download the latest dependencies package: http://sourceforge.net/projects/ogre/files/ (since this post was last updated, that would be: ogre-dependencies-vc++ -> 1.7 -> OgreDependencies_MSVC_20100501.zip)
• [TRUNK] Checkout ogre from SVN: https://ogre.svn.sourceforge.net/svnroot/ogre/trunk/
• [1.7 STABLE] Checkout ogre from SVN: https://svn.ogre3d.org/svnroot/ogre/branches/v1-7 OR download a source package from: http://www.ogre3d.org/download/source

Building Ogre

1. You need to build the dependencies. Extract the Dependencies folder from the zip into the root directory (/trunk/Dependencies/). Go to Dependencies/src and open OgreDependencies.VS20xx.sln. Right click the solution and click Build Solution, which will build every project. Do this for both Release and Debug.
2. Open CMake. “Where is the source code” should point to the root directory, and “Where to build the binaries” should point to a sub folder in the root directory. For example, you can create a folder named VCBuild.
3. Click Configure. Choose the compiler you are building for.
4. A list of options in red will appear. Configure it how you choose. I disable BUILD_PLUGIN_BSP and BUILD_RENDERSYSTEM_D3D10 since they are unnecessary for me.
5. [OPTIONAL] If you have boost built and require threading, set the BOOST_ROOT value to the root of your boost directory (e.g. “C:/boost_1_39″). Subsequent boost variables should automatically be populated. (If this is an environment variable, it should automatically detect it.) Don’t forget to set CONFIG_THREADS to 1 or 2 depending on your requirements.
6. Click configure once again.
7. The options should turn grey. Click OK.
8. Open OGRE.sln in your build directory.
9. Right click the ALL_BUILD project and click Build. Do this for both Release and Debug.
10. Right click the INSTALL project and click Build. Do this for both Release and Debug.
11. You’re done! Make sure you direct any projects using Ogre to the generated sdk folder in your build directory.

FAQ

What happened to CEGUI?
From 1.7, CEGUI is no longer part of Ogre. You should now treat it as a separate library. For instructions, refer to Building CEGUI.

What do I do next?
If you’ve not familiar with setting up an Ogre application, see my Ogre and Visual Studio Beginners FAQ and follow the walkthrough.

Let me know if you have problems with any of the steps, suggestions etc.

HELLO. MY NAME IS BOB SMITH. I MAKE GOOD WEBSITES, AND STUFF.

You know what I’m talking about. The HUGE TEXT THEY USE TO SHOUT AT THE USER ON THE HOMEPAGE. Okay, so why? Well, you could argue it draws in the user’s attention, and that it instantly tells the user what the website is about. Fair enough. But I get bored when browsing CSS design showcases, only to find almost all of them follow this trend. Admittedly, even I fall victim to this nonsense. I get a feeling design showcases discriminate websites that don’t. Perhaps it’s just another internet phase.

My 5 minute browsing results:

http://paiko.de/
http://www.baeck.no/
http://www.sergionoviello.com/
http://nathan-sanders.com/
http://www.shannonmoeller.com/
http://www.jamisonbanham.com/
http://www.jasonreedwebdesign.com/
http://sprawsm.com/
http://www.postmachina.com/

I could go on… Forever.

TidalEngine
TidalEngine is being developed alongside Project Utopia. We decided to transform it into a generic game engine that can be reused for other projects. It was a tough move, and has reduced development speed drastically. But hopefully the hard work will pay off.

We designed it to be extensible, using a modular and add-on architecture. It is multi-tiered depending on what you need. At the bottom level is the utilities – math, events, templates etc. which can be used for pretty much any application. Next is the core engine which abstracts graphics input, GUI, physics etc. Standalone it can be used to create a wide range of offline games. It uses a plugin system, allowing dependencies to be hot-swapped. For example, we have an OpenAL and FMOD plugin – either can be loaded at runtime. At the highest level is networking. This is where all the online operations will be handled.

Mobile Gaming
For a long time we have been carefully planning our pursuit of mobile development. Recently we started to put these plans into practice. We bought a brand new 24″ iMac especially for iPhone development. It will be a steep learning curve, as we’re PC junkies, but this is where most of our attention will be focused for the next few months. We plan on developing multiple titles, each increasingly challenging and complex. That’s about all we can say for now; we also put up a new page.

Websites
We have a number of clients in discussions for possible websites, and a couple more which we’re beavering away at. I’m pleased with the positive response we’ve received until now, so fingers crossed! We’re actively trying to expand our portfolio, so if you have a project in mind let us know!

TidalWare.com
Since my last blog post, I also took the opportunity to redesign our own website. It looked fine already, but until I’m 110% happy, I’m not happy. So back to the drawing board it was, and I came up with something even more minimalistic, and a better menu system to squeeze in our increasing number of pages.

Shortly after, I submitted it to CSS Design Yorkshire, and what do you know, it got featured! :D (There’s quite a few, so just search for ‘tidalware’ or ‘June 08, 2009′)

Conclusion
As you can tell, we’re always busy! If you want day-to-day updates of what we’re up to, be sure to follow us on Twitter. In the meantime I will try my best to blog more often. We removed the news page, so now every TidalWare news tidbit will be posted here.

Visit: http://www.gamerepublic.org/

We have huge plans for PU (I’m thinking I shouldn’t use that acronym). It has required many dozens of plans and documents to explain its direction. Unfortunately I’m not going to reveal too much at this moment, but maybe a little more than you already know. There’s one thing I’d like to clear up, however. It is NOT a pretty fantasy/medieval turn-based RPG. I could count all the grass blades in my sight and the amount of games in such genre will still outnumber them. Project Utopia will be a futuristic game with nothing more than what is scientifically possible. You won’t be playing humans, either.

That’s enough for now. ;) I’ll reveal more as time progresses. Not to alienate your hopes (NPI), but Project Utopia is still in very early stages. The screenshots may look nice, but graphics are only a tiny fraction of the battle. Also, progress will be extremely slow unless we can find more people. Even then, I’m not working on it full time. What will see the project to its finish is our sheer amount of determination.

On a different note, I’d like to remind everyone about the next Game Republic event. It will be held in Leeds on the 12th of January, the subject being “The future of AI”. Unless my plans get screwed somehow, I will be attending the event. So if you’re into that kind of stuff and live in Yorkshire, I recommend you pop along and check it out. More details to follow.