Difference between revisions of "Using another wxinstall"

From AMule Project FAQ
Jump to: navigation, search
(just a stub)
 
m (Corrected Spelling of Español in language selection)
 
(33 intermediate revisions by 18 users not shown)
Line 1: Line 1:
If there's already a version of [[wxWidgets]] installed, but you want aMule to use another (probably newer one), here are the steps to follow:
+
<center>
 +
'''English''' |
 +
[[Using another wxinstall-de|Deutsch]] |
 +
[[Using_another_wxinstall-es|Espa&ntilde;ol]]
 +
</center>
  
First, create the target directory, where wxWidgets and aMule will reside (they don't need to be in the same dir, but it makes life easier). Then configure wxWidgets and aMule accordingly (assuming wxWidgets 2.5.2 and current (=>20040801) aMule CVS).
+
If there's already a version of [[wxWidgets]] installed, but you want [[aMule]] to use another (probably newer) one, here are the steps to follow:
  
in wxWidgets source dir:
+
First, create the target directory (in this article, as an example, ''~/aMule/'' will be used), where [[wxWidgets]] and [[aMule]] will reside (they don't need to be in the same dir, but it makes life easier). Then configure [[wxWidgets]] and [[aMule]] accordingly.
''<pre>
+
mkdir /home/muli/BUILD
+
./configure --prefix=/home/muli/BUILD --enable-unicode --enable-gtk2
+
make && make install
+
</pre>''
+
  
In aMule source dir:
+
It is recommended that you read the article about [[Compilation_Installation#Step_1:_wxGTK|how to compile wxGTK]]
''<pre>
+
export LD_LIBRARY_PATH=/home/muli/BUILD/lib:$LD_LIBRARY_PATH
+
./configure --prefix=/home/muli/BUILD --enable-debug --with-wx-prefix=/home/muli/BUILD --with-wx-config=/home/muli/BUILD/bin/wxgtk2u-2.5-config
+
make && make install
+
</pre>''
+
  
To start aMule, you need to explicitely specifiy the LD path each time you run it:
+
In [[aMule]] source dir:<br>
 +
''./configure --prefix=/home/'''user'''/aMule/ --enable-debug --disable-optimize --with-wx-config=/home/'''user'''/aMule/bin/wx-config''<br>
 +
''make && make install''
  
''<pre>
+
'''NOTE 2:''' Sometimes [[wxBase]] will overwrite ''wx-config''. You can know if it has done so by running ''wx-config --basename''. It should show ''wx_gtk''. If it doesn't, please reinstall [[WxWidgets|wxGTK]] so it will overwritte ''wx-config'' to link it to the [[WxWidgets|wxGTK]] file.
export LD_LIBRARY_PATH=/home/muli/BUILD/lib:$LD_LIBRARY_PATH
+
 
gdb /home/muli/BUILD/bin/amule
+
On the above example, [[aMule]] binary will be installed in ''~/aMule/bin/'' directory.
gdb>handle SIGPIPE nostop noprint pass
+
 
gdb>run
+
To start [[aMule]], you need to explicitely specifiy the LD path each time you run it:
</pre>''
+
 
 +
''export LD_LIBRARY_PATH=~/aMule/lib:$LD_LIBRARY_PATH''<br>
 +
''export LC_ALL=en_EN.UTF-8''
 +
 
 +
'''NOTE 3:''' On some systems the above export command does not work, you have instead to run<br>
 +
''export LD_LIBRARY_PATH=~/aMule/lib/:$LD_LIBRARY_PATH''<br>
 +
This has been observed on [[Debian]] and [http://www.gentoo.org Gentoo Linux].
 +
 
 +
Please remember to create [[Backtraces]] and provide them to the [[AMule_devs|aMule development team]].

Latest revision as of 14:57, 24 September 2008

English | Deutsch | Español

If there's already a version of wxWidgets installed, but you want aMule to use another (probably newer) one, here are the steps to follow:

First, create the target directory (in this article, as an example, ~/aMule/ will be used), where wxWidgets and aMule will reside (they don't need to be in the same dir, but it makes life easier). Then configure wxWidgets and aMule accordingly.

It is recommended that you read the article about how to compile wxGTK

In aMule source dir:
./configure --prefix=/home/user/aMule/ --enable-debug --disable-optimize --with-wx-config=/home/user/aMule/bin/wx-config
make && make install

NOTE 2: Sometimes wxBase will overwrite wx-config. You can know if it has done so by running wx-config --basename. It should show wx_gtk. If it doesn't, please reinstall wxGTK so it will overwritte wx-config to link it to the wxGTK file.

On the above example, aMule binary will be installed in ~/aMule/bin/ directory.

To start aMule, you need to explicitely specifiy the LD path each time you run it:

export LD_LIBRARY_PATH=~/aMule/lib:$LD_LIBRARY_PATH
export LC_ALL=en_EN.UTF-8

NOTE 3: On some systems the above export command does not work, you have instead to run
export LD_LIBRARY_PATH=~/aMule/lib/:$LD_LIBRARY_PATH
This has been observed on Debian and Gentoo Linux.

Please remember to create Backtraces and provide them to the aMule development team.