Just a side note, some Plugins licenses do not allow static linking so you need to check that issue
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Paul Melis Sent: Wednesday, June 18, 2008 10:21 AM To: OpenSceneGraph Users Subject: Re: [osg-users] problem with osg 2.4 stable release Hi J-S, Jean-Sébastien Guay wrote: > Bonjour Arnaud, >> I put the libpng13.dll in the same directory of osgdb_png.dll but in >> visual studio output window the dll is called anytime I try to read a >> png and then unloaded after the operation. > No, libpng13.dll should be in your PATH or in your executable's > directory. The plugins are in OSG_BIN_DIR\osgPlugins-<version>, which > is not on your PATH (and should not be) - OSG loads them directly > which is why it works, but the libpng13.dll needs to be on the DLL > search path. > > It's up to you where you want to put it. I usually put it alongside > osgNN-osg.dll (in my case my OSG_BIN_PATH is on my PATH). If you > include the OSG DLLs alongside your application in an installer, for > example, you should include libpng13.dll alongside the OSG DLLs (not > the plugins). > > Hope this helps, This seems to come up quite often for the Windows users. Would linking against a static version of dependencies like png, jpeg, zlib, etc be a helpful solution? Paul _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
