-
-
Notifications
You must be signed in to change notification settings - Fork 171
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
setup a proper build infrastructure for win32 builds #300
Comments
This is becoming more important so we can ensure that we don't ship vulnerable media libraries (see #544) |
Here are some of the mingw packages we will need, available on Fedora 20:
Things we should be able to compile from the mingw shell:
Potential problems:
Maybe we can mix cross-compilation and native versions? |
OK, here are a few things that do build. Loosely based on the list of dependencies found here for OSX builds.
Things that do not build (yet?): |
2014-04-21 10:14:22: totaam uploaded file
|
With the patch above (found here - see also: cross compiling python for windows with mingw32), I can compile Python 2.7.6! (only it didn't find
Find out that Then we can proceed with the python dependencies using the newly installed |
Trying (and failing) to build a simple extension (
Then I can try to run the build:
Which fails to find |
2014-04-27 13:56:14: antoine commented
|
I think building pygtk2 from source will just be too hard (cross compiling is a no go because of all the extensions that need to be compiled - already hard enough even without the cross compiling part), especially if we need to update some of the libraries for security reasons (ie: So I am closing this as |
Re-opening, GTK3 is going nowhere fast. |
2016-04-25 11:30:25: antoine commented
|
Will follow up in #678. |
Developing on win32 is a nightmare and we rely on far too many sources for all the DLLs we need.
We should setup a cross compile environment based on mingw so that anyone can just follow some simple (?) steps and obtain all the components, built from source, with or without debugging symbols, etc
Including:
etc..
Then we can also automate the build and include that from the buildbot.
This should make the code more reliable/maintainable and may well help in solving a number of ugly win32 tickets:
The text was updated successfully, but these errors were encountered: