handling for SWIG 1.3.22 and the SWIG runtime library. SWIG doesn't build a runtime library anymore so a libpivy_runtime.so is created and installed into site-packages as if it's a regular python extension module (in fact, one can import it). the pivy modules are then linked against it by having the runtime_library_path set to python's site-packages directory.
handling for SWIG 1.3.22 and the SWIG runtime library.
SWIG doesn't build a runtime library anymore so a
libpivy_runtime.so is created and installed into site-packages
as if it's a regular python extension module (in fact, one can
import it). the pivy modules are then linked against it by having
the runtime_library_path set to python's site-packages directory.

possible win32 breakage (did not test and verify; removed old swig_py.dll
workaround). macosx definitely will break as it will need a .dylib
instead of an .so for that to work (untested and unverified). (there
is a distinction made on this platform for shared libraries and
runtime extensions).

looooo/pivy,looooo/pivy,looooo/pivy