Ticket #71 (closed: fixed)
MinGW cross compiler guidelines updated for mingw-w64 support
|Reported by:||epienbro||Owned by:||spot|
Right now we already have a set of packages in Fedora which can be used to build binaries for the Win32 target. This set of packages is based on the mingw.org toolchain. This toolchain isn't well maintained anymore (by upstream) and doesn't have support for the Win64 target.
As there's quite a lot of demand for Win64 support these days we (the Fedora MinGW SIG) are planning to introduce the mingw-w64 toolchain in Fedora. This toolchain can build binaries for both the Win32 and the Win64 targets and is much better maintained.
In order to avoid duplication and making things easier for package maintainers we've decided to introduce a set of RPM macros which will assist package maintainers in building binaries for multiple targets from a single .spec file. This means that for example a source rpm named 'mingw-glib2' will generate two binary rpms called 'mingw32-glib2' and 'mingw64-glib2'.
This set of RPM macros is explained at https://fedoraproject.org/wiki/PackagingDrafts/MinGWCrossCompiler. These guidelines will obsolete the original MinGW packaging guidelines. All current mingw32-* packages can be rebuilt against this new toolchain. Only a small amount of mingw32-* packages require patching to build successfully (this has already been prepared in a separate testing repository). There's also a porting guide available for package maintainers who want to port their mingw32-* package to have Win64 support: https://fedoraproject.org/wiki/MinGW/CrossCompilerFramework#Porting_guide_porting_guide
Could you please review and approve these guidelines?
Erik van Pienbroek