OGRE Wiki
Support and community documentation for Ogre3D
Ogre Forums
ogre3d.org
Log in
Username:
Password:
CapsLock is on.
Remember me (for 1 year)
Log in
Home
Tutorials
Tutorials Home
Basic Tutorials
Intermediate Tutorials
Mad Marx Tutorials
In Depth Tutorials
Older Tutorials
External Tutorials
Cookbook
Cookbook Home
CodeBank
Snippets
Experiences
Ogre Articles
Libraries
Libraries Home
Alternative Languages
Assembling A Toolset
Development Tools
OGRE Libraries
List of Libraries
Tools
Tools Home
DCC Tools
DCC Tutorials
DCC Articles
DCC Resources
Assembling a production pipeline
Development
Development Home
Roadmap
Building Ogre
Installing the Ogre SDK
Setting Up An Application
Ogre Wiki Tutorial Framework
Frequently Asked Questions
Google Summer Of Code
Help Requested
Ogre Core Articles
Community
Community Home
Projects Using Ogre
Recommended Reading
Contractors
Wiki
Immediate Wiki Tasklist
Wiki Ideas
Wiki Guidelines
Article Writing Guidelines
Wiki Styles
Wiki Page Tracker
Ogre Wiki Help
Ogre Wiki Help Overview
Help - Basic Syntax
Help - Images
Help - Pages and Structures
Help - Wiki Plugins
Toolbox
Freetags
Categories
List Pages
Structures
Trackers
Statistics
Rankings
List Galleries
Ogre Lexicon
Comments
History: Setting Up An Application - Prelude
View page
Source of version: 3
(current)
%prevogre% In order to run your application, there are various files that need to be locatable by your system. The list below details these files. [[_d] denotes an optional reference to a debug library (ie OgreMain_d.dll instead of OgreMain.dll). These files should be in your working directory, or accessible by an appropriate path. On Mac OS X, your project must be run from an application bundle (aka ".app"), otherwise Ogre will not initialise properly. XCode does this for you automatically, but if you don't use XCode you will have to build the bundle manually. The easiest way to get everything configured is to copy an existing OGRE sample and the media directory into your own working directory. If using Windows, copy all the necessary runtime DLLs to this directory. __Edit plugins.cfg and resources.cfg so that the file locations they contain match this new directory.__ __OGRE Libraries & Files:__ * OGRE libraries (OgreMain[[_d].dll, libOgreMain.so for linux). * plugins.cfg - Text file specifying the rendering libraries available to Ogre (ie DX9, OpenGL). * All the plugin libraries listed in plugins.cfg (you can remove items from plugins.cfg if you don't wish to use them). * resources.cfg - If using the ExampleApplication, a text file specifing paths to materials, textures, models, etc. * OgreCore.zip - Ensure resources.cfg has the proper path to this file if you plan to use the OGRE debug panel or profiler. * Other Resources used in your program (*.zip; *.png; *.particle; *.mesh; ...). __3rd Party Libraries:__ The following packages also need to be installed if building from source (not SDK). The libraries (.lib; .a) and header files (.h) will be required for linking and the runtime libraries (win32 .dll; linux .so) necessary for running. If on the Windows platform, it is highly recommended to use the precompiled dependencies available on [http://www.ogre3d.org/index.php?option=com_content&task=view&id=412&Itemid=132|Source releases]. Grab the correct package for your compiler. These are required: * Zlib: zlib1.dll; libz.so (debian: zlib1g, zlib1g-dev) These are optional: * CEGUI: OgreGUIRenderer[[_d].dll, CEGUIBase[[_d].dll, CEGUITaharezLook[[_d].dll, CEGUIWindowsLook[[_d].dll, xerces-c_2_5_0.dll * CEGUI: libCEGUIBase.so, libCEGUIOgreRenderer.so, libxerces-c.so (debian: libcegui-mk2-0, libcegui-mk2-dev, libxerces26, libxerces26-dev) * Cg: cg.dll; libCg.so (debian: nvidia-cg-toolkit) * OpenEXR: openexr.dll??; (debian: libopenexr-dev libopenexr2 ) * ReferenceApp: ReferenceAppLayer.dll __Extras for Microsoft Visual C++ 6 (SP3+):__ * stlport_vc6[[_stldebug]46.dll * msvcp60[[D].dll * msvcrt[[D].dll __Extras for Microsoft Visual C++.Net 2002:__ * stlport_vc7[[_stldebug]46.dll * msvcp70[[d].dll * msvcr70[[d].dll __Extras for Microsoft Visual C++.Net 2003:__ * msvcp71[[d].dll * msvcr71[[d].dll __Extras for Mingw + STLPort:__ * libstlport[[stlg].5.0.dll * mingwm10.dll !!Environment Settings You may want to register an environment variable pointing at the root of the OGRE installation so you can express all your paths relative to that. It can be easier if you ever move things around or onto a different machine. For information on checking and updating environment variables, see the documentation for [http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/environment_variables.mspx|Windows], [http://www.tldp.org/LDP/gs/node5.html|Linux] and [http://developer.apple.com/documentation/MacOSX/Conceptual/BPRuntimeConfig/index.html|Mac OSX]. * If you downloaded and installed the precompiled OGRE SDK, you should already have an environment variable called 'OGRE_HOME' registered already, pointing at the folder where you installed. If it isn't there you probably installed under a different user, so define OGRE_HOME manually * If you downloaded the source distribution, you should register a new environment variable OGRE_SRC pointing at the 'ogrenew' folder from the OGRE source !!Create A Project File This section is not for extensive compiler/IDE settings. It is only for very short steps to start a new project. This should be very easy to do in any IDE. The source code that will go into the project is below. Create a working directory to store your source code. A standard directory structure separates headers, source files and project files as follows: {CODE(wrap="1")} work_dir include *.h src *.cpp scripts *.vcproj {CODE}
Search by Tags
Search Wiki by Freetags
Latest Changes
One Function Ogre
IDE Eclipse
FMOD SoundManager
HDRlib
Building Ogre V2 with CMake
Ogre 2.1 FAQ
Minimal Ogre Collision
Artifex Terra
OpenMB
Advanced Mogre Framework
...more
Search
Find
Advanced
Search Help
Online Users
129 online users