JDJMSon wrote:
>
> Neal Becker wrote:
>
>> Shouldn't that be:
>> .def("TestFunction",&TestClass::TestFunction)
>> > ;
>
>
> Yes, you're right, but I'm still getting the error. I'm using a
> prebuilt python library, so later I'm going to rebuild python myself
> and see if that helps, as has bee
Neal Becker wrote:
> Shouldn't that be:
> .def("TestFunction",&TestClass::TestFunction)
> > ;
Yes, you're right, but I'm still getting the error. I'm using a
prebuilt python library, so later I'm going to rebuild python myself
and see if that helps, as has been suggested.
Thanks.
--
http://ma
JDJMSon wrote:
> I was wondering if someone here could help me with a problem I'm having
> building Python extensions with the Boost.Python library.
> Basically, if I have a wrapper class with something like this:
>
> string TestFunc()
> {
> return "Hello World";
> }
>
> BOOST_PYTHON_MODULE(Test
I believe this is more of a tools/compiler issue than a coding issue.
If you are using the pre-built BOOST.Python library you get compile
mismatches. I am not a Windows Visual Studio programmer (barely a
programmer), I am probably not using the correct terminology.
There are some settings for th
I was wondering if someone here could help me with a problem I'm having
building Python extensions with the Boost.Python library.
Basically, if I have a wrapper class with something like this:
string TestFunc()
{
return "Hello World";
}
BOOST_PYTHON_MODULE(TestClass)
{
def("TestFu
