Mathias Froehlich wrote:
The other thing I don't get yet, is how osgDB behaves when it wants to load
a plugin.
Either the plugins are searched like usual. But that leaves the discussed
binary compatibility problems.
I've never done this technique, so I can't verify that it works.
To avoid this you have to statically link in the plugins too. The dirty hack
is to reference the plugin proxy installer symbol in the application. Then it
get's linked in and works as usual.
> May be there is a better way for that
> dirty part, but that is what comes in mind to me.
This is only because of OSG's clever but unusual DLL plugin registration technique. If
Win32 static linking were more popular we probably could facilitate this and make it
easier. Perhaps a C-linkage void RegisterFooClass(void) function in each class that would
not need to do anything, simply provide a human-readable symbol that could be referenced
from main() to ensure linkage of the plugin .lib without the crazy mangling and linker
forced refs.
The downside is: you need to know which plugins will be ever needed...
Well, no more so than you needing to know which plugin DLLs to ship with your
application.
Greetings
Mathias
--
Chris 'Xenon' Hanson aka Eric Hammil | http://www.3DNature.com/ eric at logrus
"I set the wheels in motion, turn up all the machines, activate the programs,
and run behind the scenes. I set the clouds in motion, turn up light and
sound,
activate the window, and watch the world go 'round." -Prime Mover, Rush.
_______________________________________________
osg-users mailing list
[email protected]
http://openscenegraph.net/mailman/listinfo/osg-users
http://www.openscenegraph.org/
