openvrml-develop

[openvrml-develop] OpenVRML 0.16.0 vs. Microsoft cl 14.0

[Braden M. <br...@en...>]

I've spent a few frustrating hours trying to get OpenVRML compiled with
Microsoft cl 14.0 (the one that comes with Visual Studio 2005) to work.
And I'm just about to give up.

Code that works with gcc 4.1 and cl 13.1 just doesn't work when compiled
with cl 14.0. Compilation is not the problem; the problems are at
run-time.

What I'm seeing appears to be rather severe memory corruption. (Well, as
if that's ever mild.) The code as it is in CVS doesn't even make it
through static initialization before keeling over. I was able to get
past that with a couple of tweaks (specifically, converting
component_registry and profile_registry to singletons); but that just
led to more bizarre problems.

Because these issues are not evident when building with cl 13.1 or gcc
4.1 and because my valgrind runs on Linux look pretty clean, I am
beginning to think there is something Seriously Wrong with this
compiler.

I'd be very interested in hearing about other folks' experiences with
this compiler; in particular any noted issues with static
initialization.

-- 
Braden McDaniel                           e-mail: <br...@en...>
<http://endoframe.com>                    Jabber: <br...@ja...>

Re: [openvrml-develop] OpenVRML 0.16.0 vs. Microsoft cl 14.0

[Braden M. <br...@en...>]

On Fri, 2006-08-18 at 00:50 -0400, Braden McDaniel wrote:
> I've spent a few frustrating hours trying to get OpenVRML compiled with
> Microsoft cl 14.0 (the one that comes with Visual Studio 2005) to work.
> And I'm just about to give up.

[snip]

Some good news: with the fixes I checked in today, the DLL build of
OpenVRML appears to work. (I have successfully loaded rotation_toy.wrl
with sdl-viewer, at least.)

The problems I was observing seem to appear only when openvrml and
openvrml-gl are built as static libraries. So far, I don't have any
particular insight into those problems, though.

-- 
Braden McDaniel                           e-mail: <br...@en...>
<http://endoframe.com>                    Jabber: <br...@ja...>