Thanks you all
it works
On Mon, Aug 30, 2010 at 12:23 PM, Jim Bosch wrote:
> On 08/30/2010 10:19 AM, Junwei Zhang wrote:
>>
>> Hi, everyone,
>>
>> I just started study boost.python. and have following problem
>
>
>>
>> g++ boostpy.cc -lpython2.5 -I /usr/include/python2.5 -o boostpy.so
>> -shar
On 08/30/2010 10:19 AM, Junwei Zhang wrote:
Hi, everyone,
I just started study boost.python. and have following problem
g++ boostpy.cc -lpython2.5 -I /usr/include/python2.5 -o boostpy.so -shared
any suggestion?
Two compiler/linker flags: -fPIC and -lboost_python
You may have to app
You need to link with boost python as well.
g++ boostpy.cc -lpython2.5 -lboost_python -I /usr/include/python2.5
-o boostpy.so -shared
should probably do the trick
On Mon, Aug 30, 2010 at 12:19 PM, Junwei Zhang
wrote:
> Hi, everyone,
>
> I just started study boost.python. and have following pro
Hi, everyone,
I just started study boost.python. and have following problem
/boostpy.cc
#include
char const* greet()
{
return "hello, world";
}
BOOST_PYTHON_MODULE(boostpy)
{
using namespace boost::python;
def("greet", greet);
}
g++ boostpy.cc -lpython2.5 -I /usr/include/python2.5
> We had the same problem where one module registered converters for type A and
> B
>
> and another module for type B and C. I do not know if Ralf's solution caters
>for
>
> such situations with mixed types.
Yes, you just have to put B in its own module.
> We ended up having a private map (pa
We had the same problem where one module registered converters for type
A and B and another module for type B and C. I do not know if Ralf's
solution caters for such situations with mixed types.
We ended up having a private map (part of the shared library containing
our converters), so a convert
