[Numpy-discussion] Starting to work on runtime plugin system for plugin (automatic sse optimization, etc...)

Andreas Klöckner lists@informa.tiker....
Tue Apr 29 21:58:35 CDT 2008

On Dienstag 29 April 2008, David Cournapeau wrote:
> Andreas Klöckner wrote:
> > Argh. -1 for a hard dependency on dlopen().
> There is no hard dependency on dlopen, there is a hard dependency on
> runtime loading, because well, that's the point of a plugin system. It
> should not be difficult to be able to disable the plugin system for
> platforms who do not support it, though (and do as today), but I am not
> sure it is really useful.

As long as it's easy to disable (for example with a preprocessor define), I 
guess I'm ok.

> > At some point in my life, I might
> > be forced to compile numpy on an IBM Bluegene/L, which does *not* have
> > dynamic linking at all. (Btw, anybody done something like this before?)
> How will you build numpy in the case of a system without dynamic linking
> ? The only solution is then to build numpy and link it statically to the
> python interpreter. Systems without dynamic linking are common (embedded
> systems), though.

Yes, obviously everything will need to be linked into one big static 
executable blob. I am somewhat certain that distutils will be of no help 
there, so I will need to "roll my own". There is a CMake-based build of 
Python for BG/L, I was planning to work off that.

But so far, I might not end up having to do all that, for which I'd be 
endlessly grateful.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
Url : http://projects.scipy.org/pipermail/numpy-discussion/attachments/20080429/d9ce0306/attachment.bin 

More information about the Numpy-discussion mailing list