For this we'd want an OS X dylib that's at least 32/64-bit, if not a four-way (intel/ppc 32/64). This should be pretty easy for me to make. We'd also want standalone 32- and 64-bit windows DLLs. And should we have anything for linux, or do we assume that those people can get FreeImage compiled manually or via a package manager easily enough?
I could just package these up as "data" in a python module, and then point ctypes at the right lib based on run-time checks. Maybe silly to distribute extra binaries, but that might be the user-friendliest solution? Other feedback welcome of course.
I think distributing these is a good idea; but I'm a bit hesitant to include the binaries in the source repo. How about we modify the bdist command to fetch these binaries from GitHub, and then store them in their own repo?
That's a decent idea -- and that way, we could only fetch the appropriate binary for each bdist, instead of shipping all of them. Any way to make the install command do this as well, for those who install from source? In either case, though, I'm a bit out of my element in the distutils hackery to make this sort of thing happen... Zach
On Tue, Feb 7, 2012 at 11:38 AM, Zachary Pincus <zachary.pincus@yale.edu> wrote:
That's a decent idea -- and that way, we could only fetch the appropriate binary for each bdist, instead of shipping all of them.
Any way to make the install command do this as well, for those who install from source?
In either case, though, I'm a bit out of my element in the distutils hackery to make this sort of thing happen...
As a start, how about just getting a Python script going for doing the fetching + moving? Once that is done, I think it won't be too hard to get distutils to play along. At worst, we can tell all Windows/Mac users to do from skimage import install_libs install_libs() after installation. Cheers Stéfan
participants (2)
-
Stéfan van der Walt -
Zachary Pincus