Welcome to the OpenSceneGraph (OSG).For up-to-date information on the project, in-depth details on how to compile and run libraries and examples, see the documentation on the OpenSceneGraph website: http://www.openscenegraph.org For the impatient, read the simplified build notes below. For support subscribe to our public mailing list: http://www.openscenegraph.org/projects/osg/wiki/MailingListsRobert Osfield.Project Lead.28th July 2009.--How to build the OpenSceneGraph===============================The OpenSceneGraph uses the CMake build system to generate a platform-specific build environment. CMake reads the CMakeLists.txt files that you'll find throughout the OpenSceneGraph directories, checks for installed dependenciesand then generates the appropriate build system.If you don't already have CMake installed on your system you can grab it from http://www.cmake.org, use version 2.4.6 or later. Details on the OpenSceneGraph's CMake build can be found at: http://www.openscenegraph.org/projects/osg/wiki/Build/CMakeUnder unices (i.e. Linux, IRIX, Solaris, Free-BSD, HP-Ux, AIX, OSX) use the cmake or ccmake command-line utils, or use the included tiny configure script that'll run cmake for you. The configure script simply runs 'cmake . -DCMAKE_BUILD_TYPE=Release' to ensure that you get the best performance from your final libraries/applications. cd OpenSceneGraph ./configure make sudo make install Alternatively, you can create an out-of-source build directory and run cmake or ccmake from there. The advantage to this approach is that the temporary files created by CMake won't clutter the OpenSceneGraph source directory, and also makes it possible to have multiple independent build targets by creating multiple build directories. In a directory alongside the OpenSceneGraph use: mkdir build cd build cmake ../OpenSceneGraph -DCMAKE_BUILD_TYPE=Release make sudo make installUnder Windows use the GUI tool CMakeSetup to build your VisualStudio files. The following page on our wiki dedicated to the CMake build system should help guide you through the process: http://www.openscenegraph.org/projects/osg/wiki/Support/PlatformSpecifics/VisualStudioUnder OSX you can either use the CMake build system above, or use the Xcode projects that you will find in the OpenSceneGraph/Xcode directory. See release notes on OSX CMake build below.For further details on compilation, installation and platform-specific information read "Getting Started" guide: http://www.openscenegraph.org/projects/osg/wiki/Support/GettingStarted -- Release notes on OSX build, by Eric Sokolowsky, August 5, 2008There are several ways to compile OpenSceneGraph under OSX. Therecommended way is to use CMake 2.6 to generate Xcode projects, then useXcode to build the library. The default project will be able to buildDebug or Release libraries, examples, and sample applications. Here aresome key settings to consider when using CMake:BUILD_OSG_EXAMPLES - By default this is turned off. Turn this setting onto compile many great example programs.CMAKE_OSX_ARCHITECTURES - Xcode can create applications, executables,libraries, and frameworks that can be run on more than one architecture.Use this setting to indicate the architectures on which to build OSG.Possibilities include ppc, ppc64, i386, and x86_64. Building OSG usingeither of the 64-bit options (ppc64 and x86_64) has its own caveatsbelow.OSG_BUILD_APPLICATION_BUNDLES - Normally only executable binaries arecreated for the examples and sample applications. Turn this option on ifyou want to create real OSX .app bundles. There are caveats to creating.app bundles, see below.OSG_WINDOWING_SYSTEM - You have the choice to use Carbon or X11 whenbuilding applications on OSX. Under Leopard and later, X11 applications,when started, will automatically launch X11 when needed. However,full-screen X11 applications will still show the menu bar at the top ofthe screen. Since many parts of the Carbon user interface are not64-bit, X11 is the only supported option for OSX applications compiledfor ppc64 or x86_64.There is an Xcode directory in the base of the OSG softwaredistribution, but its future is limited, and will be discontinued oncethe CMake project generator completely implements its functionality.APPLICATION BUNDLES (.app bundles)The example programs when built as application bundles only contain theexecutable file. They do not contain the dependent libraries as would anormal bundle, so they are not generally portable to other machines.They also do not know where to find plugins. An environmental variableOSG_LIBRARY_PATH may be set to point to the location where the plugin.so files are located. OSG_FILE_PATH may be set to point to the locationwhere data files are located. Setting OSG_FILE_PATH to theOpenSceneGraph-Data directory is very useful when testing OSG by runningthe example programs.Many of the example programs use command-line arguments. Whendouble-clicking on an application (or using the equivalent "open"command on the command line) only those examples and applications thatdo not require command-line arguments will successfully run. Theexecutable file within the .app bundle can be run from the command-lineif command-line arguments are needed.64-BIT APPLICATION SUPPORTOpenSceneGraph will not compile successfully when OSG_WINDOWING_SYSTEM isCarbon and either x86_64 or ppc64 is selected under CMAKE_OSX_ARCHITECTURES,as Carbon is a 32bit only API. A version of the osgviewer library written inCocoa is needed. However, OSG may be compiled under 64-bits if the X11windowing system is selected. However, Two parts of the OSG defaultdistribution will not work with 64-bit X11: the osgviewerWX exampleprogram and the osgdb_qt (Quicktime) plugin. These must be removed fromthe Xcode project after Cmake generates it in order to compile with64-bit architectures. The lack of the latter means that images such asjpeg, tiff, png, and gif will not work, nor will animations dependent onQuicktime. A new ImageIO-based plugin is being developed to handle thestill images, and a QTKit plugin will need to be developed to handleanimations.
export OPENTHREADS_INC_DIR="/usr/local/OpenThreads/include"export OPENTHREADS_LIB_DIR="/usr/local/OpenThreads/bin"export PRODUCER_INC_DIR="/usr/local/Producer/include"export PRODUCER_LIB_DIR="/usr/local/Producer/bin"
export PATH="/usr/local/OpenSceneGraph/bin:$OPENTHREADS_LIB_DIR:$PRODUCER_LIB_DIR:$PATH"
