History: Building Ogre with boost 1.50 upwards and MinGW

Source of version: 15 (current)

{BOX(width="100%",class="Layout_box9")}{SPLIT(colsize=10%|70%)}
{IMG(src="tiki-download_file.php?fileId=2144&amp;display",height="100",alt="GCC Logo",link="Building Ogre with boost 1.50 upwards and MinGW",imalign="left",title="Building Ogre with boost 1.50 upwards and MinGW")}{IMG}
---
{DIV(class="bigBold")}((Building Ogre with boost 1.50 upwards and MinGW)){DIV}
This is a step-by-step guide for building Ogre, its dependencies and boost from sources, using your favourite Windows compiler, MinGW :)
It covers every single step and will be the only tutorial you need to read for building Ogre if this is your desired setup. Tested on Windows 7 x64 with Ogre 1.10.0
{SPLIT}{BOX}
!!Introduction
This guide covers how to do a static Ogre build with a certain plugin setup, but on the important places, a note will be added that tells what to do differently for a dynamic build or other plugins.

We will assume a lot of different folders in the course of this tutorial. You may of course derive from them if you want.

!!! 1. Download the Ogre sources
Download the latest Ogre sources, using [http://tortoisehg.bitbucket.org/|Mercurial], from the Ogre repository: 
{CODE(wrap="1", colors="c++")}http://bitbucket.org/sinbad/ogre/{CODE}
For the purpose of this tutorial, let's assume you downloaded them to the following folder: ''C:\Ogre\sources\v1-8''

Now make sure you switch your local repository to the branch of Ogre you actually want to use (like v1-8 or v1-9).
For example, with TortoiseHG, you have to "Update" your repo, selecting the branch you need.

!!! 2. Download the Ogre dependencies
The same as above, but download them from the following repository:
{CODE(wrap="1", colors="c++")}https://bitbucket.org/cabalistic/ogredeps/downloads{CODE}
{REMARKSBOX(type="warning",title="For TDM MinGW release builds",close="n")}Using TDM 4.8.1, the Cabalistic ogredeps package only works for debug builds, when building Ogre itself. On release builds you might get errors about multiple definitions of functions, to fix this use this fork of ogredeps, instead of the other one: {CODE(wrap="1", colors="c++")}https://bitbucket.org/ali1234/ogredeps/downloads{CODE}{REMARKSBOX}
This time, let's assume the following folder: ''C:\Ogre\sources\dependencies''


If you want DirectX support, you will also have to download and install the DirectX SDK:
[http://www.microsoft.com/en-us/download/details.aspx?id=6812|Download and install DirectX 9 SDK]

!!! 3. Download and install CMake
[http://www.cmake.org/cmake/resources/software.html|Download and install CMake]
Be sure to use the latest version.

!!! 4. Download and install MinGW
Download the latest MinGW version [http://sourceforge.net/projects/mingw/files/Installer/mingw-get-inst/|from here], and install it.
It is advised to install it to the default directory: ''C:\MinGW''
Make sure to use "Download latest repository catalogue". The current pre-packaged is GCC 4.6 only (may change in the future).
Also be sure to add ''C:\MinGW\bin'' and ''C:\MinGW\msys\1.0\bin'' [http://www.computerhope.com/issues/ch000549.htm|to your PATH].

Or you can choose to use the TDM version of MinGW, which provides many bug fixes aside from just the MinGW project, from http://tdm-gcc.tdragon.net/download (current version is GCC 4.8.1).
Generally it will automatically add your installation directory to the PATH, but just in case you should check.

!!! 5. Download boost
Download boost [http://sourceforge.net/projects/boost/files/boost/|from here]. This tutorial was written with version 1.50 in mind, but should work for any newer version as well.
Let's assume ''C:\boost'' as the path.

!!! 6. Building boost
Now we come to the fun part - building!
# Navigate to ''C:\boost''
# Open ''index.html'' and go to "Getting Started" -> "Getting Started on Microsoft Windows"
# Follow the steps to build boost from sources. You will most likely want to read section 5.3 "Build Binaries from source". Mind the following:
## Whenever you're supposed to run "bootstrap.bat", run "bootstrap.bat gcc" instead.
## As you are using MinGW, specify gcc as toolset when actually building boost.
## Building boost takes __much time__. Get a cup of tea.
## If you use the following line to build boost...{CODE(wrap="1", colors="c++")}b2 --build-dir=C:\boost\build toolset=gcc --build-type=complete stage{CODE} ... you will end up with a ''stage'' folder in ''C:\boost''. Move the ''lib'' folder inside the stage folder to ''C:\boost'' so that you end up having a ''C:\boost\lib'' folder.
## If you get a ''"Duplicate name of actual target"'' error when building boost, use "minimal" build-type instead of "complete".
# Add ''C:\boost'' to PATH and create new environment variables named BOOST_ROOT and Boost_DIR also pointing to ''C:\boost''.

!!! 7. Building the Ogre dependencies
# Open the CMake GUI.
# Set "Where is the source code" to ''C:\Ogre\sources\dependencies''.
# Set "Where to build the binaries" to ''C:\Ogre\building\dep-release''. THIS IS NOT the final dependencies folder. It is merely the folder we will use to build the SDK.
# Click "Configure" to init CMake. Select "MinGW Makefiles".
# Based on your setup, CMake may or may not output some errors. Make sure to resolve them before continuing. CMake is usually pretty verbose about what to do. If you are having trouble, you can always ask in our forums, of course :). Click "Configure" again until no more errors appear.
# Change CMAKE_INSTALL_PREFIX to ''C:\Ogre\built\dependencies''. Click "Generate".
# Repeat 3) – 6), this time changing CMAKE_BUILD_TYPE to "Debug". Also change the "Where to build the binaries" folder to ''C:\Ogre\building\dep-debug''.
# Open a command line in ''C:\Ogre\building\dep-release'' and type in "mingw32-make install". This will take a minute or two. Do this also for the debug folder.
# Navigate to ''C:\Ogre\built\dependencies''. Navigate to lib/Release within that folder and copy the cg.lib to lib/Debug. Somehow, the install make misses this.
# Create a new folder in ''C:\Ogre\sources\v1-8'', call it ''Dependencies'' and copy all the contents from ''C:\Ogre\built\dependencies'' there.
{REMARKSBOX(type="warning",title="For 64 bit machines")}In FreeImage there is an error somewhere within libTIFF4, due to a bad pointer conversion, this is the place:
{CODE(wrap="1", colors="c++")}// Warning: tif_fd is declared as 'int' currently (see libTIFF), 
    // may result in incorrect file pointers inside libTIFF on 
    // 64bit machines (sizeof(int) != sizeof(long)). 
    // Needs to be fixed within libTIFF.
   if (tif) {
      tif->tif_fd = (long)handle;
   }

   return tif;{CODE}
The comment is mentioning the problem and it tells you to go to the source of libTIFF and fix it there, but an easier fix I found is to just change the line causing the problem to this:
{CODE(wrap="1", colors="c++")}tif->tif_fd = (intptr_t)handle;{CODE}
intptr_t type is guaranteed to allocate enough space for the data, so no more errors here.{REMARKSBOX}

!!! 8. Building OIS statically (OPTIONAL)
# To build static OIS you will need to build it separately from the other ogredeps. First get the source from {CODE(wrap="1", colors="c++")}http://sourceforge.net/projects/wgois/{CODE}. Let's assume you use the original name of the folder which is ''ois-v-1-3''.
# Navigate to ''ois-v-1-3/Win32/'' and open ois.cbp with Code::Blocks.
# Set the project compiler search path to your DirectX SDK directory, so it can find all the headers needed.
# Make some changes in the code, as it will not compile out of the box:
In Win32Joystick.cpp line 587:
hr = CoCreateInstance(__uuidof(WbemLocator), NULL, CLSCTX_INPROC_SERVER, __uuidof(IWbemLocator), (LPVOID*)&pIWbemLocator);
uses the VC keyword __uuidof, which MingW doesn't have. Change this line to:
hr = CoCreateInstance(CLSID_WbemLocator, NULL, CLSCTX_INPROC_SERVER, IID_IWbemLocator, (LPVOID*)&pIWbemLocator);

Also the two instances of swscanf_s (Microsoft specific) were changed to swscanf.
# The libraries that have the Microsoft COM functions that are used in W32Joystick setup need to be linked in. These libraries are ole32 and oleaut32.
# OIS static libs (the build targets are Release and Debug) should be successfully, but the .dlls still need more libs to link against, those are: wbemuuid.lib, dinput8 and dxguid.
# When you have succesfully compiled all build targets, copy libs from ''ois-v-1-3/lib'' into your dependencies folder. Change their names to "libOIS.a" and "libOIS_d.a" for each one respectively and replace the old libs.
# Replace the old .dlls with new ones from ''ois-v-1-3/dll'' just like you did with the libs.
# You have successfully replaced dynamic OIS from ogredeps with static OIS you just compiled.

{REMARKSBOX(type="note",title="Static libs require dependencies to be linked",close="n")}If you want to use the static OIS library, you will also have to change CMake options for ogre by adding wbemuuid.lib, dinput8 and dxguid as extra libraries to link against.{REMARKSBOX}

!!! 9. Building the Ogre SDK
{REMARKSBOX(type="warning",title="For 64 bit users")}Before doing anything, if you use a 64 bit system you need to open CMakeLists.txt in ''C:\Ogre\sources\v1-8'' and look for the flag -march=i686. Change it to -march=x86-64. This will fix any "CPU you selected does not support x86-64 instruction set" errors.{REMARKSBOX}
''C:\Ogre\sources\v1-8''
# Open the CMake GUI.
# Set "Where is the source code" to .
# Set "Where to build the binaries" to ''C:\Ogre\building\ogre-release''. THIS IS NOT the final SDK folder. It is merely the folder we will use to build the SDK.
# Click "Configure" to init CMake. Select "MinGW Makefiles".
# CMake should find the dependencies but if it does not, set the OGRE_DEPENDENCIES_DIR to ''C:\Ogre\sources\v1-8\Dependencies'' manually.
# You can ignore the "Boost_DIR-NOTFOUND" if everything else worked well. If you have a look at the vars in "Advanced" CMake mode, you will see that all boost related vars except that one are correct.
# Set the CMAKE_INSTALL_PREFIX to ''C:\Ogre\built\ogre-sdk''. Click "Configure" again.
# If everything worked out, you will get a load of new configurations. Make sure to select OGRE_STATIC, OGRE_INSTALL_SAMPLES and OGRE_INSTALL_DOCS. 
## If you want a dynamic build, do not select OGRE_STATIC :)
## You can of course select other plugins as you desire, but this tutorial does only "guarantee" to work for the stated ones.
# Click "Configure" again, resolving all problems that might appear, until everything goes well. Click "Generate".
# Repeat 3) – 9), this time changing CMAKE_BUILD_TYPE to "Debug". Also change the "Where to build the binaries" folder to ''C:\Ogre\building\ogre-debug''.
# Open a command line in ''C:\Ogre\building\ogre-release'' and type in "mingw32-make install". This will take some time, so get another cup of tea. Do this also for the debug folder (and get your third cup of tea).
{REMARKSBOX(type="warning",title="Again for 64 bit ogre")}You may encounter some errors when Ogre::StringConverter is used. These are caused by some #ifdefs that are a bit strange, the errors themselves are "ogre\RenderSystems\GL\src\Win32\OgreWin32Window.cpp|260|error: call of overloaded 'toString(DWORD&)' is ambiguous|", this happens when it tries to use the DWORD type argument (unsigned long long) and there is no overload for this type of argument, the compiler then doesn't know which type to convert to and starts complaining.
This is an example place of where such an error happens: (there are more than 1, but all of them can be fixed using the same logic)
{CODE(wrap="1", colors="c++")}if (!GetMonitorInfo(hMonitor, &monitorInfoEx))
            {
                DWORD le = GetLastError();
                LogManager::getSingleton().logMessage(LML_CRITICAL, 
                    ::Ogre::String("Win32Window::create(): Call to GetMonitorInfo() failed.")
                    + ::Ogre::String(" GetLastError() returns: ")
                    + ::Ogre::StringConverter::toString(le)
                    );
                OGRE_EXCEPT(Exception::ERR_RENDERINGAPI_ERROR, "Call to GetMonitorInfo() failed", "Win32Window::create()");
            }{CODE}
The fix is converting DWORD to size_t, for which there is an overloaded function.
{CODE(wrap="1", colors="c++")}+ ::Ogre::StringConverter::toString(size_t(le)){CODE}{REMARKSBOX}

!!! 10. Done
That's it!
You'll have a ready-to-use-with-MinGW Ogre SDK sitting in ''C:\Ogre\built\ogre-sdk'', both in release and debug version.
Try out the samples, they rock! :D
Also, you'll probably want to go to the toilet with all that tea you just drank.

{DIV(class="Layout_box13")}%help% If you should encounter any problems while reading, please post in the [http://www.ogre3d.org/forums/viewtopic.php?f=5&t=71738&p=467778|forum thread for this article].{DIV}
History: Building Ogre with boost 1.50 upwards and MinGW

Source of version: 15 (current)

Search by Tags

Latest Changes

Search

Online Users
