Difference between revisions of "Using another wxinstall"
From AMule Project FAQ
m (links) |
(according to bt-howto) |
||
| Line 23: | Line 23: | ||
gdb /home/muli/BUILD/bin/amule | gdb /home/muli/BUILD/bin/amule | ||
gdb>handle SIGPIPE nostop noprint pass | gdb>handle SIGPIPE nostop noprint pass | ||
| + | gdb>handle SIG32 nostop noprint pass | ||
gdb>run | gdb>run | ||
</pre>'' | </pre>'' | ||
Revision as of 16:22, 2 August 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.5.2 and current (=>20040801) aMule CVS).
in wxWidgets source dir:
mkdir /home/muli/BUILD ./configure --prefix=/home/muli/BUILD --enable-unicode --enable-gtk2 make && make install
In aMule source dir:
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
To start aMule, you need to explicitely specifiy the LD path each time you run it:
export LD_LIBRARY_PATH=/home/muli/BUILD/lib:$LD_LIBRARY_PATH gdb /home/muli/BUILD/bin/amule gdb>handle SIGPIPE nostop noprint pass gdb>handle SIG32 nostop noprint pass gdb>run
