Image
Setting Up An Application With Code::Blocks And MinGW

Introduction

This set of instructions will walk you through setting up a Code::Blocks C++ project from scratch. An alternative to this tutorial is to use the Ogre Application Wizard instead. This tutorial is still useful if you wish to understand what the Application Wizard does for you. When you have finished this tutorial you will be able to compile a working Ogre Application and you will be ready to start the Basic Tutorials.

Prerequisites

Install the Ogre SDK as detailed here: Installing the Ogre SDK
note Make sure that the environment variable OGRE_HOME is pointing to the root of the Ogre MinGW SDK.

Setting up Code::Blocks / MinGW for OGRE Development

Install the latest MinGW official distribution

OGRE 1.7.2 requires MinGW 4.5. Get it at: http://www.mingw.org/
For instructions on how to install MinGW go to: http://www.mingw.org/wiki/InstallationHOWTOforMinGW

Install Code::Blocks

Download the Code::Blocks official release.
It is suggested to download the version that does not come with its own version of MinGW, as it might be incompatible with the one used to compile the Ogre SDK.

Create a directory for it - C:\CodeBlocks - and unzip the three archives into it.

Start Code::Blocks and pick the MinGW compiler from the list of detected build systems.

Goto Settings -> Compiler and Debugger to show the Global compiler settings:

CodeBlocks global compiler settings

It should be populated properly, but it can't hurt to check. smile

Also make sure that the MinGW version Code::Blocks uses is the same that was used to compile Ogre.
Do not use the MinGW version that comes with Code::Blocks. It is rather old.

You can find out your version of MinGW by going to "C:\MinGW\lib\gcc\mingw32".
This folder will contain another folder with a version number.

Create new Console application project

Click the 'Create a new project' link in the Code::Blocks start page, or find it in the menu.
Choose 'Console application':

newProject.png

Be sure to put the project in a directory with no spaces in the (full) name.
A good name would be 'C:\Projects\OgreProject':

projectPaths.png


Add the Wiki Tutorial Framework

Now we need to add some files to the project.

Download the Ogre Wiki Tutorial Framework:

 Plugin disabled

Plugin attach cannot be executed.
.

Unpack the four files into your new OgreProject directory:

newFilesinFolder.png

Right-click main.cpp in the project tree and delete it.
Now, we need to add the wiki tutorial framework to our project.
Right-click and Add files recursively...:

addFilesRecursively1.png

You are given a list of four files. Click 'OK' to add them:

addFilesRecursively2.png


Project Build Options

Right-click our OgreProject and choose Build options from the context menu:

gotoBuildOptions.png

Common Build Options

Compiler settings - Other options


Set Compiler settings - Other options to

-mthreads
-fmessage-length=0
-fexceptions
-fident


projectSettings1.png

Make sure that OgreProject is selected, and not one of the build configurations.

Compiler settings - defines


Set Compiler settings - defines to

WIN32
_WINDOWS


projectSettings2.png

Again, make sure that OgreProject is selected, and not one of the build configurations.

Linker settings - Other linker options


Set Linker settings - Other linker options to

-Wl,--enable-auto-image-base
-Wl,--add-stdcall-alias
-Wl,--enable-auto-import


projectSettings3.png

Again, make sure that OgreProject is selected in the configuration tree.

Search Directories - Compiler


Set Search Directories - Compiler to

$(OGRE_HOME)\include
$(OGRE_HOME)\include\OGRE
$(OGRE_HOME)\include\OIS
$(OGRE_HOME)\boost


Code::Blocks Search Directories

It would be prudent to mention that OgreProject should be selected in the configuration tree (and not one of the build configurations)

Search Directories - Linker


Set Search Directories - Linker to

$(OGRE_HOME)\bin\$(TARGET_NAME)


projectSettings5.png

Again, you need to have OgreProject selected, not one of the build configurations! razz

Debug Build options

Select the Debug build configuration in the configuration selector on the left.

Debug - Compiler settings - defines


Set Debug - Compiler settings - defines to

_DEBUG


projectSettings6.png



Set Debug - Linker settings - Link libraries to

OgreMain_d
OIS_d


projectSettings7.png


Release Build options

Release - Compiler settings - defines


Set Release - Compiler settings - defines to

NDEBUG


projectSettings8.png



Set Release - Linker settings - Link libraries to

OgreMain
OIS


projectSettings9.png


Additional libraries when using boost


When you use a version of the Ogre SDK that uses boost, you will need to link against some boost libraries.
For boost 1.50+, these are:

date_time
thread
system
chrono

For previous boost versions, you can ignore system and chrono.

To get the exact file names, have a look at your Ogre SDK folder. If it uses boost, it will contain a "boost" folder which has all needed libraries in "lib" in both debug and release. (Remember to add "$(OGRE_HOME)\boost\lib" to "Search Directories - Linker" if you use boost!)

One filename could be, for example, "libboost_date_time-mgw47-mt-1_51.a", which is a boost 1.51 version compiled with MinGW GCC 4.7.X.
For this, you would have to link against "boost_date_time-mgw47-mt-1_51".

Debugging

If you want to run your executable from within Code::Blocks, you need to set up 'working directory' and 'command' in the project settings like this:

code_blocks_build_targets_dialog.png


Conclusion

That's it.
You should now be able to compile and run your Ogre application.
Well, maybe not until you've copied it to the Ogre sdk bin directory (or take resources.cfg and plugins.cfg from there).
Or by copying Ogre dlls and media..
But that's something for a later wiki article..

Proceed to the Tutorials. smile