OSG & SVN

These are notes of actions performed - never having used SVN before. I usually download the Windows binaries. At present I am working on a hybrid system - Vista on a MacPro - while I wait for my replacement computer to be built. I have noticed several quirks with this setup in my familiar setup, and of course don't know what to put it down to - The MacOS, or Vista (both are new to me). So I am not optimistic that I will get a clean compile - in fact, it will be a miracle. Nevertheless, I'm getting impatient - let's give it a go, see what happens.


  1. Using TortoiseSVN. I Run it using the Windows start menu and get a message to the effect, "RTFM dork!"
  2. On W:/ create a folder "Repository" and right-click it.
  3. I choose, "Create Repository" thereby initialising /Repository as a repository.
  4. http://www.openscenegraph.org/projects/osg/wiki/Downloads/SVN gives the repository as svn checkout http://www.openscenegraph.org/svn/osg/OpenSceneGraph/trunk OpenSceneGraph
  5. I paste the URL portion "http://www.openscenegraph.org/svn/osg/OpenSceneGraph/trunk" into the Tortoise Checkout Dialogue, with "Trunk", and "Full recursive" selected,
  6. After 3 mins., and an 11.8 Mbyte download, the log reads, "At revision: 8661" And the contents have expanded to 67.3 Mbytes., and I'm wondering what I do next, given that I am not planning on posting major revisions in the next few days.
  7. Does Tortoise handle creating a working copy, or should I copy it manually? And, what about compiling it - the Readme at the top of the directory tree by Robert Osfield says,"
    ...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 install

Under Windows use..."
    So I guess that´s "Make a copy and run Cmake on it to get the Make file."

... which I shall do, although as I said earlier, I am not optimistic given the nature of the stand-in system I am currently using. However, it will be good to try using CMake and CodeBlock even though it may throw up errors which are beyond me to address.
Under Windows use the GUI tool CMakeSetup [... (See wiki:)] http://www.openscenegraph.org/projects/osg/wiki/Support/PlatformSpecifics/VisualStudio

  1. Make a new directory in W:/Programs ( my "Program files" overflow on an external HD - adding further complications if tools use the registry )
  2. Copy everything across.
  3. Download QuickTime 7.1 SDK for Windows Download
    QuickTime 7.1 SDK for Windows contains a set of QuickTime headers, libraries, tools and documentation used when building QuickTime-savvy applications. These include definitions for the new APIs introduced in QuickTime for Windows 7.1.
  4. Then there were MORE 3rd Party files. To download Glut, And all the instructions are for VisualStudio compilation. A feebie, i have downloaded VisualStudio Lite - so I am wondering; prevaricating... Should I go GCC or Visual Studio? Omar uses GCC in Code::Blocks - it would be good if we were using the same tools. I shall try GCC as preferred option, and then if that fails, move to VS. ( Notes say that the version of CMake should be 2.4.8 -
  5. Ground to a halt - CMake couldn't compile a simple C program. Whereas it compiled fine in CodeBlocks. It says something about can't run as.exe which is there - so it must have changed the paths itself?
  6. Read these: http://wiki.codeblocks.org/index.php?title=Installing_a_supported_compiler#MinGW.2FGCC
    http://forums.codeblocks.org/index.php/topic,3550.0.html
    http://www.mail-archive.com/cmake@cmake.org/msg10319.html
    http://www.cmake.org/pipermail/cmake/2007-December/018268.html
    http://www.google.co.uk/search?q=%22unable+to+find+a+build+program%22&ie=utf-8&oe=utf-8&aq=t&rls=org.mozilla:en-GB:official&client=firefox-a

    However, these things are for a later date. There are more pressing things to attend to at the moment.