Re: [openvrml-develop] A few Questions

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

On Thu, 2010-04-29 at 12:52 +0200, Christian Lang wrote: 
> > Perhaps it was not set correctly.
> >    
> I think it was, because the 0.17.12 version worked fine.

0.17.x does not require this setting.

> Could it be 
> that blanks in the path are a problem?
> I'll try around more tomorrow.

I don't *think* spaces in the path are a problem; but this might be
worth testing.

> >> (By the way there were some minor issues, too:
> >> - in some project folders (like
> >> openvrml-0.18.5\ide-projects\Windows\VisualC9_0\OpenVRML\x3d-cad-geometry)
> >> the *.vcproj file had an incorrect or missing file ending
> >> - in openvrml-0.18.5\src\node\x3d-cad-geometry (and only there) was the
> >> register_node_metatypes.cpp missing, which i got by a google query
> >>      
> > Whoops. :-(
> >
> > I suspect these two bullet points are the same problem.  (If they
> > aren't, could you be more specific about what's going on with the first
> > one?)
> >
> > I will commit a fix to ensure that this file gets distributed in 0.18.6.
> >    
> I was wrong about the first one: in x3d-cad-geometry the vcproj file is 
> alright. But:
> (in the following lines i will refer to subolders of 
> openvrml-0.18.5\ide-projects\Windows\VisualC9_0\OpenVRML)
> 
> in \x3d-environmental-effects it is "x3d-environmental" instead of 
> "x3d-environmental-effects.vcproj"
> in \x3d-event-utilities it is "x3d-event-utilities.vcp" instead of 
> "x3d-event-utilities.vcproj"
> in \x3d-key-device-sensor it is "x3d-key-device-sensor" instead of 
> "x3d-key-device-sensor.vcproj"
> 
> This applies to 
> http://sourceforge.net/projects/openvrml/files/openvrml/0.18.5/openvrml-0.18.5.tar.gz/download
> 
> In the current svn revision the filenames are correct, as i noticed today.

They're correct in the tarball, too:

        $ tar tvf openvrml-0.18.5.tar.gz | grep x3d-environmental-effects[.]vcproj
        -rw-r--r-- braden/users    4598 2009-07-04 17:20 openvrml-0.18.5/ide-projects/Windows/VisualC9_0/OpenVRML/x3d-environmental-effects/x3d-environmental-effects.vcproj
        $ tar tvf openvrml-0.18.5.tar.gz | grep x3d-event-utilities[.]vcproj
        -rw-r--r-- braden/users    5904 2009-07-04 17:20 openvrml-0.18.5/ide-projects/Windows/VisualC9_0/OpenVRML/x3d-event-utilities/x3d-event-utilities.vcproj
        $ tar tvf openvrml-0.18.5.tar.gz | grep x3d-key-device-sensor[.]vcproj
        -rw-r--r-- braden/users    4785 2009-07-04 17:20 openvrml-0.18.5/ide-projects/Windows/VisualC9_0/OpenVRML/x3d-key-device-sensor/x3d-key-device-sensor.vcproj
        
It sounds like there's probably something wrong with the program you're
using to unpack the tarball.  Make sure the program supports the tar pax
format.

> > You built the wrong configuration of FreeType.  Did you build the one
> > specified on the BuildOpenvrmlOnWindows wiki page? (It's possible that
> > page is incorrect; but I can't check it at the moment.)
> >    
> I built the LIB Debug Multithreaded and LIB Release Multithreaded as 
> specified on the wiki page.
> This produces the freetype2312MT_D.lib whereas openvrml wants the 
> freetype2312_D.lib.

Yes, the page was incorrect.  You want the "LIB Release" and "LIB Debug"
configurations.

> Besides, in version 0.17.12 openvrml requires the freetype239MT_D.lib 
> and not the freetype239_D.lib.

Yeah; but I think this is a bug in the 0.17 project files.  The OpenVRML
project files are set up to be built with /MD(d); so its dependencies
should match that.

> > [snip]
> >
> > Hm... Any chance you could use the debugger to check the value of the
> > "urn" variable right before this happens?  (In the
> > openvrml::local::component::add_scope_entry function.)
> >    
> I'll try that tomorrow hopefully.
> > I suspect what has happened here is that OpenVRML has read a component
> > descriptor corresponding to a module that, for some reason, wasn't
> > loaded.  What do you have OPENVRML_NODE_PATH set to?
> >    
> to [blabla]\openvrml-0.18.5\openvrml-0.18.5\src\node

That's probably not correct.  It needs to be set to where the DLL
modules are located (i.e., vrml97.dll, x3d-core.dll, etc.).  Similarly,
OPENVRML_SCRIPT_PATH needs to be set to where the scripting engine
modules live (javascript.dll and java.dll).

> > This could be related to the problem you had with
> > x3d-cad-geometry/register_node_metatypes.cpp.  Can you try the svn
> > sources?
> >
> >          http://svn.openvrml.org/svnroot/openvrml/branches/0.18
> >    
> What is the difference between
> 
> http://svn.openvrml.org/svnroot/openvrml/branches/0.18
> 
> and
> 
> http://svn.openvrml.org/svnroot/openvrml/trunk
> ?

branches/0.18 is what future 0.18.x releases will be made from.  trunk
will become 0.19.0.

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