Difference between revisions of "Using another wxinstall"

From AMule Project FAQ
Jump to: navigation, search
Line 17: Line 17:
 
'''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.
 
'''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]] binnary will be installed in ''~/aMule/bin/'' directory.
+
On the above example, [[aMule]] binary will be installed in ''~/aMule/bin/'' directory.
  
 
Also note that ''--with-wxbase-config=...'' should only be used with [[wxWidgets]] versions prior to 2.5.
 
Also note that ''--with-wxbase-config=...'' should only be used with [[wxWidgets]] versions prior to 2.5.
Line 25: Line 25:
 
''export LD_LIBRARY_PATH=~/aMule/lib:$LD_LIBRARY_PATH''<br>
 
''export LD_LIBRARY_PATH=~/aMule/lib:$LD_LIBRARY_PATH''<br>
 
''export LC_ALL=en_EN.UTF-8''
 
''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 Gentoo Linux.
  
 
Please remember to create [[Backtraces]] and provide them to the [[AMule_devs|aMule development team]].
 
Please remember to create [[Backtraces]] and provide them to the [[AMule_devs|aMule development team]].

Revision as of 22:54, 24 February 2005

English | Deutsch

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 (assuming wxWidgets 2.4.2 and current (=>rc8) aMule).

It is recommended that you read the article about how to compile wxGTK and (optionally, only if installing a wxWidgets version prior to 2.5) how to compile wxBase

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

NOTE: On some distros, instead of --with-wx-config=/home/user/aMule/bin/wx-config you might need to use --with-wx-config=/home/user/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-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.

Also note that --with-wxbase-config=... should only be used with wxWidgets versions prior to 2.5.

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.