Difference between revisions of "Using another wxinstall"

Revision as of 12:45, 25 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 wxGTK source dir:

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

in wxBase source dir:

mkdir ~/aMule
./configure --prefix=~/aMule
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

NOTE: On some distros, instead of --with-wx-config=~/aMule/bin/wx-config you might need to use --with-wx-config=~/aMule/bin/wxgtk-2.4-config

NOTE 2: Sometimes wxBase will overwrite wx-config. You can know if it has done so by running wx-cinfig --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.

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