Difference between revisions of "HowTo compile on Win32 with MinGW"

From AMule Project FAQ
Jump to: navigation, search
m (=Installing the Minimal System=)
Line 13: Line 13:
 
'''Note:''' Some of these require manually moving includes and libraries into their correct directories.
 
'''Note:''' Some of these require manually moving includes and libraries into their correct directories.
  
*[http://www.microsoft.com/windows Windows] port of [http://gcc.gnu.org GNU C compiler], MinGW -> [http://prdownloads.sourceforge.net/mingw/MinGW-4.1.1.exe?download Download (4.1.1)]
+
*[http://www.microsoft.com/windows Windows] port of [http://gcc.gnu.org GNU C compiler], [http://www.mingw.org MinGW] -> [http://prdownloads.sourceforge.net/mingw/MinGW-4.1.1.exe?download Download (4.1.1)]
  
*Minimal [http://www.gnu.org GNU] shell for [http://www.microsoft.com/windows Windows], MSys -> [http://prdownloads.sf.net/mingw/MSYS-1.0.10.exe?download Download (1.0.10)]
+
*Minimal [http://www.gnu.org GNU] shell for [http://www.microsoft.com/windows Windows], [http://www.mingw.org/msys.shtml MSys] -> [http://prdownloads.sf.net/mingw/MSYS-1.0.10.exe?download Download (1.0.10)]
  
 
*Developer toolkit for [http://www.mingw.org/msys.shtml MSys] (for [http://www.gnu.org/software/cvs CVS] & co) -> [http://prdownloads.sf.net/mingw/msysDTK-1.0.1.exe?download Download (1.0.1)]
 
*Developer toolkit for [http://www.mingw.org/msys.shtml MSys] (for [http://www.gnu.org/software/cvs CVS] & co) -> [http://prdownloads.sf.net/mingw/msysDTK-1.0.1.exe?download Download (1.0.1)]
Line 32: Line 32:
 
The first step is to create a linux-like environment, which is required in order to be able to perform the build. This can be done by following these steps '''in this order''':
 
The first step is to create a linux-like environment, which is required in order to be able to perform the build. This can be done by following these steps '''in this order''':
  
*Install MinGW. When it prompts you for a folder, the default is slightly messy but the safer selection.
+
*Install [http://www.mingw.org MinGW]. When it prompts you for a folder, the default is slightly messy but the safer selection.
  
*Install MSys. When it prompts you for the MinGW folder, it's very important to specify it correctly. Failure on this step will stop any compilation attempts. If for some reason you fail, install MSys again, or edit the file ''/etc/fstab'' in your MSys environment.
+
*Install [http://www.mingw.org/msys.shtml MSys]. When it prompts you for the [http://www.mingw.org MinGW] folder, it's very important to specify it correctly. Failure on this step will stop any compilation attempts. If for some reason you fail, install [http://www.mingw.org/msys.shtml MSys] again, or edit the file ''/etc/fstab'' in your [http://www.mingw.org/msys.shtml MSys] environment.
  
*Install the MSys developer toolkit.
+
*Install the [http://www.mingw.org/msys.shtml MSys] developer toolkit.
  
*Install LibIConv.
+
*Install [http://www.gnu.org/software/libiconv LibIConv].
  
*Install GetText.
+
*Install [http://www.gnu.org/software/gettext GetText].
  
 
== Compiling the libraries ==
 
== Compiling the libraries ==
  
There are two libraries that aMule will need compiled: zlib and wxWidgets.
+
There are two libraries that [[aMule]] will need compiled: [http://www.zlib.org zlib] and [[wxWidgets]].
  
We will compile them from MSys, so just run it. Once you are running MSys, you'll be on your home folder. Copy the zlib and wxWidgets files you downloaded above into this folder.
+
We will compile them from [http://www.mingw.org/msys.shtml MSys], so just run it. Once you are running [http://www.mingw.org/msys.shtml MSys], you'll be on your home folder. Copy the zlib and wxWidgets files you downloaded above into this folder.
  
 
The steps for compiling them is:
 
The steps for compiling them is:
  
*[http://www.zlib.org zlib]: Uncompress zlib, cd to the newly created directory and run ''./configure --prefix=/mingw && make && make install''
+
*[http://www.zlib.org zlib]: Uncompress [http://www.zlib.org zlib], cd to the newly created directory and run ''./configure --prefix=/mingw && make && make install''
  
*[[wxWidgets]]: Uncompress wxWidgets, cd to the newly created directory and run ''./configure --disable-shared --without-checklistbox && make && make install''
+
*[[wxWidgets]]: Uncompress [[wxWidgets]], cd to the newly created directory and run ''./configure --disable-shared --without-checklistbox && make && make install''
  
If you want to help us developers, you can add ''--enable-debug'' flag to the wxWidgets configure command, right after ''--disable-shared'', but be warned it will result into a > 100Mb aMule.exe.
+
If you want to help us developers, you can add ''--enable-debug'' flag to the wxWidgets configure command, right after ''--disable-shared'', but be warned it will result into an ''aMule.exe'' file bigger than 100MB.
  
 
== Compilation ==
 
== Compilation ==
  
Ok, we're all done with the compilation environment. Let's do the last step: compiling aMule.
+
Ok, we're all done with the compilation environment. Let's do the last step: compiling [[aMule]].
  
The compilation itself is actually just a matter of following the usual method: ''./configure && make''. Use your favorite flags on ./configure, for example, ''--disable-debug'' will remove debug info, but will also make it harder for us developers to understand the bugs you might find.
+
The compilation itself is actually just a matter of following the usual method: ''./configure && make''. Use your favorite flags on ''./configure'', for example, ''--disable-debug'' will remove debug info, but will also make it harder for us developers to understand the bugs you might find.
  
 
You might want to compile just the remote GUI: the flags would be ''--disable-monolithic --disable-ed2k --enable-amule-gui''
 
You might want to compile just the remote GUI: the flags would be ''--disable-monolithic --disable-ed2k --enable-amule-gui''

Revision as of 00:58, 27 August 2005

Originally by Madcat

English | Deutsch

This wiki page only covers the latest CVS version of aMule, not releases in the 1.x.x or 2.x.x branches.

For those of you that don't want to compile aMule from source, there is also the option of the aMule Windows Installer.

Requirements for compiling aMule

Note: Some of these require manually moving includes and libraries into their correct directories.


Installing the Minimal System

The first step is to create a linux-like environment, which is required in order to be able to perform the build. This can be done by following these steps in this order:

  • Install MinGW. When it prompts you for a folder, the default is slightly messy but the safer selection.
  • Install MSys. When it prompts you for the MinGW folder, it's very important to specify it correctly. Failure on this step will stop any compilation attempts. If for some reason you fail, install MSys again, or edit the file /etc/fstab in your MSys environment.
  • Install the MSys developer toolkit.

Compiling the libraries

There are two libraries that aMule will need compiled: zlib and wxWidgets.

We will compile them from MSys, so just run it. Once you are running MSys, you'll be on your home folder. Copy the zlib and wxWidgets files you downloaded above into this folder.

The steps for compiling them is:

  • zlib: Uncompress zlib, cd to the newly created directory and run ./configure --prefix=/mingw && make && make install
  • wxWidgets: Uncompress wxWidgets, cd to the newly created directory and run ./configure --disable-shared --without-checklistbox && make && make install

If you want to help us developers, you can add --enable-debug flag to the wxWidgets configure command, right after --disable-shared, but be warned it will result into an aMule.exe file bigger than 100MB.

Compilation

Ok, we're all done with the compilation environment. Let's do the last step: compiling aMule.

The compilation itself is actually just a matter of following the usual method: ./configure && make. Use your favorite flags on ./configure, for example, --disable-debug will remove debug info, but will also make it harder for us developers to understand the bugs you might find.

You might want to compile just the remote GUI: the flags would be --disable-monolithic --disable-ed2k --enable-amule-gui