HI Manu,
My thought about using C functions would be for them to be unique for
each ReaderWriter i.e :
extern "C" {
void osgdb_ive(void)
{
}
};
Would be added to the ive plugin, and the same goes for the other
plugins. One could possible do this via a macro when doing the proxy
instantiation just to simplify the source code. Could you try this
as a quick hack and let me know how you get on.
The .osg plugin and its dozens of DotOsgWrappers is more of a
challenge, but will be solvable using something similar.
Robert.
On 5/24/07, Emmanuel Roche <[EMAIL PROTECTED]> wrote:
Well, things aren't going that well unfortunately:
I've just realize that every plugin that use even a single
RegisterDotOsgWrapperProxy return the exact SAME symbol for this object...
and I cannot find anyway to tell gcc to include the same symbol from
multiple libraries (or worse from multiple objets files in a single library
in the case of osg...): This means for example that we can't link with
osgdb_osgText and osgdb_osgFX at the same time for example... :'(
concerning the automation of the process, indeed, it's quite heavy... but I
doubt there is any C function to retrieve the mangled name internally
the best solution would be to use small scripts just after core and plugins
libs construction to find all the needed symbols and then to include them
for each sample...
and for other projets... hmm... well... we can still use the generated
symbols but I don't see anything better for the moment :-)
Manu.
2007/5/24, Robert Osfield < [EMAIL PROTECTED]>:
>
> Hi Many,
>
> On 5/24/07, Emmanuel Roche <[EMAIL PROTECTED]> wrote:
> > Hmmm yet it works fine for plugin with their single
> > RegisterReaderWriterProxy object !! :-)
> >
> > --> I managed to start osgviewer with a .ive file !!! :-D
> >
> > So considering the symbol lists I already have for windows I would say
that
> > the only "problematic" plugins (in the "common" and "image" series at
least)
> > are osg and osgParticle
>
> Good to hear that you've made further progress. It would be nice to
> be able to automate some of this leg work. I do also wonder about the
> possibility of use a C functions in the plugins to allow one to grab
> the sybmol with the name manging, this might help the process of
> making things more automated.
>
> W.r.t .osg plugin and others of its type they all use an proxy
> mechanism for registering the ReaderWriter (read.write files) and the
> DotOsgWrappers (read/write the objects), its the later which is
> different from the rest of the plugins.
>
> Robert.
> _______________________________________________
> osg-users mailing list
> osg-users@openscenegraph.net
> http://openscenegraph.net/mailman/listinfo/osg-users
> http://www.openscenegraph.org/
>
_______________________________________________
osg-users mailing list
osg-users@openscenegraph.net
http://openscenegraph.net/mailman/listinfo/osg-users
http://www.openscenegraph.org/
_______________________________________________
osg-users mailing list
osg-users@openscenegraph.net
http://openscenegraph.net/mailman/listinfo/osg-users
http://www.openscenegraph.org/
