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

[Sam U. <sa...@ho...>]

Hi,

 

>>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.

 

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?

 

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

 

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.


 
> From: br...@en...
> To: ope...@li...
> Date: Fri, 2 Jul 2010 02:20:44 -0400
> Subject: Re: [openvrml-develop] parse-vrml97.exe crash
> 
> On Thu, 2010-07-01 at 18:43 -0400, Sam Url wrote: 
> > >>What did you set them to?
> > 
> > 
> > set OPENVRML_DATADIR=C:\openvrml-0.18.6\data 
> > set OPENVRML_NODE_PATH=C:\openvrml-0.18.6\src\node
> > set OPENVRML_SCRIPT_PATH=C:\openvrml-0.18.6\models\rotation_toy.wrl
> > 
> > 
> > 
> > It still crashes on me.
> 
> Again, note the descriptions of these variables in README.
> 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).
> 
> > >> I'm not 100% clear on what this means to you. The provided project
> > >> files build libopenvrml as a DLL. And the node implementations and
> > >> scripting engines all live in plug-in DLLs.
> > 
> > 
> > 
> > I would like to use OpenVRML to open and parse VRML files. Does this require a node/scripting engine?
> 
> If you provide your own semantic actions for the parser, no. (You will,
> however, still need the component descriptors--that's where the parser
> gets its information about how to parse specific nodes.) See
> pretty-print for an example that provides its own semantic actions.
> 
> The parse-vrml97 and parse-x3d test programs use the semantic actions
> that are compiled into libopenvrml--and these create a tree of
> openvrml::nodes using the node implementations.
> 
> You only need a scripting engine if you want to process scripts at
> run-time.
> 
> -- 
> Braden McDaniel <br...@en...>
> 
> 
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Sprint
> What will you do first with EVO, the first 4G phone?
> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
> _______________________________________________
> openvrml-develop mailing list
> ope...@li...
> https://lists.sourceforge.net/lists/listinfo/openvrml-develop
 		 	   		  
_________________________________________________________________
The New Busy think 9 to 5 is a cute idea. Combine multiple calendars with Hotmail. 
http://www.windowslive.com/campaign/thenewbusy?tile=multicalendar&ocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_5