using something similar to ctypes dlopen?
I would like to be able to create a wrapper for a library that can
built on the client machine without the necessity of the target
libraries being present.
Then, upon import of the library, the library would check for the
presence of the .so's and raise
Chris Colbert wrote:
using something similar to ctypes dlopen?
I would like to be able to create a wrapper for a library that can
built on the client machine without the necessity of the target
libraries being present.
Consider having multiple modules -- say, mylib and mylib.withsolib.
a)
More particularly, i'm going to be working on some opencv
compatibility for scikits.image. The idea is the user can build
scikits.image once, regardless of whether or not OpenCV is currently
on their system. If and when the user does put OpenCV on their system,
then scikits.image.opencv
Chris Colbert wrote:
More particularly, i'm going to be working on some opencv
compatibility for scikits.image. The idea is the user can build
scikits.image once, regardless of whether or not OpenCV is currently
on their system. If and when the user does put OpenCV on their system,
then
On Oct 7, 2009, at 12:31 PM, Dag Sverre Seljebotn wrote:
Chris Colbert wrote:
More particularly, i'm going to be working on some opencv
compatibility for scikits.image. The idea is the user can build
scikits.image once, regardless of whether or not OpenCV is currently
on their system. If and
On Thu, Oct 8, 2009 at 1:45 AM, Chris Colbert sccolb...@gmail.com wrote:
using something similar to ctypes dlopen?
As mentioned by other, it will be hard to do it if you care about
cross-platformness. Linking and loading dynamic binaries is different
on almost every platform. For example,
On Wed, Oct 7, 2009 at 10:42 PM, David Cournapeau courn...@gmail.com wrote:
On Thu, Oct 8, 2009 at 1:45 AM, Chris Colbert sccolb...@gmail.com wrote:
using something similar to ctypes dlopen?
As mentioned by other, it will be hard to do it if you care about
cross-platformness. Linking and
