compiling problems again

[Krešimir Špes]

Hi,

I'm starting work on the new theora video plugin wrapper and have yet
again encountered build problems.

I have followed the http://wiki.python-ogre.org/index.php/WindowsBuildAuto
article to the letter and using BuildModule have downloaded and
unzipped all dependencies.

The only exceptions are boost (I'm using 1.36.0) and gccxml (I'm
using 0.9 installer provided by Roman).
an unusual thing I've found is that BuildModule does not copy the
indexing suite v2 to boost dir (If you'd like, I can make a patch
which does that in the building process)

so, to sum up, my software versions are:
Python-Ogre SVN HEAD
gccxml 0.9
boost 1.36.0 with indexing suite v2
the rest of the software versions are as BuildModule fetched them

some compiling options:

enivorment.py: _STABLE=True


generating code works like a charm, but compiling has issues. here's
ois's compiling log.out:
-----

cl /nologo /DBOOST_PYTHON_MAX_ARITY=19 /nologo -Zm200 /W3 /wd4675 /TP /
MD /Zc:forScope /EHs /c /Ox /Ob2 /Oi /Ot /Oy /GS- /GR -IF:\pythonogre
\root\usr\include /TP /IF:\pythonogre\boost_1_36_0 /IF:\pythonogre\ois
\includes /IC:\dev\Python25\include /IF:\pythonogre\boost_1_36_0 /c
generated\ois_1.2\AxisVector.pypp.cpp /FoC:\temp
\build_dir_2.5\ois_1.2\AxisVector.pypp.obj

AxisVector.pypp.cpp

F:\pythonogre\boost_1_36_0\boost/python/detail/caller.hpp(235) : error
C2903: 'extract_return_type' : symbol is neither a class template nor
a function template

F:\pythonogre\boost_1_36_0\boost/python/detail/caller.hpp
(231) : while compiling class template member function
'boost::python::detail::py_func_sig_info
boost::python::detail::caller_arity<2>::impl<F,Policies,Sig>::signature
(void)'

with

[

F=boost::python::list (__cdecl *)(std::vector<OIS::Axis>
&,boost::python::indexing::slice),


Policies=boost::python::indexing::detail::postcall_override<boost::python::indexing::default_container_policies>,


Sig=boost::mpl::vector3<boost::python::list,std::vector<OIS::Axis>
&,boost::python::indexing::slice>

]

F:\pythonogre\boost_1_36_0\boost/python/detail/caller.hpp
(169) : see reference to class template instantiation
'boost::python::detail::caller_arity<2>::impl<F,Policies,Sig>' being
compiled

with

[

F=boost::python::list (__cdecl *)(std::vector<OIS::Axis>
&,boost::python::indexing::slice),


Policies=boost::python::indexing::detail::postcall_override<boost::python::indexing::default_container_policies>,


Sig=boost::mpl::vector3<boost::python::list,std::vector<OIS::Axis>
&,boost::python::indexing::slice>

]

F:\pythonogre\boost_1_36_0\boost/python/make_function.hpp
(37) : see reference to class template instantiation
'boost::python::detail::caller<F,CallPolicies,Sig>' being compiled

with

[

F=boost::python::list (__cdecl *)(std::vector<OIS::Axis>
&,boost::python::indexing::slice),


CallPolicies=boost::python::indexing::detail::postcall_override<boost::python::indexing::default_container_policies>,


Sig=boost::mpl::vector3<boost::python::list,std::vector<OIS::Axis>
&,boost::python::indexing::slice>

]

F:\pythonogre\boost_1_36_0\boost/python/make_function.hpp
(111) : see reference to function template instantiation
'boost::python::api::object
boost::python::detail::make_function_aux<boost::python::list(__cdecl *)
(std::vector<_Ty>
&,boost::python::indexing::slice),CallPolicies,boost::mpl::vector3<T0,T1,T2>>
(F,const CallPolicies &,const Sig &)' being compiled

with

[

_Ty=OIS::Axis,


CallPolicies=boost::python::indexing::detail::postcall_override<boost::python::indexing::default_container_policies>,

T0=boost::python::list,

T1=std::vector<OIS::Axis> &,

T2=boost::python::indexing::slice,

F=boost::python::list (__cdecl *)(std::vector<OIS::Axis>
&,boost::python::indexing::slice),


Sig=boost::mpl::vector3<boost::python::list,std::vector<OIS::Axis>
&,boost::python::indexing::slice>

]


etc etc...

[Roman Yakovenko]

On Mon, Jan 19, 2009 at 2:17 PM, Krešimir Špes <kresim...@gmail.com> wrote:
>
> Hi,
>
> I'm starting work on the new theora video plugin wrapper and have yet
> again encountered build problems.
>
> I have followed the http://wiki.python-ogre.org/index.php/WindowsBuildAuto
> article to the letter and using BuildModule have downloaded and
> unzipped all dependencies.
>
> The only exceptions are boost (I'm using 1.36.0) and gccxml (I'm
> using 0.9 installer provided by Roman).
> an unusual thing I've found is that BuildModule does not copy the
> indexing suite v2 to boost dir (If you'd like, I can make a patch
> which does that in the building process)

It is intentional. The rational is described in the following link:
http://sourceforge.net/mailarchive/forum.php?thread_name=7465b6170812092307o25a42fa1w2424fcdf216eb38a%40mail.gmail.com&forum_name=pygccxml-development

Andy and I agreed on such change.

If you want to submit the patch it should be to Py++ :-)

I am planning to integrate indexing suite v2 more smoothly with Py++
and install it ( copy file ) during the code generation process, to
the destination directory. So users will not have to deal with this at
all.

> so, to sum up, my software versions are:
> Python-Ogre SVN HEAD
> gccxml 0.9
> boost 1.36.0 with indexing suite v2
> the rest of the software versions are as BuildModule fetched them
>
> some compiling options:
>
> enivorment.py: _STABLE=True
>
>
> generating code works like a charm, but compiling has issues. here's
> ois's compiling log.out:

Can you post the relevant generated code too and to provide version of
your compiler?

--
Roman Yakovenko
C++ Python language binding
http://www.language-binding.net/

[Krešimir Špes]

I'll upload the generated code to the group.

I'm using Visual C++ express 2008 (forgot to mention in the first post)

[Andy Miller]

Ogre 1.6.1 will be released this week at which point I'll update the build process etc to cope with the changes to boost and Py++ (in all it's a simplification as patching will not be required)..

The intention will also be to tweak the build system to add the Mac fixes that I've implemented on my own system (along with releasing a Mac binary build)

Andy...

2009/1/19 Krešimir Špes <kresim...@gmail.com>

[Krešimir Špes]

Ok, i'll make my own little wrapper for our project until the codebase
stabilizes.

After the 1.6.1 release, it would be a good idea to make a stable
branch that would freeze dependency versions/revisions and concentrate
on bug fixes which would be merged back to the trunk.

On Jan 19, 3:10 pm, "Andy Miller" <nzmill...@gmail.com> wrote:
> Ogre 1.6.1 will be released this week at which point I'll update the build
> process etc to cope with the changes to boost and Py++ (in all it's a
> simplification as patching will not be required)..
> The intention will also be to tweak the build system to add the Mac fixes
> that I've implemented on my own system (along with releasing a Mac binary
> build)
>
> Andy...
>

> 2009/1/19 Krešimir Špes <kresimir.s...@gmail.com>