On Tue, Aug 25, 2009 at 1:02 PM, William Stein<[email protected]> wrote: > On Tue, Aug 25, 2009 at 9:55 AM, David Cournapeau<[email protected]> wrote: >> On Tue, Aug 25, 2009 at 11:35 AM, Robert >> Bradshaw<[email protected]> wrote: >>> On Aug 25, 2009, at 2:49 AM, Dag Sverre Seljebotn wrote: >>> >>>>>> This is really great: the setup takes a few minutes, and now I don't >>>>>> even have to fire up VirtualBox and spend any time in the >>>>>> godforsaken >>>>>> hell that is Windows to build installers for code with C extensions! >>>>> >>>>> There is no reason for this language, there are a lot of us who like >>>>> Windows, and if you look at the numpy/scipy mailinglist then the only >>>>> build issues are with the hundreds of versions of unix/linux. >>>> >>>> Your statement here in turn provokes me. I'd like to try to stop short >>>> of a flamewar, but I have to say something: >>> >>> Maybe we need a cython-flames list. On a more serious note, thanks to >>> all for keeping the discussion relatively civil. I think the main >>> point above is the excitement that the important target audience >>> using Windows can be more easily supported by those who don't enjoy >>> using it. >>> >>>> I'm always tempted to say that I believe Cython should simply say that >>>> we do not support Windows, or Visual C, until we can AT THE VERY LEAST >>>> find one user who actually use Windows on a daily basis who volunteers >>>> to do the relatively trivial task of testing new releases and >>>> packaging >>>> it for exe distribution about four times a year. >>> >>> >>> I don't think we have to outright drop support, as it seems to mostly >>> work most of the time (the messiness of distuitls is not our issue, >>> as long as we get the .c files right). But it is untested and I would >>> love for someone who knows and uses windows to step up and do testing >>> an packaging. Perhaps much could be automated as above, but I >>> wouldn't even know what I'm looking for. >> >> as long as you are looking for: >> - purely command line >> - don't care about compilers other than mingw >> - don't care about windows x64 >> >> wine is really the best solution IMHO for people who don't enjoy using >> windows. You can test things, install python and quite a few >> dependencies, generate binaries. You should always test the final >> product on windows in the end, though. > > Is it possible these days to build Python from source using mingw + wine?
This I don't know - I just install python from python.org, install mingw in wine, and build numpy/scipy from it. It is literally as easy as downloading the python/mingw binaries, installing them, and modifying one wine config file for mingw to be in wine path. I would avoid building python with mingw, unless you are ready to build everything, as extensions start to be incompatible in quite subtle ways (it will import ok but will crash, for example). cheers, David _______________________________________________ Cython-dev mailing list [email protected] http://codespeak.net/mailman/listinfo/cython-dev
