The ABI changed VERY slightly; name mangling for IIRC partial template specialization was updated to eliminate some ambiguities. So the binaries are link compatible for the most part. I haven't spotted that the name mangling changes affect OpenEXR.
The cross linked standard libraries that Kevin mentions are a big deal though. For that reason, I'd say it would be cleaner to distribute vc7 and vc8 prebuilt versions. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kevin Wheatley Sent: Thursday, June 08, 2006 4:25 AM To: Drew Hess Cc: [email protected] Subject: Re: [Openexr-devel] VS2003 vs. VS2005 C++ ABI Drew Hess wrote: > > Did the C++ ABI change in Visual Studio 2005? Can you compile a C++ > application in VS2005 and link it against C++ static libs and/or DLLs > that were compiled in VS2003? (If not, what about vice versa?) > > I'm trying to figure out whether we need to distribute two > pre-compiled OpenEXR packages for Win32 or just one. Drew, if you compile with 2005 you will get a different runtime linked to those parts of your app for sure (which can cause some problems if you pass memory between runtimes), I tried it with some things here and it 'appeared to work' but it was not a very exhaustive test, so your mileage may vary. I had Qt libraries compiled with 2005 running with 2003 compiled code. Kevin -- | Kevin Wheatley, Cinesite (Europe) Ltd | Nobody thinks this | | Senior Technology | My employer for certain | | And Network Systems Architect | Not even myself | _______________________________________________ Openexr-devel mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/openexr-devel _______________________________________________ Openexr-devel mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/openexr-devel
