Hi Grégory, Thanks for the changes. I've taken these and stripped out the old proxies that you had commented out, and have added USE_FLTRECORDS and a USE_OSGPLUGIN(attr) to the ReaderWriterFLT.cpp in a similar style to how the .osg plugin copes with this issue. I used the command line script:
grep REGISTER_FLTRECORD * -h | grep -v "#define" | sed 's/REGISTER_FLTRECORD/USE_FLTRECORD/g' To general the USE_ list so we can be sure we've caught all entries. The osgstaticviewer example already linked to the OpenFlight plugin so I was able to test the changes out and everything works great - both dynamic and static builds are now able to read for OpenFlight files. Since I've added the USE_OSGPLUGIN(attr) into the ReaderWriterFLT.cpp you no longer need to include it in application. These changes are now checked into svn/trunk. Cheers, Robert. 2009/5/27 Grégory Jaegy <[email protected]>: > Hi, > > > > I had some issues using the open flight plugin when OSG is linked > statically. The issue is similar to the one with the plugins registration > mechanism. > > > > More details about this issue on the forum : > http://forum.openscenegraph.org/viewtopic.php?p=13001 > > > > Attached the modified files (base is OSG 2.8.1 release). > > > > One thing that would need to be improve are the huge number of > “USE_FLTRECORD” macros that need to be used in the host application (see > “user_application.cpp”). I think a way to improve this would be to declare > another macro in one of the OpenFlight header that would declare all these > “USE_FLTRECORD” entries. > > > > You can contact me for any further information ! > > > > Cheers, > > > > Grégory Jaegy > > > > > > _______________________________________________ > osg-submissions mailing list > [email protected] > http://lists.openscenegraph.org/listinfo.cgi/osg-submissions-openscenegraph.org > > _______________________________________________ osg-submissions mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-submissions-openscenegraph.org
