From Fedora Project Wiki
(Added missing sections, move to FeatureReadyForWrangler category.)
Line 1: Line 1:
= Windows cross-compiler =
= Windows cross-compiler =
{{Admon/note | This is a proposed feature for Fedora <b>11</b>}}
== Summary ==
== Summary ==
Line 61: Line 59:
== User Experience ==
== User Experience ==
'''FIXME''' -- See other sections?
== Dependencies ==
== Dependencies ==
Line 75: Line 73:
== Release Notes ==
== Release Notes ==
* '''FIXME'''
== Comments and Discussion ==
* See [[Talk:Features/Windows_cross_compiler]]  <!-- This adds a link to the "discussion" tab associated with your page.  This provides the ability to have ongoing comments or conversation without bogging down the main feature page -->

Revision as of 18:33, 18 November 2008

Windows cross-compiler


Build and test full-featured Windows programs, from the comfort of the Fedora system, without needing to use Windows.


Please send any email correspondence about this feature to the fedora-mingw mailing list (you do not need to be subscribed).

Current status

  • Targeted release: Fedora 11
  • Last updated: 2008-10-28
  • Percentage of completion: 20%

Detailed Description

The Fedora MinGW project's mission is to provide an excellent development environment for Fedora users who wish to cross-compile their programs to run on Windows, minimizing the need to use Windows at all. In the past developers have had to port and compile all of the libraries and tools they have needed, and this huge effort has happened independently many times over. We aim to eliminate duplication of work for application developers by providing a range of libraries and development tools which have already been ported to the cross-compiler environment. This means that developers will not need to recompile the application stack themselves, but can concentrate just on the changes needed to their own application.

Benefit to Fedora

There are two primary benefits for Fedora users.

Firstly, developers who are asked to write software for Windows will no longer need to deal with Windows and all the proprietary compilers/software on top of Windows. Instead they can throw a "configure switch" and build (and test) the software without leaving Fedora.

Secondly — and this is the long term goal — it should mean that Windows users can have a greater choice of higher quality open source applications available to them. (Developers who are primarily Linux users will actually be able to produce daily builds for Windows and respond to bug reports from Windows users, so the quality will generally improve). Windows users can use these applications instead of the usual choice of closed, proprietary, expensive apps, giving them at least some freedom. Once they are used to the high quality free applications available, it will be much easier for them to switch to a fully open platform.

The GNU project started out in much the same way by providing much better quality command-line tools for proprietary platforms such as SunOS, and eventually SunOS users liked them so much they switched over to GNU on Linux.


Requires importing the libraries and development tools from our repository.

Test Plan

0. What special hardware / data / etc. is needed (if any)?

No special hardware is needed: it should be possible to test using a standard Fedora installation.

1. How do I prepare my system to test this feature? What packages need to be installed, config files edited, etc.?

The tester should install the mingw32-* packages and wine from Fedora 11. Wine then needs an extra configuration step described in MinGW/Configure wine.

2. What specific actions do I perform to check that the feature is working like it's supposed to?

hg clone
cd fedora-mingw--devel

Look for some application packages. These are marked by having the file NOT-FOR-FEDORA in the subdirectory, meaning the package is not a development tool or library and so cannot be added to Fedora, but is kept as an example or for testing purposes. (An example is Inkscape). In these directories you will find a spec file which will try to cross-compile the application and produce a binary RPM.

Test by attempting to build these applications, then running them under Wine and comparing them to the native Fedora application.

3. What are the expected results of those actions?

The cross-compiled applications, running under Wine, should behave more or less similarly to the same Fedora application running natively.

User Experience

FIXME -- See other sections?



Contingency Plan

No contingency plan is necessary.


Release Notes


Comments and Discussion