History: CMake Quick Start Guide

1. Download the Dependencies repository. To i.e. C:\OgreSDK\Dependencies
2. Download and install CMake. You want the 'Win32 installer' release in the binary distribution section. Use version +2.8; version 3.x is not widely tested yet.
3. Launch CMake via Start > Program Files > CMake 2.8 > CMake
4. Point "Where is the source code" to C:\OgreSDK\Dependencies; and "Where to build the binaries" pointing to "C:\OgreSDK\Dependencies\build"
5. Click 'Configure' and select the generator (i.e. if you're using Visual Studio 2013, select Visual Studio 12)
6. Answer 'Ok' when asked if you want to create the build directory
7. Sometimes on bleeding edge repos there might be CMake syntax warnings. Ignore them.
8. Now click 'Generate'.
9. Open C:\OgreSDK\Dependencies\build\OGREDEPS.sln under Visual Studio. If you have multiple versions of VS, make sure you open it with the one you targeted for in CMake.
10. Build the whole solution; which should build FreeImage, freetype, OIS, zlib and zziplib. Make sure to build both Debug and Release
11. Once it's finished, right click on INSTALL project, and click build. THIS IS VERY IMPORTANT. It will create the folder structure that Ogre needs. You need to do this both for Debug and Release.
12. This should've created an SDK folder structure under C:\OgreSDK\Dependencies\build\ogredeps
13. Now download Ogre from the repository into C:\OgreSDK.
14. We now repeat the same process: Open CMake, set C:\OgreSDK and C:\OgreSDK\build as "Where is the source code" and "Where to build the binaries" respectively.
15. Hit Configure and choose the same Visual Studio generator you did for the dependencies. It will now complain it can't find the Dependencies.
16. Set OGRE_DEPENDENCIES_DIR to point to C:\OgreSDK\Dependencies\build\ogredeps as in the picture. Use the search filter to find the option quickly. Now hit configure again.
17. Pro tip: If "C:\OgreSDK\Dependencies" contains the files that are generated in C:\OgreSDK\Dependencies\build\ogredeps; you can skip the previous step.
18. Click Generate.
19. Open the solution C:\OgreSDK\build\OGRE.sln and compile.
20. Right click on INSTALL project if you wish to generate the SDK structure we provide in our official releases.
21. You're done.
22. If you are like me (I don't like using INSTALL feature for my own projects), you can add C:\OgreSDK\build\include to your project's include location and C:\OgreSDK\build\lib\Debug (and Release) to your additional library paths. The DLLs will be located in bin\debug (or release)

That's it for CMake! You now have a set of project files that are very much like you're used to in previous versions of OGRE, in the output folder you chose. There is now a special target called 'ALL_BUILD' which is a quick way to build all targets for a specific configuration. Note that all build output is now stored in a subfolder of this build folder, and not in the original OGRE source folder - so you can create multiple builds from one source directory now.

If you're more into video tutorials instead of reading, here's one:

If the embedded player is not showing up, here's the link: https://www.youtube.com/watch?v=-3XwyYQ9OLg

-(Linux)--------

1. Download Ogre Source (Instructions below assume current version of 1.8.0, update as needed)
2. Decompress:
   Copy to clipboard

   tar xjf ogre_src_v1-8-0.tar.bz2

3. Move to source directory:
   Copy to clipboard

   cd ogre_src_v1-8-0

4. Create build directory:
   Copy to clipboard

   mkdir build

5. Move into build directory:
   Copy to clipboard

   cd build

6. Trigger cmake, passing path to Ogre source directory:
   Copy to clipboard

   cmake ..

   See the Extensive CMake page for a list of compilation options which can be passed to CMake at this stage, and Getting Started With CMake for even more background material. N.B. Please note that OGRE_CONFIG_THREADS = 1 is not supported on Linux.
7. If the CMake results look good, build Ogre:
   Copy to clipboard

   make -j2

   The -j2 specifies how many parallel compilation jobs to run. Substitute the number of processor cores on your system, e.g. -j2 for a dual-core, -j4 for a quad core...
8. Once compilation is successful, you can install into the system (by default, /usr/local):
   Copy to clipboard

   sudo make install

-(Mac OS X)--------

Building Ogre via CMake GUI (see alt. command line below)

Xcode 4.3 changed the layout of developer tools on disk which can cause some serious problems for CMake. The issue has been fixed but is not yet publicly released. CMake 2.8.8 will include Xcode 4.3 support. At the time of writing, a release candidate is available that includes this support.

You will also need to install the Command Line Tools from within Xcode's Downloads Preferences and set the Xcode path from the command line like this.

Assuming that Xcode is installed in /Applications,

sudo xcode-select -switch /Applications/Xcode.app/Contents/Developer

1. Download CMake. You want the 'Mac OS X Universal' release in the binary distribution section
2. The .dmg will probably auto-mount when it downloads, if not, double-click it to open
3. Double-click the .pkg installer, install on your main drive and opt to install the command-line tools too (in case you want to use them later, we will use the GUI here)
4. Launch CMake via Applications
5. In the "Where is the source code" box, type or browse to the root directory of your OGRE source (the one that contains the OgreMain folder)
6. In the "Where to build the binaries" box, type or browse to any folder you like - this will be where the build output will go (libraries, headers, dlls & sample exes). The folder does not have to exist yet. Note that you can run this process more than once with different output folders if you want (but we won't complicate matters now)
7. Hit the 'Configure' button near the bottom of the screen
8. Pick 'Xcode' as the generator and opt to use native compilers
9. Answer 'Ok' when asked if you want to create the build directory
10. Wait for the configure process to finish
11. The screen will now have a bunch of configuration options on it, which will be red (this is to indicate this is the first time you've seen them). You can see the potential for customising your build here, but for now just click the 'Configure' button again
12. The values will turn grey, and the 'Generate' button at the bottom will now be enabled. Click 'Generate'
13. Build files will now be generated in the location you picked
14. Now, open OGRE.xcodeproj in the build directory you picked, open it in Xcode. SampleBrowser will build everything!

Note: ALL_BUILD does not work properly with Xcode 4.

Building Ogre via Command Line (see alt. GUI method above)

1. Download Ogre Source (Instructions below assume current version of 1.8.0, update as needed)
2. Decompress:
   Copy to clipboard

   tar xjf ogre_src_v1-8-0.tar.bz2

3. Move to source directory:
   Copy to clipboard

   cd ogre_src_v1-8-0

4. Create build directory:
   Copy to clipboard

   mkdir build

5. Move into build directory:
   Copy to clipboard

   cd build

6. Trigger cmake, specify Xcode generation and pass path to Ogre source directory:
   Copy to clipboard

   cmake -GXcode ..

   See the Extensive CMake page for a list of compilation options which can be passed to CMake at this stage, and Getting Started With CMake for even more background material.
7. Build via Xcode
   Copy to clipboard

   xcodebuild -configuration RelWithDebInfo

   (or open OGRE.xcodeproj and build within Xcode)

Installing Ogre

You will find Ogre.framework in 'lib' within your build directory. You can embed this in your application bundle, or drag it to /Library/Frameworks for system-wide installation.

You will also find plugins (Plugin_*.dylib and RenderSystem_GL.dylib) in the same location, you can copy these to the framework's Resource directory or your own application's bundle. Be sure to configure you applications' plugins.cfg to match (e.g. /Library/Frameworks/Ogre.framework/Resources/)

-(iPhone)--------
Detailed instructions on building OGRE for iPhone can be found on this page Building From Source (for iPhone)

-(Android)--------

Here we target the lowest possible Android API, which is API 10 Android 2.3.3. This build process has been tested using OGRE v1.9 and v1.10 using both Linux and Windows hosts and up to Android 4.4 Kitkat (API 19).

General Android Build Instructions:

1. Download and install the Android SDK:
   Copy to clipboard

   https://developer.android.com/sdk/

2. Follow the instructions on the SDK site to use the tools included in the SDK to download and install your target Android API version.
3. Download and install the Android NDK. Android NDK revision 8b is not supported due a bug in the toolchain.
   Copy to clipboard

   https://developer.android.com/tools/sdk/ndk/

4. Initialize your Android SDK and NDK environment variables:
   1. Create environment variables ANDROID_SDK and ANDROID_NDK and set them to the full install path of the Android SDK and NDK respectively.
   2. Prepend %ANDROID_SDK%\tools, %ANDROID_SDK%\platform-tools, and %ANDROID_NDK% to the beginning of your PATH variable.
5. Download and build the OGRE dependencies. This will require configuring `ogredeps` to target an Android build while running CMake.
   1. Download ogredeps.
      Copy to clipboard

      https://bitbucket.org/cabalistic/ogredeps

   2. Navigate your command prompt to the root of the ogredeps build directory.
   3. Run CMake to create your build files. ANDROID_ABI is usually armeabi-v7a, ANDROID_NATIVE_API_LEVEL should match whatever API level you downloaded via the SDK utilities, ANDROID_TOOLCHAIN_NAME should match the toolchain (i.e., build system) you wish to use from %ANDROID_NDK%\toolchains, and replace "Unix Makefiles" with whatever build system you wish to use. Assuming you are building from ogredeps/build:
      Copy to clipboard

      cmake -G"Unix Makefiles" -DCMAKE_TOOLCHAIN_FILE="../cmake/android.toolchain.cmake" -DANDROID_ABI=armeabi-v7a -DANDROID_NATIVE_API_LEVEL=10 -DANDROID_TOOLCHAIN_NAME=arm-linux-androideabi-4.8 ..

   4. Build as usual using your target build system.
6. Build OGRE for Android.
   1. Download the OGRE source code (either via the Mercurial repo or the compressed source archive).
   2. Run CMake from the OGRE build directory. Again, change parameters like you did while building ogredeps to suit your Android target. Assuming you want to build OGRE in the folder ogre/build, run CMake like so:
      Copy to clipboard

      cmake -DCMAKE_TOOLCHAIN_FILE="../CMake/toolchain/android.toolchain.cmake" -DOGRE_DEPENDENCIES_DIR="/path/to/ogredeps/build" -DANDROID_ABI=armeabi-v7a  -DANDROID_NATIVE_API_LEVEL=10 -DANDROID_TOOLCHAIN_NAME=arm-linux-androideabi-4.8 ..

   3. Build as usual using your target build system. Replace "darwin-x86" with the folder corresponding to your host build system. If using the Make build system, you may want to use the version of make included with the NDK.
      Copy to clipboard

      android-ndk/prebuilt/darwin-x86/bin/make)

7. (Optional) Build and install the OGRE SampleBrowser onto your Android device.
   1. Download and install ant (http://ant.apache.org/bindownload.cgi) which will be used to build Android projects from the command line and install them on your device. On most OS, this could be done either manually or using a package manager (including Chocolatey on Windows, MacPorts or Homebrew on Mac OS X, or whatever package manager comes with your Linux distro).
   2. Navigate your command prompt to the SampleBrowserNDK subfolder in your OGRE build folder.
   3. Build the SampleBrowser as a native activity using ndk-build. Optionally use the "-j <# threads>" option — without the quotes of course — for a parallel build.
      Copy to clipboard

      ndk-build all

   4. Attach your Android device to your PC so that a call to 'adb devices' lists the device.
   5. Build a debug APK of the SampleBrowser and install on Android device:
      Copy to clipboard

      ant debug install

8. (Optional) Build and install the OGRE JNI example application, which demonstrates how to interface a C++ OGRE application with a Java Android bridge.
   1. TODO: Fill me in.

Notes on building for Android on Linux host:

Notes on building for Android on Mac OS X host:

Notes on building for Android on Windows host:
Standard NMake can only build one file at a time. For functionality similar to "make -j" (parallel builds), use JOM in place of the "nmake" command above. JOM can be found here: http://qt-project.org/wiki/jom

Here is a sample CMake configuration command for building OGRE for Android on Windows using NMake as the build system and armeabi as the Android ABI (assuming you are building from ogre/build):

cmake -G"NMake Makefiles" -DCMAKE_TOOLCHAIN_FILE=..\CMake\toolchain\android.toolchain.cmake -DOGRE_DEPENDENCIES_DIR="/path/to/ogredeps/build" -DANDROID_ABI=armeabi -DANDROID_NATIVE_API_LEVEL=9 -DANDROID_TOOLCHAIN_NAME=arm-linux-androideabi-4.8 ..