Редактирование: Part 1

<h1>Building a Cross compiler for Windows on Linux</h1>

<p>
This is a small How-To on creating a cross compiler for Windows that runs on Linux.
</p>

<h2>Intro</h2>

<p>
Why would one ever do something as stupid as compiling Qt/Windows applications on Linux? There are several (good and better) reasons to do this:
</p>

<ul>
<li>You don't feel <a href="http://silmor.de/24">comfortable</a> working under Windows.</li>
<li>The <a href="http://silmor.de/20">shell</a> on Linux is far more powerful than Windows own cmd.exe.</li>

<li>You don't want to reboot your workstation just to do another compile.<ul>
<li>You don't want to transport your working copy of the source tree on a floppy or memory stick, just because Windows is too dumb to read most Linux file systems.</li>
</ul>
</li>
<li>You don't want to leave your known and comfortable <a href="http://www.kdevelop.org">programming environment</a>.</li>
<li>You don't want to search, download and install your favourite scripting language to do something useful, just because Windows did not deliver it in the base package.</li>
<li>Your Windows is so crippled and restricted that you can't even install simple things (many admins in big companies like this sport).</li>
<li>In short: you don't want to waste good development time.</li>
</ul>

<p>
This article will show you how to create an environment on Linux, so that you don't need to leave it for compiling Windows applications. Unfortunately you'll still need Windows to test these applications.
</p>
<h2>Getting the sources</h2>

<p>
If you installed Qt/Win32 with MinGW before, just copy the MinGW source files (c:\MinGW\src\*.gz) from  Windows to Linux. 
</p>
<p>
Otherwise download the source packages from: <a href="http://mingw.sourceforge.net/download.shtml">http://mingw.sourceforge.net/download.shtml</a>, you'll need these packages (the versions in parenteses are the current ones I tested with, newer ones should work as well):
</p>

<ul>
<li>binutils (2.15.94)</li>
<li>gcc-core (3.4.2)</li>
<li>gcc-g++ (3.4.2, must match gcc-core!)</li>
<li>mingw-runtime (3.7)</li>
<li>w32api (3.2)</li>
</ul>
<p>
</p>
<h2>Creating the MinGW cross-compiler</h2>

<p>
It is assumed that:
<tt><br/>
TARGET=i586-mingw32<br/>
PREFIX=$HOME/mingw
</tt>
</p>
<ol>
<li>Unpack all archives</li>
<li>compile binutils: <br/><tt>./configure --target=$TARGET --prefix=$PREFIX<br/>make &amp;&amp; make install</tt></li>

<li>Copy the header files to the target:<br/><tt>mkdir -vp $PREFIX/include<br/>cp -r mingw-runtime-*/include/* $PREFIX/include<br/>cp -r w32api-*/include/* $PREFIX/include</tt></li>
<li>Compile GCC for C only (you need C for the libs and the libs for C++):<br/><tt>./configure --prefix=$PREFIX --target=$TARGET --enable-threads --enable-languages=c<br/>make &amp;&amp; make install</tt></li>
<li>Compile the Windows API:<br/><tt>./configure --prefix=$PREFIX --target=$TARGET --host=$TARGET --build=$(./config.guess)<br/>make &amp;&amp; make install</tt></li>

<li>Compile the Windows Runtime:<br/><tt> mv w32api-* w32api<br/> cd mingw-runtime*<br/>./configure --prefix=$PREFIX --target=$TARGET --host=$TARGET --build=$(./config.guess)<br/>make &amp;&amp; make install</tt></li>
<li>Re-compile GCC for C &amp; C++:<br/><tt>./configure --prefix=$PREFIX --target=$TARGET --enable-threads --enable-languages=c,c++<br/>make &amp;&amp; make install</tt></li>

</ol>

<p>
It might happen that GCC has problems with linking, the solution is easy:
</p>
<p>
The install scripts create $PREFIX/lib and $PREFIX/$TARGET/lib - move everything from
$PREFIX/$TARGET/lib to $PREFIX/lib and then make the former a link to the latter:<br/><tt>
 cd $PREFIX/$TARGET<br/>
 rmdir lib<br/>
 ln -s ../lib lib</tt>

</p>
<h2>How to proceed</h2>

<p>
From there on you can use the MinGW C/C++ compiler just like any other version of GCC.
</p>
<p>
In <a href="http://silmor.de/38">Part 2</a> of this article I will explain how to cross compile Qt4/Win32.
</p>
<p>
In <a href="http://silmor.de/29">Part 3</a> I will explain how to compile Qt applications using this cross compiler.
</p>