Re: [openvrml-develop] parse-vrml97.exe crash

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

On Fri, 2010-07-02 at 17:35 -0400, Sam Url wrote: 
> >>OPENVRML_NODE_PATH is where you have *compiled* node implementations
> >>(e.g., vrml97.dll). OPENVRML_SCRIPT_PATH is where you have compiled
> >>scripting engines (e.g., javascript.dll).
>  
> Ok, I'm unable to build javascript.dll, because jsapi.h is missing.
> But, as you mentioned, I don't need it if I don't use scripting.

You'll need the XULRunner SDK or SpiderMonkey to build this.

You'd probably benefit from reading this:

        http://sourceforge.net/apps/trac/openvrml/wiki/BuildOpenvrmlOnWindows

> And, I tried to build vrml97.dll, but it says ft2build.h is missing.
> 
>  
> 
> I noticed OPENVRML_ENABLE_RENDER_TEXT_NODE was defined in the proprocessor list,
> so I removed it.  But, I'm still getting compilation errors from text.cpp
> still being dependent on FreeType:
> c:\openvrml-0.18.6\src\node\vrml97\text.cpp(139) : error C2061: syntax error : identifier 'FT_Face'
> 
>  
> 
> Is FreeType required to build vrml97.dll?

Sigh... Yes; but removing that preprocessor symbol definition is
supposed to remove the need for FreeType.  That's a bug.

> And there are 3 projects missing:
> x3d-environmental-effects (unavailable)
> x3d-event-utilities (unavailable)
> x3d-key-device-sensor (unavailable)

This sounds similar to an error someone else reported; but those files
are present in the archive.  I suspect that there's a problem with your
unarchiving program.

> My compiled node .DLLs are located here:
> set OPENVRML_NODE_PATH=C:\openvrml-0.18.6\ide-projects\Windows\VisualC9_0\OpenVRML\Debug\bin\node
> 
>  
> 
> x3d-texturing.dll
> x3d-cad-geometry.dll
> x3d-shape.dll
> x3d-rendering.dll
> x3d-nurbs.dll
> x3d-networking.dll
> x3d-core.dll
> x3d-interpolation.dll
> x3d-h-anim.dll
> x3d-grouping.dll
> x3d-geospatial.dll
> x3d-dis.dll
> x3d-geometry2d.dll
> 
>  
> 
> I was able to compile pretty-print.exe, but this crashes on me too, even after
> setting OPENVRML_NODE_PATH.

I'm going to investigate this.  If you're able to provide me with a
stack trace of where the crash occurs, that will save me some time.  If
you do have this, please file a bug in trac and attach it there.

-- 
Braden McDaniel <br...@en...>