A possible option is to install the toolchain inside site-packages and to deploy it as PYPI wheel or wininst packages. The PATH to the toolchain could be extended during import of the package. But I have no idea, whats the best strategy to additionaly install ATLAS or other third party libraries.

Cheers,

Carl


2014-04-27 23:46 GMT+02:00 Matthew Brett <matthew.brett@gmail.com>:
Hi,

On Sun, Apr 27, 2014 at 2:34 PM, Carl Kleffner <cmkleffner@gmail.com> wrote:
> Hi,
>
> I will definitly don't have not time until thursday this week working out
> the github workflow for a numpy pull request. So feel free to do it for me.

OK - I will have a go at this tomorrow.

> BTW: There is a missing feature in the mingw-w64 toolchain. By now it
> features linking to msvcrt90 runtime only. I have do extend the specs file
> to allow linking to msvcr100 with an addional flag. Or create a dedicated
> toolchain - what do you think?

I don't know.

Is this a discussion that should go to the mingw-w64 list do you
think?  It must be a very common feature.

As you know, I'm really hoping it will be possible make a devkit for
Python similar to the Ruby devkits [1].

The ideal would be a devkit that transparently picked up 32 vs 64 bit,
and MSVC runtime according to the Python version.  For example, OSX
compilation automatically picks up the OSX SDK with which the relevant
Python was built.  Do you think something like this is possible?  That
would be a great improvement for people building extensions and wheels
on Windows.

Cheers,

Matthew

[1] http://rubyinstaller.org/add-ons/devkit/
_______________________________________________
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion