Difference between revisions of "Using another wxinstall"

From AMule Project FAQ
Jump to: navigation, search
(needs only be set for runtime, not compiletime)
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:
 
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, 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.3 and current (=>rc7) aMule).
+
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.4.2 and current (=>rc7) aMule).
  
 
in [[wxWidgets]] source dir (don't forget to install the patch!):
 
in [[wxWidgets]] source dir (don't forget to install the patch!):
 
''<pre>
 
''<pre>
 
mkdir ~/aMule
 
mkdir ~/aMule
./configure --prefix=~/aMule --disable-gtk2 --with-gtk --enable-debug --enable-debug_gdb
+
./configure --prefix=~/aMule --disable-gtk2 --with-gtk
 
make && make install
 
make && make install
 
</pre>''
 
</pre>''
Line 12: Line 12:
 
In [[aMule]] source dir:
 
In [[aMule]] source dir:
 
''<pre>
 
''<pre>
./configure --prefix=~/aMule/ --enable-debug --with-wx-prefix=~/aMule --with-wx-config=~/aMule/bin/wx-config
+
./configure --prefix=~/aMule/ --enable-debug --disable-optimize --with-wx-config=~/aMule/bin/wx-config --with-wxbase-config=~/aMule/bin/wxbase-2.4-config
 
make && make install
 
make && make install
 
</pre>''
 
</pre>''

Revision as of 03:29, 10 November 2004

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, 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.4.2 and current (=>rc7) aMule).

in wxWidgets source dir (don't forget to install the patch!):

mkdir ~/aMule
./configure --prefix=~/aMule --disable-gtk2 --with-gtk
make && make install

In aMule source dir:

./configure --prefix=~/aMule/ --enable-debug --disable-optimize --with-wx-config=~/aMule/bin/wx-config --with-wxbase-config=~/aMule/bin/wxbase-2.4-config
make && make install

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
gdb ~/aMule/bin/amule
gdb>handle SIGPIPE nostop noprint pass
gdb>handle SIG32 nostop noprint pass
gdb>set height 0
gdb>run

After aMule crashed, generate a backtrace and post it in the aMule forum:

...
Program received signal SIGSEGV, Segmentation fault.

gdb>bt
gdb>bt full