Hi Lilinx,
The RegisterDotOsgWrapperProxy objects are the proxy mechanism that I
mentioned in my previous email. The ReaderWriter's have a similar
proxy object mechanism, and this one also only works properly when
using dynamic libraries as they symbols are not exported. This is
actually by desi
hi all,
when we use static lib osgdb_osg_s.lib, may be some global vars in other
cpp files,
e.g, RegisterDotOsgWrapperProxy g_CameraProxy in Camera.cpp are not
exported?
or we can't depend on global var initializtion before the main function
when we use
static lib?
hi,Robert Osfield!
I add some debug info in ReaderWriterOSG.cpp:
osg::notify(osg::NOTICE)<<"lilinx test something"
>There certainly looks like an issue with auto registration via proxy
>objects, both .osg and .flt plugins use it.
>
>Robert.
>
>On Mon, Dec 8, 2008 at 4:58 PM
Hi Lilinx,
There certainly looks like an issue with auto registration via proxy
objects, both .osg and .flt plugins use it.
Robert.
On Mon, Dec 8, 2008 at 4:58 PM, Lilinx <[EMAIL PROTECTED]> wrote:
> hi ,Robert Osfield
>
>yes, write to ive succeds.
>read osg was also failed.
>
>I
hi ,Robert Osfield
yes, write to ive succeds.
read osg was also failed.
I also test the flt plugin using a flt file lost texture files, the output
info is:
Unknown record, opcode=1 size=324
Unknown record, opcode=32 size=4228
Unknown record, opcode=113 size=84
Unknown record
Hi Lilinx,
Static linking of OSG is still a bit bleeding edge, and a path not
often walked so a few teething problems are likely till we get more
exposure of this type of build - so you're feedback is very useful :-)
To home in what the problem is we'll need to follow up on a couple of
different
hi, all
I write a simple app to write out osg file using static library as
follows( write to ive is right ):
I use windows, vs 2003, osg 2.6.
The static lib name : osgdb_osg_s.lib, osgdb_ive_s.lib ...
#include ...
#pragma comment (lib, ...)
7 matches
Mail list logo