Details about this can be found at the testing repository page. Until the remaining packages belonging to the new Fedora MinGW packaging guidelines are imported in Fedora people interested can test this feature using a testing repository. The cross-compiled binaries can be tested using wine Toolchain in earlier Fedora releases can be used to cross-compile packages against this toolchain. The exact same RPM macros and wrapper scripts (like mingw32-configure) as used in the MinGW
The Win32 part of the mingw-w64 toolchain is already part of the Fedora 17 repositories. Most of the steps required to get this in Fedora are also explained at the roadmap page Merge all ported packages from the testing repository back to Fedora in progress.Port the individual mingw-* packages to use this new framework about 70% of all mingw32-* packages are already ported in the testing repository.
Mingw w64 Patch#
Patch all mingw32-* packages which failed to build against the mingw-w64 toolchain done.Rebuild all mingw32-* packages against the mingw-w64 toolchain done.Develop a set of RPM macros to reduce duplication in.Developers can also use the tools from this framework to cross-compile binaries (and test these using wine) for the Win32 and Win64 targetsīefore this feature can land in Fedora several tasks have to be done: This feature makes it easier for packagers to cross-compile packages for both the Win32 and the Win64 targets. We can now merge back all the changes from this testing repository back to Fedora after which the testing repository will disappear As the legal approval arrived at February 22 2012 We had to do all development and testing work in this testing repository. As we were waiting on legal approval for the introduction of mingw-w64 in Fedora This testing repository has already been available for about a year and various members from the Fedora MinGW SIG alreadyĬontributed patches and improvements to it. All packages which require some patching have been identifiedĪnd have already been made operational in a testing repository Most packages compile fine out of the box against the mingw-w64 toolchain. With this framework we will also be able to build binaries for the Win32 target using the mingw-w64 toolchain (instead of the one). These new packages will replace the current mingw32 toolchain packages: mingw32-filesystem, mingw32-binutils, mingw32-gcc, mingw32-w32api and mingw32-crt Several RPM packages have been developed like mingw-binutils, mingw-gcc, mingw-headers and mingw-crt containing all pieces belonging to the mingw-w64 toolchain (which can build binaries for both Win32 as well as Win64). These new packaging guidelines are already approved by the FPC All these macros are explained in the updated MinGW packaging guidelines: Packaging:MinGW_Future. spec files to a minimum and are bundled in the mingw-filesystem package (which will replace mingw32-filesystem). These RPM macros are an attempt to reduce the amount of duplication of. In order to make it easy for packagers to build binaries for multiple targets (from a single source rpm) several RPM macros have been developed. In order to build binaries for the Win64 target we have to switch from the toolchain to the (much better maintained and more complete) mingw-w64 toolchain There has been a demand to also add support for building binaries for the Win64 target. At the moment there are over 110 packages in Fedora which make use of this toolchain (the mingw32-* packages). Several Fedora releases ago support was added to build binaries for the Win32 target using the toolchain ( Features/Windows_cross_compiler). Use the mingw-w64 cross compiler toolchain to build binaries for both Win32 and Win64 targets
0 kommentar(er)
