[osg-users] Fix for Windows version pfb plugin

Here is the corrected CMakeLists.txt file for the Windows XP VisualStudio 8 SP1 version of 'Plug 3d pfb' Performer plugin. INCLUDE_DIRECTORIES( ${PERFORMER_INCLUDE_DIR} ) SET(TARGET_SRC ReaderWriterPFB.cpp ConvertFromPerformer.cpp ) SET(TARGET_H ConvertFromPerformer.h ) IF(MSVC) SE

Re: [osg-users] Compiling Samples through Visual Studio 2005

This can happen if the 'manifest' resource is corrupted. Visual Studio 2005 uses the new Side-by-Side dll versioning scheme of Windows XP and it installs these dll's in C:\WINDOWS\WinSxS\x86_Microsoft.VC80.DebugCRT directories. During the link and post link stage a manifest file is built and

Re: [osg-users] build break...

Yes, that would definitely work. The other alternative which is cleaner is to detect when I'm invoking a virtual method defined in a base class and generate code that casts the object pointer to the base class type before invoking the method. I've got sufficient type information to do that, it's

RE: [osg-users] moving to VS8

> * Has anyone assembled a 3rdParty dependencies package for VS8 along the > lines of 3rdParty_Win32binaries_2005_05_10.zip (which is for VS7.1)? I > don't see it on > http://www.openscenegraph.com/osgwiki/pmwiki.php/Downloads/Dependencies > I put one together (and it was a real pain to do). You

[osg-users] SVN osgWrapper VS2005 warnings

Ok, I know that these 'wrapper' things are created by some kind of code generator program so I can't just fix the code. The fix has to go into the code generator. I saw some messages recently that made me think this area was being worked on. So here are the warning messages, hope this helps

[osg-users] OSG <-> Microsoft philosophical differences

Got a build warning here ... It looks like Microsoft has a philosophical problem with people using the xsgetn() method. Maybe we should add the _SCL_SECURE_NO_WARNINGS define to the build settings for this project. What do you think? J. -- Build started: Project: osgPlugin net, Config

RE: [osg-users] SVN .dsp problems

>Regarding the compilation errors, the VS6 build was a casualty of the >VS2005 64 bit support. See this thread for details: > >http://openscenegraph.org/archiver/osg-users/2006-September/0217.html > > > >If you follow the thread to the end I posted a script which undoes the >64 bit changes and le

[osg-users] SVN .dsp problems

F.Y.I., I just got the 'trunk' version out of SVN and double-clicking the OpenSceneGraph\VisualStudio\OpenSceneGraph.dsw file generates these errors in DevStudio6, SP6. www.cs.utexas.edu/~jss/OSG/error1.jpg www.cs.utexas.edu/~jss/OSG/error2.jpg www.cs.utexas.edu/~jss/OSG/error3.jpg Double-cli

Re: [osg-users] What do you want for the osgviewer example

I don't understand. If you're going to keep the Producer features and file format then why not just keep Producer as well? Or, What the problem with Producer? J. - Original Message - From: "Robert Osfield" <[EMAIL PROTECTED]> To: "osg users" Sent: Thursday, January 11, 2007 3:00 PM

[osg-users] CVS tags vs release mapping?

Hi, I'd like to checkout the source for OpenSceneGraph, OpenThreads, and Producer latest release 1.2 from the CVS server but I don't know what CVS tag corresponds to that release. Right now I'm using the Producer_OpenSceneGraph_BranchPoint tag simply because it is the latest one. Is this rig