-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 02/09/2014 12:55 AM, Bengt Gustafsson wrote:
> I get errors for ctors and dtors of std::istream and std::ostream
> when I link my application to the OSG 3.2.0 / VS2013 libraries (if
> I use these classes in my code).
> 
> I think it has to do with the osgDB::istream and osgDB::ostream
> classes which derives from the std variants.
> 
> I took the labour to rename these to db_istream/ostream but it
> didn't help (if it had there would have been some strange bug in VS
> linker). So I ruled that one out at least.
> 
> I also noted that during OSG compilation I got complaints about 
> conflicting MSVCRT libraries from (at least) freefont loader. I
> resolved this according to VS suggestion, but it didn't help
> either.
> 
> Anyone having noticed and solved this problem before?

Are you mixing debug and release libraries?
Or libraries compiled with different versions of MSVC++? That's a
NO-NO with Microsoft's compilers.

That's where you would most likely get these linking errors, because
the debug libraries have their symbols mangled slightly differently.

The MSVCRT warning is also pretty much indication that you are mixing
release and debug runtime somewhere - you must not do that, otherwise
you will get crashes and heap corruption. Microsoft has decided, in
their infinite wisdom, to use a different heap management scheme for
debug and release in order to allow some extra memory access checking
in debug mode. The consequence is memory corruption if you mix debug
and release libraries. This applies not only for OSG but also for all
dependencies, they must be linked correctly.


Regards,

J.


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iD8DBQFS92FEn11XseNj94gRAgasAKDHwF1+p1su9UsSXmgScir0QTgn2gCgxoXp
txNz0eu6fMBZB0SLAjI4ImA=
=/iqK
-----END PGP SIGNATURE-----
_______________________________________________
osg-users mailing list
[email protected]
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Reply via email to