Thanks for your answers, I tried both but it didn't work. However, later it
turned out that both libraries didn't link against exactly the same boost
version, so that was the problem. Now everything works fine :)
--
View this message in context:
http://www.nabble.com/Boost.Python%3A-same-class-i
Verify your library linkage order, because python boost library need
to be the first one, for some reasons of types resolve.
BR
On Tue, Jul 14, 2009 at 12:15 PM, William Ladwig wrote:
> Are you using the static or dynamic version of the boost python library?
> This looks similar to a problem a
Are you using the static or dynamic version of the boost python library? This
looks similar to a problem a coworker had and switching to the dynamic version
of the library fixed his problem. According to the documentation, the dynamic
version of the library "contains a type conversion registry
