Re: [pygccxml-development] Fwd: My log

[Lakin W. <lak...@gm...>]

Right.  I never realized that boost would return error messages in
such a way, but it makes sense.  I will work on this.

Lakin

On 5/28/06, Roman Yakovenko <rom...@gm...> wrote:
> On 5/28/06, Lakin Wecker <lak...@gm...> wrote:
> > I've tried using the boost date_time bindings as an example of how to
> > build the library once the cpp files are generated.  So I copied the
> > sconscript and hacked it to compile the files.  There are some things
> > that need to be fixed in my script, such as the python path is
> > hardcoded, and the cpp path is hardcoded, but I was just hoping to
> > hack together something that works, and then clean it up
> >
> > The following links show you the sconscript I used, and the log is
> > generated from running:
> > scons -f sconscript >& Scons.log
> >
> > http://lakin.weckers.net/ogre/sconscript
> > http://lakin.weckers.net/ogre/Scons.log
> >
> > any thoughts on where I can investigate this?
>
> Yes, you can read it :-).
>
> cpp/Overlay2DElementsIterator.pypp.cpp:26:   instantiated from here
> /usr/include/boost/python/detail/invoke.hpp:88: error: no match for
> call to '(const
> boost::python::detail::specify_a_return_value_policy_to_wrap_functions_returning<Ogre::OverlayContainer*>)
>                                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>   (Ogre::OverlayContainer*)'
>
> You did not set call policies :-(.
>
> from pyplusplus import utils
>
> mb = module_builder_t( ... )
>
> utils.missing_call_policies.print_ ( mb.code_creator )
> utils.missing_call_policies.exclude( mb.code_creator )
>
> Basically next code will print all function, that are missing call policies
> and then will remove them. May be it will work, may be not
> ( hint pure virtual functions ).
>
> > Lakin
> --
> Roman Yakovenko
> C++ Python language binding
> http://www.language-binding.net/
>