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

Revision as of 07:44, 20 February 2008

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

You will need the following packages:

• Windows port of GNU C compiler, MinGW -> Download (5.1.3)
• Minimal GNU shell for Windows, MSys -> Download (1.0.10)
• Developer toolkit for MSys (for CVS & co) -> Download (1.0.1)
• LibIConv (required by gettext) -> Download (1.8)
• GetText (for po files, autogen.sh, etc) -> Download (0.11.5)
• zlib compression library -> Download (1.2.3)
• Windows port of wxWidgets library (knows as wxMSW) -> Download (2.6.1)
• Crypto++ library -> Download(5.5.2)
• aMule's latest release sources or aMule CVS -> Download aMule
• ActivePerl -> Download

Also, 800MB-1500MB free space on your hard disk (around 40MB to download the above packages and the rest for temporary compilation files and installations. The amount of space needed will largely depend on the configuration flags you use).

As a reference, the whole compilation process will take around 3 hours on a medium-high resourced computer.

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:

1. Install MinGW. Select Compact installation unless you know what you are doing. When it prompts you for a folder, the default (C:\mingw) is slightly messy but the safer selection.
2. 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.
3. Install the MSys developer toolkit.
4. Install LibIConv.
5. Install GetText.
6. Install ActivePerl.

Compiling the libraries

There are three libraries that aMule will need compiled: zlib libcrypto 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 (something like C:\msys\1.0\home\user).

The steps for compiling them is as follow: (Hint: If you are using a multi-core system, you can speed up compiling by adding "-jX" after the make command, where X is the number of cores in your system plus one. For instance, ./configure --prefix=/mingw && make -j3 && make install)

1. zlib: Uncompress zlib, cd to the newly created directory and run ./configure --prefix=/mingw && make && make install
2. wxWidgets: Uncompress wxWidgets, cd to the newly created directory and run ./configure --enable-unicode --disable-shared --without-checklistbox && make && make install
3. Libcrypto: Uncompress the Crypto++ libraries (you'll need to create a directory yourself!), cd to the newly created directory and run make && PREFIX=/mingw/ 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.

First of all, extract aMule's sources and enter the newly created folder.

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

Beware: The following programs do not work yet on Windows:

• aMule Daemon: Doesn't even compile.
• CAS: Fails to find the signature file.

Note: To keep the size of the binaries down, you can run strip from within MSys, e.g. find . -name '*.exe' -print | xargs -r strip.

Running

To run the binaries we've created you need mingwm10.dll. This file can be found in C:\MinGW\bin\mingwm10.dll (or whatever path you used to install MinGW).

You now have to place this file in some place so that the binaries find it when they are executed. Here you have three options:

1. Place it in the same folder where the binaries are (if you have them spread in several different folders, copy this file once into each folder. Since it is a very small file, it is not much of a loss).
2. Place it in C:\windows or some other any other path where Windows might look for libraries (such as C:\Windows\System or C:\Windows\System32).
3. Add C:\MinGW\bin (or whatever path you used to install MinGW) to your PATH environment variable.

Now... just run your binaries and have fun with aMule on your Windows box!

Note: By default, the binaries are compiled to C:\MSys\1.0\home\user\amule-2.0.3\src\.

Having different languages

Now aMule will be successfully running, but you will not be able to use any other language but default english.

TO be able to choose between any of the lot of languages aMule is shipped with, from MSys go to aMule's extracted folder and then into po/ folder. Something like the following should do it:

cd
cd amule-2.0.3/po

Now install the languages:

make install-data-yes

This language files are now in C:\MSys\1.0\local\share\locale, so exit MSys, go to C:\msys\1.0\local\share\locale and copy that folder to the folder were you are keeping your compiled amule.exe and amulegui.exe files.

Downloading precompiled win32 version

Keep in mind this is a user contributed build. Install it at your own risk

If you prefer a stable (and more recent) build, you can grab amulegui from the stable 2.1.1 sources here: http://conrausch.elise.no-ip.com/aMuleGUI-2.1.1-all_lang.zip

Again, this is a user contributed build, which you should not trust ;). It works pretty well though. It is a little big (almost 3MB), but it contains the .dll plus all language packs that were available with the release. For problems with this one, please contact conrausch [at] gmx de

Author

Originally by Madcat