Difference between revisions of "Compilation Installation"
m (=Manual Installation=) |
(=Compiling From Sources=) |
||
Line 9: | Line 9: | ||
'''WARNING:''' Make sure you have '''no''' copies of [[wxWidgets]] installed. If you already have [[wxWidgets]] installed, check [[How to uninstall wxWidgets]] before starting a new installation. If you still have problems after this, then [[Check_if_wx_is_installed_twice|check if wx is installed twice]], since that's a common compilation and runtime problem. | '''WARNING:''' Make sure you have '''no''' copies of [[wxWidgets]] installed. If you already have [[wxWidgets]] installed, check [[How to uninstall wxWidgets]] before starting a new installation. If you still have problems after this, then [[Check_if_wx_is_installed_twice|check if wx is installed twice]], since that's a common compilation and runtime problem. | ||
− | '''NOTE:''' In [[wxWidgets]] 2.5.1 | + | '''NOTE:''' In [[wxWidgets]] >= 2.5.1, [[wxBase]] is not distributed as a separate tarball. So if you are going to compile [[wxWidgets|wxGTK]] 2.5.x, skip the second step ([[wxBase]] compilation). |
==== Step 1: [[wxWidgets|wxGTK]] ==== | ==== Step 1: [[wxWidgets|wxGTK]] ==== |
Revision as of 15:46, 22 October 2004
Contents
Manual Installation
To install aMule you can either install it from scratch, as described in Compiling From Sources or use RPMs which will speed things up a lot, as described in the Installing using RPMs section.
NOTE: This HowTo uses wxWidgets 2.4.2 and Crypto++ 5.1, as an example, however aMule can also be compiled using wxWidgets 2.5.x and versions of Crypto++ newer than 5.1. Starting with 2.0.0-rc6, you don't even need Crypto++.
Compiling From Sources
WARNING: Make sure you have no copies of wxWidgets installed. If you already have wxWidgets installed, check How to uninstall wxWidgets before starting a new installation. If you still have problems after this, then check if wx is installed twice, since that's a common compilation and runtime problem.
NOTE: In wxWidgets >= 2.5.1, wxBase is not distributed as a separate tarball. So if you are going to compile wxGTK 2.5.x, skip the second step (wxBase compilation).
Step 1: wxGTK
- download wxGTK ->
- compile wxGTK ->
- tar -zxvf wxGTK-2.4.2.tar.gz
- cd wxGTK-2.4.2
- ./configure --prefix=/usr --disable-gtk2 --with-gtk && make
- tar -zxvf wxGTK-2.4.2.tar.gz
- as root:
- make install
- ldconfig
Step 2: wxBase
- download wxBase ->
- compile wxBase ->
- tar -zxvf wxBase-2.4.2.tar.gz
- cd wxBase-2.4.2
- ./configure --prefix=/usr && make
- as root:
- make install
- ln -sf /usr/bin/wxgtk-2.4-config /usr/bin/wx-config
- ln -sf /usr/bin/wxbase-2.4-config /usr/bin/wxbase-config
- ldconfig
Step 3: Crypto++
Note: Only needed from version 2.0.0-rc1 to 2.0.0-rc5 (included)
- download libcrypto ->
- compile libcrypto ->
- tar xvjf crypto-5.2.1.tar.bz2
- cd crypto-5.2.1
- make
- as root:
- cp libcryptopp.a /usr/lib/
- mkdir /usr/include/cryptopp
- cp *.h /usr/include/cryptopp/
- ldconfig
Step 4: aMule
- download latest aMule version ->
- compile aMule ->
- tar -zxvf aMule-X.X.X.tar.gz (replace X with the right version number..)
- cd aMule-X.X.X
- ./configure --disable-debug --enable-optimise && make
- as root:
- make install
- run aMule as user from your console by typing -> amule
Installing using RPMs
Step 1: wxGTK
- install wxGTK ->
- as root:
- rpm -Uvh wxGTK-2.4.2-1.i386.rpm wxGTK-devel-2.4.2-1.i386.rpm
- ldconfig
- as root:
Step 2: wxBase
- download wxBase ->
- install wxBase ->
- as root:
- rpm -Uvh wxBase-2.4.2-1.i586.rpm
- ln -sf /usr/bin/wxgtk-2.4-config /usr/bin/wx-config
- ln -sf /usr/bin/wxbase-2.4-config /usr/bin/wxbase-config
- ldconfig
- as root:
Step 3. Crypto++
Note: Only needed from version 2.0.0-rc1 to 2.0.0-rc5 (included)
- download libcrypto ->
- as root:
- rpm -Uvh the-above-downloaded-package.rpm
Step 4: aMule
- download latest aMule version ->
- install aMule ->
- as root:
- rpm -Uvh aMule-X.X.X-1.iX86-X.rpm (replace X with the right version number..)
- as root:
- run aMule as user from your console by typing -> amule