New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
native build of python win32 using msys under wine. #49204
Comments
this patch uses work from bpo-3871 to get a build of python for win32 /bin/sh.exe is so xxxxing unbelievably slow on msys under wine consequently, given that PC/config.h is perfectly useable on nt, configure must be run as: there is an additional bug in msys /bin/sh which stops python.exe as a result, the build process terminates at: to complete the build, "wineconsole cmd" must be run, cd $(BUILDDIR) stunningly, this does actually work: python.exe is build, other necessary workarounds:
regarding testing: it's all a bit... odd.
overall it's a damn good start - i'm dead impressed with compiling and testing python under wine + msys should help |
Are you seriously requesting inclusion of the file f into Python? It (besides, I personally think that the ability to compile Python with |
Is Msys+Mingw32 (running on a regular Windows) an interesting |
martin, hi, thanks for responding.
so - if graminit and configure _are_ in the main ... but i doubt that, and so graminit and configure "appearing"
the reason why it's a minority platform is because... THERE WASN'T i.e. msys and wine simply have not been good enough - and certainly instead of depending on some xxxxing proprietary piece of double-xxxx sorry about that - just to emphasise how distasteful i find it to basically, it should be pretty clear that now that python _can_ ... but regarding "minority platform"? that's .... really quite it was a _non-existent_ platform until about... yesterday :) |
hi amaury, thanks for responding.
[wine+]msys+mingw32 is used to _build_ python - not depend on it. clarification:
but in either case, you end up with a complete build of python.exe, ... WITHOUT requiring, in any way shape or form, in other words, it's a big damn deal. no more proprietary dependence. ... let me put it this way, martin: if i told richard stallman that
yeeees.... sort-of - but if you do s/#ifdef __CYGWIN__/#if defined you actually have to do s/#ifdef _MSC_VER/#if defined(_MSC_VER) || |
updated patch - also removes quotes removal quotes of graminit and also included is an updated version of bpo-4956 as it's an essential |
It is certainly desirable to be able to build extension modules |
Please trust that Python puts generated files into the repository for
Ok, so feel free to continue to work on it; good luck with |
So what CRT do you link with? Is it msvcrt? Which version? If building with mingw becomes wide-spread, care must |
i can respect that :) for no reason other than if somone says |
i was _just_ beginning to wonder about that, after i saw http://www.mingw.org/wiki/SpecsFileHOWTO aww, _frick_. :) well... it's _going_ to be msvcr80. why don't mingw ship with *sigh*. will get back to you on that one - it may make a difference on |
yeah, and the nice thing is - it works, too! :)
not without modification, it doesn't: bpo-3871 adds "proper" etc. etc.
i tried that a few months ago.
at that point, i decided i'd had enough: i wasn't going to
python setup.py build seems quite happy: rpetrov added .S the only slight issue there is that the assembly file there's been a gcc bugreport raised, to get interoperability GCC issue bpo-36834. |
yaay! here's the regression test log, including some summary: 250 tests OK. 12 tests failed: not baaad :) |
Please understand that MSI is *not* a proprietary installer. So to help Wine, it would be best to write a proper MSI |
http://www.winehq.org/pipermail/wine-users/2006-May/021624.html _drat_. a rebuild of wine, adding a workaround to cope with lack of euuw :) so - that's going to delay things somewhat. i'll test with |
I'm rejecting this patch for the moment, as it seems far from being |
workarounds for a couple of wine bugs, |
updated. incorporating roumen's work as well. |
manifests and rc files for msvcr80 build |
martin, so sorry, i didn't see your comments - no dang hell no i'm regarding graminit.h: graminit.h isn't being removed - i keep editing it so it's a bit irritating to keep having to even see it, so i removed if i accidentally submit its removal please ignore it, entirely. people _are_ tracking the progress of this development, and assisting closing the bug looks... like... i dunno - it's not very helpful, |
Hello everyone, I'm seconding the wish to be able to build Python with MSYS on Win32, It is my understanding that in order to build an extension for Python on Therefore, the choice of compiler affects not only Win32 developers As of now, Microsoft has released its Visual C++ compiler in various Express versions supersede each other, so once a new version is Python binary releases for Win32 use the Visual Studio 2005 compiler, Right now, it's impossible to build an extension using distutils without It takes considerable effort to keep Python/Win32 setup tools compatible A developer wishing to deploy Win32 binaries for his extensions is Cross-building extensions for Python on Unix using Wine is impossible I call this a terrible situation. Cygwin is the second alternative. Building Python using Cygwin makes Python and all its extensions From my perspective, MSYS does deliver. Resulting binaries depend only I would actually very much prefer if the default distribution of Python It's also unnecessary, as you can gather from the following: I mainly develop games and multimedia applications on the Linux I could cross-build these apps on Linux, and test them for Win32 within I would need neither a VC/VS nor a Windows license to support it. I call that a wonderful situation. <offtopic>LKCL: although you are clearly a mad scientist, please do Nevertheless, I see the feature you are trying to implement as trivial |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: