Thanks, Nikolaus However I am still wondering if there is a way to avoid rebuilding the extension when one travel from machine to machine. Of course that should definitely work, but it seems unpractical for many purposes or at least inconvenient. Suppose I want to run some calculations on a cluster using the extension. That means I need the library to be copied on every machine of that cluster (may be I am wrong with this but this is most straightforward way to clone the process). Also this makes lot of potential troubles for other users who would want to work with such extension - do they need to rebuild extension module every time? I hope that there may exist some fancy way to avoid rebuilding the module (also to do this the user would need boost python installed, what may require some extra-work for that user). So if anyone knows if this is still possible - please, let me know. Alexey 2009/12/14 Nikolaus Rath <Nikolaus@rath.org>
Alexey Akimov <alexey.akimov85@gmail.com> writes:
I get confused trying to port my boost python extension module. So I've made a shared object file test.so which actually perfectly works in the original development directory. However, when I copy this file to another Linux machine (I also copy some extra libraries such as
I am not very familiar with Py++ yet, but .so libraries are not supposed to be copied around from machine to machine unless your runtime environment is exactly the same.
You should probably compile test.so (and any other required libraries) on the target machine (i.e., copy the sources and not the binaries from the development system).
Best,
-Nikolaus
-- »Time flies like an arrow, fruit flies like a Banana.«
PGP fingerprint: 5B93 61F8 4EA2 E279 ABF6 02CF A9AD B7F8 AE4E 425C
_______________________________________________ Cplusplus-sig mailing list Cplusplus-sig@python.org http://mail.python.org/mailman/listinfo/cplusplus-sig