On Mon, Mar 31, 2014 at 12:05 PM, Matthew Brett <[email protected]>wrote:
> > that part, yes, but isn't Linux too much of a varying target for there > to be > > any point anyway? > > You mean, the /usr/lib stuff varies too much, so that any copied > dynamic libraries would have little chance of binary compatibility > with the system libs? exactly. > The "usual" way is to put the dll next to where it is needed. I _think_ a > > when a one dll (the pyton extension) is linked to another one, the first > > place windows looks is right next to the one loading it -- same as for > dlls > > linked to main executables. > > I had assumed from [1] is that it's the path of the executable not the > loading DLL that is on the DLL search path, but I might well be wrong > I could be wring, too -- I'm pretty sure I tested this at some point, but It could be getting lost in the fog of memory. I guess, if it was the path of the loading DLL, you'd run into trouble > because you'd likely have python extensions in several directories, > and then you'd need to copy the dependencies into all of them. yup -- not ideal > > The python.org python install has a DLLs directory: > > > > C:\Python27\DLLs > > > > Maybe putting them there with nice long, non-standard names would work. > > Sounds reasonable to me. on that note -- looking at my Python install on Windows, I don't see "C:\Python27\DLLs" in PATH. So there must be some run-time way to tel Windows to look there. Maybe that could be leveraged. This may be a question for distutils-sig or something.... -Chris -- Christopher Barker, Ph.D. Oceanographer Emergency Response Division NOAA/NOS/OR&R (206) 526-6959 voice 7600 Sand Point Way NE (206) 526-6329 fax Seattle, WA 98115 (206) 526-6317 main reception [email protected]
_______________________________________________ NumPy-Discussion mailing list [email protected] http://mail.scipy.org/mailman/listinfo/numpy-discussion
