Hi all,
I've an issue concerning the std::ifstream in my application.
I know that I need to use osgDB::ifstream instead of std::ifstream and I
did everywhere in my code.
But, my project links with an other lib than OSG, and this library is
using std::ifstream and std::ofstream, and this results
Hi all,
No advices or ideas ? Am I the only one this this issue
Regards,
Vincent
Le 04/04/2011 17:36, Vincent Bourdier a écrit :
Hi all,
I've an issue concerning the std::ifstream in my application.
I know that I need to use osgDB::ifstream instead of std::ifstream and
I did everywhere
Hi Vincent,
On Mon, Apr 4, 2011 at 4:36 PM, Vincent Bourdier wrote:
> 2>TsLib_MDdNET2010.lib(IwPoly.obj) : error LNK2005: "public: void
> __thiscall std::basic_ifstream
> >::close(void)" (?close@?$basic_ifstream@DU?$char_traits@D@std@@@std@@QAEXXZ)
> already defined in osgDBd.lib(osg65-osgDBd.dl
Hi Mourad
Thanks for your answer but I already checked that. TsLib_MDdNET2010 is a
static lib but linked with /MD(d), like my application...
Vincent.
Le 20/04/2011 11:50, Mourad Boufarguine a écrit :
Hi Vincent,
On Mon, Apr 4, 2011 at 4:36 PM, Vincent Bourdier
mailto:vincent.bourd...@gmail
Hi all,
I just found a fix after some tests, but it is not a fix I am proud of.
I just added the close() method in osgDB/fstream implementation, so
there is no conflict because my fstream implementation uses
osgDB/fstream and not osgDB/fstream AND std::fstream.
I will continue to investigate
Hi,
Sorry to insist but I would appreciate any advices about this issue.
Maybe I'm the only one who encountered it, but the patch I did is not
so... "clean" to my mind...
Thanks.
Regards,
Vincent.
Le 21/04/2011 14:50, Vincent Bourdier a écrit :
Hi all,
I just found a fix after some te
1 11:47 PM
To: osg user
Subject: Re: [osg-users] osgDB ifstream / ofstream conflict
Hi,
Sorry to insist but I would appreciate any advices about this issue. Maybe I'm
the only one who encountered it, but the patch I did is not so... "clean" to my
mind...
Thanks.
Regards,
Vince
s, they tried to reproduce the problem without
> luck...
>
> So if you manage to reproduce this in a small example, go ahead and
> post it. We must make them aware of this problem.
>
>
>
> http://social.msdn.microsoft.com/Forums/en-US/vclanguage/thread/191de00a-53c9-4b
From: osg-users-boun...@lists.openscenegraph.org
[mailto:osg-users-boun...@lists.openscenegraph.org] On Behalf Of
Vincent Bourdier
Sent: Wednesday, 27 April 2011 11:47 PM
To: osg user
Subject: Re: [osg-users] osgDB ifstream / ofstream conflict
Hi,
Sorry to insist but I would appreciate any advices about th
Hi Vincent,
I have been using Visual Studio 2010 and fstreams and OSG DLLs with no issues
at all. The only possibility is you are compiling with incompatible compiler
options between OSG and your other library. All files must be compiled /MD(d)
and of course compiled with Visual Studio 2010.
Hi,
I am now running against the same issue.
I checked to see that everything is compiled with /MD.
I'm trying to build osg 3.2.0 x64 with VS2012
- 3rd-Party Binaries from:
www.helleboreconsulting.com/index.php/open-source/openscenegraph
- OSG built by myself
- my project runs into:
Code:
4>*
Hi Florian,
You can get around the fatal error by adding /FORCE: MULTIPLE to your
linker options.
This seems to be some odd VS2010 and beyond conformance problem.
Basically I get this error in almost any application linking to osgDB
and using fstream. It is somehow related to the derived stre
I had the same problem with VS2010 and there are two ways to get around it.
1. Use /FORCE:multiple
2. Create a typdef:
Code:
#pragma once
// Compatibility layer for VS2010 bug. The compiler tries to link the same
// multiple symbols in for the OSG fstream classes which inherit from the STL
//
Hi,
so far, "/FORCE:multiple" has worked for me.
Thank you!
Cheers,
Florian
--
Read this topic online here:
http://forum.openscenegraph.org/viewtopic.php?p=56555#56555
___
osg-users mailing list
osg-users@lists.openscenegraph.org
14 matches
Mail list logo
