Hi,
On Tue, 2008-12-02 at 17:59 -0600, Patrick Hartling wrote:
> Marcus Lindblom wrote:
> > Hi,
> >
> > I've coaxed gccxml into fooling OpenSG it is VS9 (I think that would be
> > the way to go, we'll see..), so it doesn't fail on first try.
> >
> > I get the osgmodule_mainheader.h generated and it tries to go on, but
> > that file contains references to some headers I've never seen, and
> > can't find either in OpenSG nor referenced in pyopensg!?!
> >
> > Here's a small sample of the output:
> >
> > OpenSG/OSGShaderVariableMMatrix.h: No such file or directory
> > OpenSG/OSGShaderVariablePnt3f.h: No such file or directory
> > OpenSG/OSGShaderExecutableVarChunk.h: No such file or directory
> > OpenSG/OSGShaderVariableVec4f.h: No such file or directory
> > OpenSG/OSGShaderVariableMatrix.h: No such file or directory
> > OpenSG/OSGColladaGeoInputAttachment.h: No such file or directory
> > OpenSG/OSGShaderVariableBool.h: No such file or directory
> > OpenSG/OSGShaderVariableMReal.h: No such file or directory
> > OpenSG/OSGShaderVariableVec2f.h: No such file or directory
> > OpenSG/OSGShaderProgramVariables.h: No such file or directory
> > OpenSG/OSGShaderProgramVariableChunk.h: No such file or directory
> > OpenSG/OSGShaderVariableFunctor.h: No such file or directory
> >
> > Ideas?
>
> As far as I know, that list of headers is built up from two different
> sources: a static list of files in gen_bindings.py and a dynamically
> generated list based on running GCC-XML. It's possible that the dynamic
> list generation has some assumptions that are out of date with respect
> to new concepts in the OpenSG source tree. What is probably more likely
> is that there are .fcd files in the OpenSG source tree that are not
> being used to generate OpenSG C++ code but are being found and used
> unwittingly by gen_bindings.py to generate bindings for code that does
> not exist.
looks like, these come from the two different (exclusive) shader
frameworks. Dependent on enable_new_shader={True|False} either this one
(new, Source/System/State/Shader) or the old one
(Source/System/State/SHL) is active.
Ideally gen_bindings.py should be aware of the build.info settings and
only take files that are relevant.
If gen_bindings.py is using more something like a find based method to
gather the fcd file the best choice might be to analyze OSGConfigured.h
which should tell you which choices were active at compile time.
kind regards,
gerrit
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Opensg-users mailing list
Opensg-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensg-users
