Difference between revisions of "Compilation Installation"

From AMule Project FAQ
Jump to: navigation, search
(=Step 3. libcrypto=)
(=Manual Compilation=)
Line 1: Line 1:
 
To install aMule you can either install it from scratch, as described in '''Manual Compilation''' or use RPMs which will speed things up a lot, as described in the '''Installing using RPMs''' section.
 
To install aMule you can either install it from scratch, as described in '''Manual Compilation''' or use RPMs which will speed things up a lot, as described in the '''Installing using RPMs''' section.
  
−
== Manual Compilation ==
+
== Manual Installation ==
  
  
 
'''NOTE:''' This HowTo uses [[wxWidgets]] 2.4.2 and [[libcrypto|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.
 
'''NOTE:''' This HowTo uses [[wxWidgets]] 2.4.2 and [[libcrypto|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.
−
 
  
 
=== Compiling from sources ===
 
=== Compiling from sources ===

Revision as of 01:18, 24 July 2004

To install aMule you can either install it from scratch, as described in Manual Compilation or use RPMs which will speed things up a lot, as described in the Installing using RPMs section.

Manual Installation

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.

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 (and only in that version), wxBase is not distributed as a separate tarball. So if you are going to compile wxGTK 2.5.1, skip the first step (wxBase compilation).


Step 1: 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 2: wxGTK

  • compile wxGTK ->
    • tar -zxvf wxGTK-2.4.2.tar.gz
      • cd wxGTK-2.4.2
      • ./configure --prefix=/usr --disable-gtk2 --with-gtk && make
  • as root:
    • make install
    • ldconfig


Step 3: Crypto++

  • compile libcrypto ->
    • tar xvjf crypto-5.1.tar.bz2
    • cd crypto-5.1
    • make
If you have problems compiling with older gcc versions, it can be due to stray DOS newlines in some files. Invoke
file * | grep CRLF | while read file rest; do dos2unix ${file%:}; done
to convert them to UNIX newlines (bash syntax).
  • as root:
    • cp libcryptopp.a /usr/lib/
    • mkdir /usr/include/cryptopp
    • cp *.h /usr/include/cyrptopp/
    • ldconfig


Step 4: aMule

  • 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-optimize && make
  • as root:
    • make install
  • run aMule as user from your console by typing -> amule


Installing using RPMs

Step 1: 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


Step 2: wxGTK

  • install wxGTK ->
    • as root:
      • rpm -Uvh wxGTK-2.4.2-1.i386.rpm wxGTK-devel-2.4.2-1.i386.rpm
      • ldconfig


Step 3. Crypto++

Step 4: aMule

  • install aMule ->
    • as root:
      • rpm -Uvh aMule-X.X.X-1.iX86-X.rpm (replace X with the right version number..)
  • run aMule as user from your console by typing -> amule
Retrieved from "http://wiki.amule.org/t/index.php?title=Compilation_Installation&oldid=963"