(1) Yes, Support for MSVC100 (python-3.3 and up) is on the TODO list (2) both toolchains are configured for static linking. No need to deploy: libgcc_s_dw2-1.dll, libgomp-1.dll, libquadmath-0.dll, libstdc++-6.dll, libgfortran-3.dll or libwinpthread-1.dll (3) I decided to create two dedicated toolchains for 32bit and for 64bit Regards, Carl 2014-04-29 11:19 GMT+02:00 Matthew Brett <matthew.brett@gmail.com>:
Hi,
On Mon, Apr 28, 2014 at 10:54 AM, Chris Barker <chris.barker@noaa.gov> wrote:
On Sun, Apr 27, 2014 at 2:46 PM, Matthew Brett <matthew.brett@gmail.com> wrote:
As you know, I'm really hoping it will be possible make a devkit for Python similar to the Ruby devkits [1].
That would be great!
From a really quick glance, it looks like we could almost use the Ruby Devkit, maybe adding a couple add-ons..
Please, Carl correct me if I'm wrong, but I think the main issues are:
1) Linking to the right MSVC runtime for each Python version (seems to need different gcc specs) 2) Static linking - Carl's toolchain does full static linking including C runtimes so we don't need to deal with the DLL path. I'm not sure what the ruby devkit does to solve that.
What do they do for 64 bit?
It looks like they have their own Mingw-w64 toolchain.
Cheers,
Matthew _______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion