OpenSceneGraph

If details below are not sufficient then head over to the openscenegraph.org to the Documentation/GettingStarted and Documentation/PlatformSpecifics sections for more indepth instructions. 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 dependencies and then generates files for the selected build system. If you don't already have CMake installed on your system you can grab it from use version 2.8.0 or later. Details on the OpenSceneGraph's CMake build can be found at: Under Unix-like systems (i.e. Linux, IRIX, Solaris, Free-BSD, HP-UX, AIX, macOS) use the cmake or ccmake command-line utils. Note that cmake . defaults to building Release to ensure that you get the best performance from your final libraries/applications. 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: Under 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: Under macOS 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 macOS CMake build below. There are two ways to compile OpenSceneGraph under macOS. The recommended way is to use CMake to generate Xcode project files and then use Xcode to build the library. The default project will be able to build Debug or Release libraries, examples, and sample applications. The alternative is to build OpenSceneGraph from the command line using make or ninja using the instructions for Unix-like systems above. Here are some key settings to consider when using CMake: BUILD OSG EXAMPLES - By default this is turned off. Turn this setting on to 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. x86 64 is the only supported value for OS versions 10.7. OSG BUILD APPLICATION BUNDLES - Normally only executable binaries are created for the examples and sample applications. Turn this option on if you want to create real macOS .app bundles. There are caveats to creating .app bundles, see below. OSG DEFAULT IMAGE PLUGIN FOR OSX - By default macOS uses the imageio plugin instead of the plugins for the individual file types (e.g. jpg , gif , etc.) to load image file types. The imageio plugin can handle all popular file formats through the ImageIO framework. OSG WINDOWING SYSTEM - You have the choice to use Cocoa, Carbon, or X11 when building applications on macOS. Cocoa is the default for OS versions = 10.5. Carbon and X11 are no longer actively supported, either by Apple or the OSG community. The example programs when built as application bundles only contain the executable file. They do not contain the dependent libraries as would a normal bundle, so they are not generally portable to other machines. They also do not know where to find plugins. An environmental variable OSG 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 location where data files are located. Setting OSG FILE PATH to the OpenSceneGraph-Data directory is very useful when testing OSG by running the example programs. Many of the example programs use command-line arguments. When double-clicking on an application (or using the equivalent "open" command on the command l