Hi Vincent, osgDB Plugins register them self to the db registry. If you take a look into every plugin, there is some kind of proxy global object. The constructor of this get initiated as soon as library is loaded, and in the constructor the plugin register himself to the osgDB. Hence no magic ;)
As to the getProcAddress: as far s I know this is just a wrapper for the getProcAdress of a OS function. So it always returns void. In plugins it isn't used, or at least, I do not remember any plugin which use it. However you can use it for your own things. If you take a look into CUDA example from osgPPU, then you will see how I use that method in order to get the unit module initialized. Cheers, art Vincent.B wrote: > Hi all, > > I've just spent some hours running into the osgDB code, and some littles > things are more clear but there is the big question I cannot answer : > > The method > DynamicLibrary::PROC_ADDRESS DynamicLibrary::getProcAddress(const > std::string& procName) > > is for me the only one which the loader must use each time a plugin dll have > to be loaded. > But, there is no utilization, at no place ! So how can the osgDB core find > the good methods in the dLL without using this method ? > I'm not a c++ master, but for now, I feel lost in the c++ myst ... > ------------------ Read this topic online here: http://forum.openscenegraph.org/viewtopic.php?p=12079#12079 _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
