| 4 | |
| 5 | == !OpenSceneGraph == |
| 6 | |
| 7 | To use osgVisual, users have to create a build environment like !OpenSceneGraph. It is recommended not to use precompiled packages but to compile osg from SVN trunk. |
| 8 | Read http://www.openscenegraph.org/projects/osg/wiki/Support/GettingStarted for durther details.[[br]] |
| 9 | Windows user can use the third party requirements as precompiled packages for VS2005 and VS2008 from http://www.openscenegraph.org/projects/osg/wiki/Downloads/Dependencies. |
| 10 | |
| 11 | In short: |
| 12 | * checkout osg SVN trunk |
| 13 | * Linux: "svn co http://www.openscenegraph.org/svn/osg/OpenSceneGraph/tags/OpenSceneGraph-2.9.7 !OpenSceneGraph" |
| 14 | * Windows: TortoiseSVN checkout from svn "http://www.openscenegraph.org/svn/osg/OpenSceneGraph/tags/OpenSceneGraph-2.9.7" |
| 15 | * configure osg |
| 16 | * Linux: "./configure" |
| 17 | * Windows: use CMAKE: "configure" -> set your "Install Prefix" to the same directory as your source code , select your settings, "generate" |
| 18 | * Compile and install osg: |
| 19 | * Linux: "make && make install" |
| 20 | * Windows: "Build ALL" as release and debug |
| 21 | |
| 22 | == osgVisual third party modules == |
| 23 | |
| 24 | osgVisual provides several moduls which rely on commercial third party modules like [http://www.wetzel-technology.com/ Vista2D] or [http://sundog-soft.com Silverlining]. To use this moduls, install the packages and activate the modules during CMAKE configuration. If modules are enabled, further configuration opntions appear after running another "configure" loop. Specify the options (e.g. Silver-lining license information or paths to libraries and include files. |
| 25 | |
| 26 | __It is possible to run osgVisual without any commercial module.__ |
| 27 | |
| 28 | == osgVisual == |