<?xml version="1.0"?>
<?xml-stylesheet type="text/css" href="http://test.amule.szerverem.hu/w/skins/common/feed.css?303"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
		<id>http://test.amule.szerverem.hu/w/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Ken</id>
		<title>AMule Project FAQ - User contributions [en]</title>
		<link rel="self" type="application/atom+xml" href="http://test.amule.szerverem.hu/w/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Ken"/>
		<link rel="alternate" type="text/html" href="http://test.amule.szerverem.hu/wiki/Special:Contributions/Ken"/>
		<updated>2026-04-05T16:48:15Z</updated>
		<subtitle>User contributions</subtitle>
		<generator>MediaWiki 1.23.3</generator>

	<entry>
		<id>http://test.amule.szerverem.hu/wiki/HowTo_compile_on_Mac</id>
		<title>HowTo compile on Mac</title>
		<link rel="alternate" type="text/html" href="http://test.amule.szerverem.hu/wiki/HowTo_compile_on_Mac"/>
				<updated>2005-11-10T22:57:18Z</updated>
		
		<summary type="html">&lt;p&gt;Ken: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;How to get and install [[aMule]] on [http://www.apple.com/macosx/ Apple Mac OS X].&lt;br /&gt;
&lt;br /&gt;
# You can simply download the finished application ('binary release') or &lt;br /&gt;
# You compile it from a [[aMule CVS|CVS source snapshot]].&lt;br /&gt;
&lt;br /&gt;
''The preceding version of this page covering [[aMule]] 2.0.0rc8 and earlier is archived [[HowTo_compile_on_Mac_v200rc8|here]].''&lt;br /&gt;
&lt;br /&gt;
== Binary releases ==&lt;br /&gt;
&lt;br /&gt;
If you don't want to bother with installing and compiling all those tools and sources, then get one of the pre-compiled [[aMule]] applications. The official release is considered 'stable', but every now and then applications are built from the current source to allow more people to test new features or the like. &lt;br /&gt;
&lt;br /&gt;
# Latest official binary release: [http://www.amule.org/files/download.php?file=72 aMule-2.0.0-Mac]&lt;br /&gt;
# Periodically compiled binary from cvs: [http://forum.amule.org/thread.php?threadid=5051 amule forum]&lt;br /&gt;
&lt;br /&gt;
== Compiling from source ==&lt;br /&gt;
&lt;br /&gt;
Compiling from source allows most current bug reports, because you can compile and test the [[aMule CVS|CVS snapshot]] of the very day.&lt;br /&gt;
&lt;br /&gt;
To compile [[aMule]] from source you need some development tools, the [[wxWidgets]] library and the [http://dl.amule.org aMule source].&lt;br /&gt;
&lt;br /&gt;
=== Get the sources and development tools ===&lt;br /&gt;
&lt;br /&gt;
==== [http://developer.apple.com/tools/xcode Xcode] ====&lt;br /&gt;
&lt;br /&gt;
[http://developer.apple.com/tools/xcode Xcode] is [http://www.apple.com Apple]'s development environment. We need it for the [http://gcc.gnu.org GCC] compiler. You may have [http://developer.apple.com/tools/xcode Xcode] on CD/DVD, e.g. it is on the [http://www.apple.com/macosx/ OS X] 10.4 DVD.&lt;br /&gt;
&lt;br /&gt;
Otherwise, you can download it from [http://www.apple.com Apple], but you must sign up for a free-of-charge developer account first.&lt;br /&gt;
&lt;br /&gt;
# Get XCode from http://developer.apple.com/tools/download&lt;br /&gt;
# &amp;quot;Member Site&amp;quot;-&amp;gt;&amp;quot;Log In&amp;quot;-&amp;gt;&amp;quot;Download Software&amp;quot;-&amp;gt;&amp;quot;Developer Tools&amp;quot;-&amp;gt;&amp;quot;Download Xcode Tools last release&amp;quot;&amp;gt;&amp;quot;Install&amp;quot;&lt;br /&gt;
&lt;br /&gt;
==== [http://fink.sourceforge.net Fink] ====&lt;br /&gt;
&lt;br /&gt;
'''Optional:''' [http://fink.sourceforge.net Fink] and [http://www.gnu.org/software/gettext gettext] are not strictly required to compile [[aMule]], but without them [[aMule]] will only appear in english.&lt;br /&gt;
&lt;br /&gt;
[http://fink.sourceforge.net Fink] is an open source installer for lots of open source tools ported to [http://macos.apple.com Mac OSX]. We need it to install the open source tool [http://www.gnu.org/software/gettext gettext].&lt;br /&gt;
&lt;br /&gt;
# Get [http://fink.sourceforge.net Fink] from http://fink.sourceforge.net/download&lt;br /&gt;
# Read [http://fink.sourceforge.net/download Fink's installation guide] to learn how to install applications through [http://fink.sourceforge.net Fink].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== [http://www.gnu.org/software/gettext gettext] ====&lt;br /&gt;
&lt;br /&gt;
'''Optional:''' [http://www.gnu.org/software/gettext gettext] and [http://fink.sourceforge.net Fink] are not strictly required to compile [[aMule]], but without them [[aMule]] will only appear in english.&lt;br /&gt;
&lt;br /&gt;
[http://www.gnu.org/software/gettext gettext] is an open source library for text internationalization. This library is used to make [[aMule]] multi-lingual.&lt;br /&gt;
# Get and install the [http://www.gnu.org/software/gettext gettext] library with [http://fink.sourceforge.net Fink]. The package name is [http://www.gnu.org/software/gettext gettext]. &lt;br /&gt;
&lt;br /&gt;
==== [[wxWidgets|wxMac]] ====&lt;br /&gt;
&lt;br /&gt;
[[wxWidgets|wxMac]] is the port of the [[wxWidgets]] library for [http://macos.apple.com Mac OSX]. This library is used to make [[aMule]] 'multi-platform'.&lt;br /&gt;
&lt;br /&gt;
# Get the source from: http://prdownloads.sourceforge.net/wxwindows/wxMac-2.6.1.tar.gz&lt;br /&gt;
# Extract the archive (just double-click it)&lt;br /&gt;
&lt;br /&gt;
Or get the current [[wx-cvs|CVS snapshot]]. Warning: the [[wxMac]] [[wx-cvs|CVS]] is frequently in a bad condition.&lt;br /&gt;
&lt;br /&gt;
 bash: cd ~/Desktop&lt;br /&gt;
 bash: cvs -d :pserver:anoncvs@cvs.wxwidgets.org:/pack/cvsroots/wxwidgets login&lt;br /&gt;
 Note: password is 'anoncvs'&lt;br /&gt;
 bash: cvs -d :pserver:anoncvs@cvs.wxwidgets.org:/pack/cvsroots/wxwidgets checkout wxMac&lt;br /&gt;
&lt;br /&gt;
==== [http://www.amule.org aMule itself] ====&lt;br /&gt;
&lt;br /&gt;
# Get latest daily [[aMule CVS|CVS source snapshot]]: [http://www.amule.org/files/download.php?file=5 aMule CVS]&lt;br /&gt;
# Extract the archive (just double-click it)&lt;br /&gt;
&lt;br /&gt;
=== Compile the sources ===&lt;br /&gt;
&lt;br /&gt;
Put the ''amule'' folder and the ''wxMac'' folder in the same place, e.g. on the desktop (if using another location, ensure that there are no spaces in the path as this can lead to file not found errors with [[wxMac]]). &lt;br /&gt;
&lt;br /&gt;
'''Important:''' If you use [http://developer.apple.com/tools/xcode Xcode] 2.0 then the [http://gcc.gnu.org gcc] 4.0 that comes with it is somewhat broken and can't compile aMule. There are two solutions: upgrade to [http://developer.apple.com/tools/xcode Xcode] 2.1 by [[#Xcode|downloading]] it from [http://www.apple.com Apple] for free, or switch your system to use [http://gcc.gnu.org gcc] 3.3. If your prefer to switch to [http://gcc.gnu.org gcc] 3.3, first check the version of your current default [http://gcc.gnu.org gcc] with ''gcc --version'' and then switch to version 3.3 if required:&lt;br /&gt;
&lt;br /&gt;
 bash: gcc --version&lt;br /&gt;
 bash: sudo gcc_select 3.3&lt;br /&gt;
&lt;br /&gt;
==== Compile [[wxMac]] ====&lt;br /&gt;
&lt;br /&gt;
This step is only needed once, even if you later download and compile a newer version of the [[aMule CVS]] source. &lt;br /&gt;
&lt;br /&gt;
The following assumes that you have placed the above packages on your Desktop.&amp;lt;br&amp;gt;&lt;br /&gt;
''cd'' into the ''wxMac'' folder, ''configure'' and ''make'':&lt;br /&gt;
&lt;br /&gt;
 bash: cd ~/Desktop/wxMac-2.6.1/build&lt;br /&gt;
 bash: ../configure --disable-shared --enable-unicode &lt;br /&gt;
 bash: make&lt;br /&gt;
&lt;br /&gt;
'''NOTE:''' This took approx. 30 minutes on a G4 at 1 GHz.&lt;br /&gt;
&lt;br /&gt;
==== Compile [[aMule]] ====&lt;br /&gt;
&lt;br /&gt;
Now ''cd'' into the ''amule'' folder, ''configure'' and ''make'':&lt;br /&gt;
&lt;br /&gt;
'''NOTE:''' You can copy'n'paste the 3 lines for ''./configure'' in one go.&lt;br /&gt;
&lt;br /&gt;
 bash: cd ~/Desktop/aMule&lt;br /&gt;
 bash: ./configure --disable-systray --disable-gtk     \&lt;br /&gt;
            --with-wx-config=../wxMac-2.6.1/build/wx-config \&lt;br /&gt;
            --disable-debug --enable-optimize    '''''&amp;lt;font color=&amp;quot;red&amp;quot;&amp;gt;OPTIONAL&amp;lt;/font&amp;gt;'''''&lt;br /&gt;
          &lt;br /&gt;
 bash: make&lt;br /&gt;
 bash: strip src/amule    '''''&amp;lt;font color=&amp;quot;red&amp;quot;&amp;gt;OPTIONAL&amp;lt;/font&amp;gt;'''''&lt;br /&gt;
 bash: mv src/amule aMule.app/Contents/MacOS/&lt;br /&gt;
&lt;br /&gt;
The two lines marked as '''''&amp;lt;font color=&amp;quot;red&amp;quot;&amp;gt;OPTIONAL&amp;lt;/font&amp;gt;''''' are optional, that is, the last two options to ''./configure'' and the ''strip'' command. They result in a dramatically reduced file size (approx. 3 MB instead of 50 MB) but disable all possibilities to submit a helpful stacktrace if [[aMule]] crashes or a sample if it hangs to the [[aMule devs|aMule developers]].&lt;br /&gt;
&lt;br /&gt;
=== Problems and solutions ===&lt;br /&gt;
&lt;br /&gt;
*If [http://fink.sourceforge.net Fink] reports something like: ''After unpacking 11.2GB will be freed'', don't be afraid. [http://fink.sourceforge.net Fink] has evolved into a different way of managing packet's size and some old (&amp;quot;old&amp;quot;: at least some months old) packages' sizes aren't handled correctly on the output. If this is your case, devide the number by 1024. So, what the above example really means is: ''After unpacking 11.2MB will be freed''.&lt;br /&gt;
&lt;br /&gt;
*If you get an error like this: ''You cannot open the application &amp;quot;amule&amp;quot; because it may be damaged or incomplete'', right click on ''amule'', then click on ''Show Packages Contents'', go to &amp;quot;Contents&amp;quot;&amp;gt;&amp;quot;MacOS&amp;quot;&amp;gt; and double click on ''amule''. Next time you start from ''aMule.app'' it will run fine. If you still get the same error, move ''aMule.app'' to the desktop and run it from there.&lt;/div&gt;</summary>
		<author><name>Ken</name></author>	</entry>

	<entry>
		<id>http://test.amule.szerverem.hu/wiki/HowTo_compile_on_Mac</id>
		<title>HowTo compile on Mac</title>
		<link rel="alternate" type="text/html" href="http://test.amule.szerverem.hu/wiki/HowTo_compile_on_Mac"/>
				<updated>2005-08-12T04:46:12Z</updated>
		
		<summary type="html">&lt;p&gt;Ken: Removed the &amp;quot;--with-wx-prefix&amp;quot; configure switch; it's redundant with &amp;quot;--with-wx-config&amp;quot;.  Reversed the sense of the debug and optimize switches to match the paragraph describing them.&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;How to get and install [[aMule]] on [http://www.apple.com/macosx/ Apple Mac OS X].&lt;br /&gt;
&lt;br /&gt;
# You can simply download the finished application ('binary release') or &lt;br /&gt;
# You compile it from a [[aMule CVS|CVS source snapshot]].&lt;br /&gt;
&lt;br /&gt;
''The preceding version of this page covering aMule 2.0.0rc8 and earlier is archived [[HowTo_compile_on_Mac_v200rc8|here]].''&lt;br /&gt;
&lt;br /&gt;
== Binary releases ==&lt;br /&gt;
&lt;br /&gt;
If you don't want to bother with installing and compiling all those tools and sources, then get one of the pre-compiled [[aMule]] applications. The official release is considered 'stable', but every now and then applications are built from the current source to allow more people to test new features or the like. &lt;br /&gt;
&lt;br /&gt;
# Latest official binary release: [http://www.amule.org/files/download.php?file=72 aMule-2.0.0-Mac]&lt;br /&gt;
# Periodically compiled binary from cvs: [http://forum.amule.org/thread.php?threadid=5051 amule forum]&lt;br /&gt;
&lt;br /&gt;
== Compiling from source ==&lt;br /&gt;
&lt;br /&gt;
Compiling from source allows most current bug reports, because you can compile and test the [[aMule CVS|CVS snapshot]] of the very day.&lt;br /&gt;
&lt;br /&gt;
To compile [[aMule]] from source you need some development tools, the [[wxWidgets]] library and the [http://dl.amule.org aMule source].&lt;br /&gt;
&lt;br /&gt;
=== Get the sources and development tools ===&lt;br /&gt;
&lt;br /&gt;
==== [http://developer.apple.com/tools/xcode Xcode] ====&lt;br /&gt;
&lt;br /&gt;
[http://developer.apple.com/tools/xcode Xcode] is [http://www.apple.com Apple]'s development environment. We need it for the [http://gcc.gnu.org GCC] compiler. You may have [http://developer.apple.com/tools/xcode Xcode] on CD/DVD, e.g. it is on the [http://www.apple.com/macosx/ OS X] 10.4 DVD.&lt;br /&gt;
&lt;br /&gt;
Otherwise, you can download it from [http://www.apple.com Apple], but you must sign up for a free-of-charge developer account first.&lt;br /&gt;
&lt;br /&gt;
# Get XCode from http://developer.apple.com/tools/download&lt;br /&gt;
# &amp;quot;Member Site&amp;quot;-&amp;gt;&amp;quot;Log In&amp;quot;-&amp;gt;&amp;quot;Download Software&amp;quot;-&amp;gt;&amp;quot;Developer Tools&amp;quot;-&amp;gt;&amp;quot;Download Xcode Tools last release&amp;quot;&amp;gt;&amp;quot;Install&amp;quot;&lt;br /&gt;
&lt;br /&gt;
==== [http://fink.sourceforge.net Fink] ====&lt;br /&gt;
&lt;br /&gt;
'''Optional:''' Fink and gettext are not strictly required to compile aMule, but without them aMule will only appear in English.&lt;br /&gt;
&lt;br /&gt;
[http://fink.sourceforge.net Fink] is an open source (OS) installer for lots of OS tools ported to [http://macos.apple.com Mac OSX]. We need it to install the OS tool [http://www.gnu.org/software/gettext gettext].&lt;br /&gt;
&lt;br /&gt;
# Get [http://fink.sourceforge.net Fink] from http://fink.sourceforge.net/download&lt;br /&gt;
# Read [http://fink.sourceforge.net/download Fink's installation guide] to learn how to install applications through [http://fink.sourceforge.net Fink].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== [http://www.gnu.org/software/gettext gettext] ====&lt;br /&gt;
&lt;br /&gt;
'''Optional:''' gettext and Fink are not strictly required to compile aMule, but without them aMule will only appear in English.&lt;br /&gt;
&lt;br /&gt;
[http://www.gnu.org/software/gettext gettext] is an OS library for text internationalization. This library is used to make [[aMule]] multi-lingual.&lt;br /&gt;
# Get and install the [http://www.gnu.org/software/gettext gettext] library with [http://fink.sourceforge.net Fink]. The package name is [http://www.gnu.org/software/gettext gettext]. &lt;br /&gt;
&lt;br /&gt;
==== [[wxWidgets|wxMac]] ====&lt;br /&gt;
&lt;br /&gt;
[[wxWidgets|wxMac]] is the port of the [[wxWidgets]] library for [http://macos.apple.com Mac OSX]. This library is used to make [[aMule]] 'multi-platform'.&lt;br /&gt;
&lt;br /&gt;
# Get the source from: http://prdownloads.sourceforge.net/wxwindows/wxMac-2.6.0.tar.gz&lt;br /&gt;
# Extract the archive (just double-click it)&lt;br /&gt;
&lt;br /&gt;
Or get the current [[wx-cvs|CVS snapshot]]. Warning: the [[wxMac]] [[wx-cvs|CVS]] is frequently in a bad condition.&lt;br /&gt;
&lt;br /&gt;
 bash: cd ~/Desktop&lt;br /&gt;
 bash: cvs -d :pserver:anoncvs@cvs.wxwidgets.org:/pack/cvsroots/wxwidgets login&lt;br /&gt;
 Note: password is 'anoncvs'&lt;br /&gt;
 bash: cvs -d :pserver:anoncvs@cvs.wxwidgets.org:/pack/cvsroots/wxwidgets checkout wxMac&lt;br /&gt;
&lt;br /&gt;
==== [http://www.amule.org aMule itself] ====&lt;br /&gt;
&lt;br /&gt;
# Get latest daily [[aMule CVS|CVS source snapshot]]: [http://www.amule.org/files/download.php?file=5 aMule CVS]&lt;br /&gt;
# Extract the archive (just double-click it)&lt;br /&gt;
&lt;br /&gt;
=== Compile the sources ===&lt;br /&gt;
&lt;br /&gt;
Put the ''amule'' folder and the ''wxMac'' folder in the same place, e.g. on the desktop.&lt;br /&gt;
&lt;br /&gt;
'''Important:''' If you use [http://developer.apple.com/tools/xcode Xcode] 2.0 then the [http://gcc.gnu.org gcc] 4.0 that comes with it is somewhat broken and can't compile aMule.  There are two solution: upgrade to [http://developer.apple.com/tools/xcode Xcode] 2.1 by [[#Xcode|downloading]] it from [http://www.apple.com Apple] for free, or switch your system to use [http://gcc.gnu.org gcc] 3.3.  If your prefer to switch to [http://gcc.gnu.org gcc] 3.3, first check the version of your current default [http://gcc.gnu.org gcc] with ''gcc --version'' and then switch to version 3.3 if required:&lt;br /&gt;
&lt;br /&gt;
 bash: gcc --version&lt;br /&gt;
 bash: sudo gcc_select 3.3&lt;br /&gt;
&lt;br /&gt;
==== Compile [[wxMac]] ====&lt;br /&gt;
&lt;br /&gt;
This step is only needed once, even if you later download and compile a newer version of the [[aMule CVS]] source. &lt;br /&gt;
&lt;br /&gt;
The following assumes that you have placed the above packages on your Desktop.&amp;lt;br&amp;gt;&lt;br /&gt;
''cd'' into the ''wxMac'' folder, ''configure'' and ''make'':&lt;br /&gt;
&lt;br /&gt;
 bash: cd ~/Desktop/wxMac-2.6.0/build&lt;br /&gt;
 bash: ../configure --disable-shared --enable-unicode &lt;br /&gt;
 bash: make&lt;br /&gt;
&lt;br /&gt;
'''NOTE:''' This took approx. 30 minutes on a G4 at 1 GHz.&lt;br /&gt;
&lt;br /&gt;
==== Compile [[aMule]] ====&lt;br /&gt;
&lt;br /&gt;
Now ''cd'' into the ''amule'' folder, ''configure'' and ''make'':&lt;br /&gt;
&lt;br /&gt;
'''NOTE:''' You can copy'n'paste the 3 lines for ''./configure'' in one go.&lt;br /&gt;
&lt;br /&gt;
 bash: cd ~/Desktop/aMule&lt;br /&gt;
 bash: ./configure --disable-systray --disable-gtk     \&lt;br /&gt;
            --with-wx-config=../wxMac-2.6.0/build/wx-config \&lt;br /&gt;
            --disable-debug --enable-optimize                    '''''&amp;lt;font color=&amp;quot;red&amp;quot;&amp;gt;OPTIONAL&amp;lt;/font&amp;gt;'''''&lt;br /&gt;
          &lt;br /&gt;
 bash: make&lt;br /&gt;
 bash: strip src/amule                                        '''''&amp;lt;font color=&amp;quot;red&amp;quot;&amp;gt;OPTIONAL&amp;lt;/font&amp;gt;'''''&lt;br /&gt;
 bash: mv src/amule aMule.app/Contents/MacOS/&lt;br /&gt;
&lt;br /&gt;
The two lines marked as '''''&amp;lt;font color=&amp;quot;red&amp;quot;&amp;gt;OPTIONAL&amp;lt;/font&amp;gt;''''' are optional, that is, the last two options to ''./configure'' and the ''strip'' command. They result in a dramatically reduced file size (approx. 3 MB instead of 50 MB) but disable all possibilities to submit a helpful stacktrace if [[aMule]] crashes or a sample if it hangs to the [[aMule devs|aMule developers]].&lt;br /&gt;
&lt;br /&gt;
=== Problems and solutions ===&lt;br /&gt;
&lt;br /&gt;
*If [http://fink.sourceforge.net Fink] reports something like: ''After unpacking 11.2GB will be freed'', don't be afraid. [http://fink.sourceforge.net Fink] has evolved into a different way of managing packet's size and some old (&amp;quot;old&amp;quot;: at least some months old) packages' sizes aren't handled correctly on the output. If this is your case, devide the number by 1024. So, what the above example really means is: ''After unpacking 11.2MB will be freed''.&lt;br /&gt;
&lt;br /&gt;
*If you get an error like this: ''You cannot open the application &amp;quot;amule&amp;quot; because it may be damaged or incomplete'', right click on ''amule'', then click on ''Show Packages Contents'', go to &amp;quot;Contents&amp;quot;&amp;gt;&amp;quot;MacOS&amp;quot;&amp;gt; and double click on ''amule''. Next time you start from ''aMule.app'' it will run fine. If you still get the same error, move ''aMule.app'' to the desktop and run it from there.&lt;/div&gt;</summary>
		<author><name>Ken</name></author>	</entry>

	<entry>
		<id>http://test.amule.szerverem.hu/wiki/HowTo_compile_on_Mac</id>
		<title>HowTo compile on Mac</title>
		<link rel="alternate" type="text/html" href="http://test.amule.szerverem.hu/wiki/HowTo_compile_on_Mac"/>
				<updated>2005-07-31T04:09:06Z</updated>
		
		<summary type="html">&lt;p&gt;Ken: Changed warning about Xcode 2.0's gcc4 to recommend upgrading to Xcode 2.1&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;How to get and install [[aMule]] on [http://www.apple.com/macosx/ Apple Mac OS X].&lt;br /&gt;
&lt;br /&gt;
# You can simply download the finished application ('binary release') or &lt;br /&gt;
# You compile it from a [[aMule CVS|CVS source snapshot]].&lt;br /&gt;
&lt;br /&gt;
''The preceding version of this page covering aMule 2.0.0rc8 and earlier is archived [[HowTo_compile_on_Mac_v200rc8|here]].''&lt;br /&gt;
&lt;br /&gt;
== Binary releases ==&lt;br /&gt;
&lt;br /&gt;
If you don't want to bother with installing and compiling all those tools and sources, then get one of the pre-compiled [[aMule]] applications. The official release is considered 'stable', but every now and then applications are built from the current source to allow more people to test new features or the like. &lt;br /&gt;
&lt;br /&gt;
# Latest official binary release: [http://www.amule.org/files/download.php?file=72 aMule-2.0.0-Mac]&lt;br /&gt;
# Periodically compiled binary from cvs: [http://forum.amule.org/thread.php?threadid=5051 amule forum]&lt;br /&gt;
&lt;br /&gt;
== Compiling from source ==&lt;br /&gt;
&lt;br /&gt;
Compiling from source allows most current bug reports, because you can compile and test the [[aMule CVS|CVS snapshot]] of the very day.&lt;br /&gt;
&lt;br /&gt;
To compile [[aMule]] from source you need some development tools, the [[wxWidgets]] library and the [http://dl.amule.org aMule source].&lt;br /&gt;
&lt;br /&gt;
=== Get the sources and development tools ===&lt;br /&gt;
&lt;br /&gt;
==== [http://developer.apple.com/tools/xcode Xcode] ====&lt;br /&gt;
&lt;br /&gt;
[http://developer.apple.com/tools/xcode Xcode] is [http://www.apple.com Apple]'s development environment. We need it for the [http://gcc.gnu.org GCC] compiler. You may have [http://developer.apple.com/tools/xcode Xcode] on CD/DVD, e.g. it is on the [http://www.apple.com/macosx/ OS X] 10.4 DVD.&lt;br /&gt;
&lt;br /&gt;
Otherwise, you can download it from [http://www.apple.com Apple], but you must sign up for a free-of-charge developer account first.&lt;br /&gt;
&lt;br /&gt;
# Get XCode from http://developer.apple.com/tools/download&lt;br /&gt;
# &amp;quot;Member Site&amp;quot;-&amp;gt;&amp;quot;Log In&amp;quot;-&amp;gt;&amp;quot;Download Software&amp;quot;-&amp;gt;&amp;quot;Developer Tools&amp;quot;-&amp;gt;&amp;quot;Download Xcode Tools last release&amp;quot;&amp;gt;&amp;quot;Install&amp;quot;&lt;br /&gt;
&lt;br /&gt;
==== [http://fink.sourceforge.net Fink] ====&lt;br /&gt;
&lt;br /&gt;
'''Optional:''' Fink and gettext are not strictly required to compile aMule, but without them aMule will only appear in English.&lt;br /&gt;
&lt;br /&gt;
[http://fink.sourceforge.net Fink] is an open source (OS) installer for lots of OS tools ported to [http://macos.apple.com Mac OSX]. We need it to install the OS tool [http://www.gnu.org/software/gettext gettext].&lt;br /&gt;
&lt;br /&gt;
# Get [http://fink.sourceforge.net Fink] from http://fink.sourceforge.net/download&lt;br /&gt;
# Read [http://fink.sourceforge.net/download Fink's installation guide] to learn how to install applications through [http://fink.sourceforge.net Fink].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== [http://www.gnu.org/software/gettext gettext] ====&lt;br /&gt;
&lt;br /&gt;
'''Optional:''' gettext and Fink are not strictly required to compile aMule, but without them aMule will only appear in English.&lt;br /&gt;
&lt;br /&gt;
[http://www.gnu.org/software/gettext gettext] is an OS library for text internationalization. This library is used to make [[aMule]] multi-lingual.&lt;br /&gt;
# Get and install the [http://www.gnu.org/software/gettext gettext] library with [http://fink.sourceforge.net Fink]. The package name is [http://www.gnu.org/software/gettext gettext]. &lt;br /&gt;
&lt;br /&gt;
==== [[wxWidgets|wxMac]] ====&lt;br /&gt;
&lt;br /&gt;
[[wxWidgets|wxMac]] is the port of the [[wxWidgets]] library for [http://macos.apple.com Mac OSX]. This library is used to make [[aMule]] 'multi-platform'.&lt;br /&gt;
&lt;br /&gt;
# Get the source from: http://prdownloads.sourceforge.net/wxwindows/wxMac-2.6.0.tar.gz&lt;br /&gt;
# Extract the archive (just double-click it)&lt;br /&gt;
&lt;br /&gt;
Or get the current [[wx-cvs|CVS snapshot]]. Warning: the [[wxMac]] [[wx-cvs|CVS]] is frequently in a bad condition.&lt;br /&gt;
&lt;br /&gt;
 bash: cd ~/Desktop&lt;br /&gt;
 bash: cvs -d :pserver:anoncvs@cvs.wxwidgets.org:/pack/cvsroots/wxwidgets login&lt;br /&gt;
 Note: password is 'anoncvs'&lt;br /&gt;
 bash: cvs -d :pserver:anoncvs@cvs.wxwidgets.org:/pack/cvsroots/wxwidgets checkout wxMac&lt;br /&gt;
&lt;br /&gt;
==== [http://www.amule.org aMule itself] ====&lt;br /&gt;
&lt;br /&gt;
# Get latest daily [[aMule CVS|CVS source snapshot]]: [http://www.amule.org/files/download.php?file=5 aMule CVS]&lt;br /&gt;
# Extract the archive (just double-click it)&lt;br /&gt;
&lt;br /&gt;
=== Compile the sources ===&lt;br /&gt;
&lt;br /&gt;
Put the ''amule'' folder and the ''wxMac'' folder in the same place, e.g. on the desktop.&lt;br /&gt;
&lt;br /&gt;
'''Important:''' If you use [http://developer.apple.com/tools/xcode Xcode] 2.0 then the [http://gcc.gnu.org gcc] 4.0 that comes with it is somewhat broken and can't compile aMule.  There are two solution: upgrade to [http://developer.apple.com/tools/xcode Xcode] 2.1 by [[#Xcode|downloading]] it from [http://www.apple.com Apple] for free, or switch your system to use [http://gcc.gnu.org gcc] 3.3.  If your prefer to switch to [http://gcc.gnu.org gcc] 3.3, first check the version of your current default [http://gcc.gnu.org gcc] with ''gcc --version'' and then switch to version 3.3 if required:&lt;br /&gt;
&lt;br /&gt;
 bash: gcc --version&lt;br /&gt;
 bash: sudo gcc_select 3.3&lt;br /&gt;
&lt;br /&gt;
==== Compile [[wxMac]] ====&lt;br /&gt;
&lt;br /&gt;
This step is only needed once, even if you later download and compile a newer version of the [[aMule CVS]] source. &lt;br /&gt;
&lt;br /&gt;
The following assumes that you have placed the above packages on your Desktop.&amp;lt;br&amp;gt;&lt;br /&gt;
''cd'' into the ''wxMac'' folder, ''configure'' and ''make'':&lt;br /&gt;
&lt;br /&gt;
 bash: cd ~/Desktop/wxMac-2.6.0/build&lt;br /&gt;
 bash: ../configure --disable-shared --enable-unicode &lt;br /&gt;
 bash: make&lt;br /&gt;
&lt;br /&gt;
'''NOTE:''' This took approx. 30 minutes on a G4 at 1 GHz.&lt;br /&gt;
&lt;br /&gt;
==== Compile [[aMule]] ====&lt;br /&gt;
&lt;br /&gt;
Now ''cd'' into the ''amule'' folder, ''configure'' and ''make'':&lt;br /&gt;
&lt;br /&gt;
'''NOTE:''' You can copy'n'paste the 4 lines for ''./configure'' in one go.&lt;br /&gt;
&lt;br /&gt;
 bash: cd ~/Desktop/aMule&lt;br /&gt;
 bash: ./configure --disable-systray --disable-gtk     \&lt;br /&gt;
            --with-wx-prefix=../wxMac-2.6.0/build/lib/     \&lt;br /&gt;
            --with-wx-config=../wxMac-2.6.0/build/wx-config \&lt;br /&gt;
            --enable-debug --disable-optimise                    '''''&amp;lt;font color=&amp;quot;red&amp;quot;&amp;gt;OPTIONAL&amp;lt;/font&amp;gt;'''''&lt;br /&gt;
          &lt;br /&gt;
 bash: make&lt;br /&gt;
 bash: strip src/amule                                        '''''&amp;lt;font color=&amp;quot;red&amp;quot;&amp;gt;OPTIONAL&amp;lt;/font&amp;gt;'''''&lt;br /&gt;
 bash: mv src/amule aMule.app/Contents/MacOS/&lt;br /&gt;
&lt;br /&gt;
The two lines marked as '''''&amp;lt;font color=&amp;quot;red&amp;quot;&amp;gt;OPTIONAL&amp;lt;/font&amp;gt;''''' are optional, that is, the last two options to ''./configure'' and the ''strip'' command. They result in a dramatically reduced file size (approx. 3 MB instead of 50 MB) but disable all possibilities to submit a helpful stacktrace if [[aMule]] crashes or a sample if it hangs to the [[aMule devs|aMule developers]].&lt;br /&gt;
&lt;br /&gt;
=== Problems and solutions ===&lt;br /&gt;
&lt;br /&gt;
*If [http://fink.sourceforge.net Fink] reports something like: ''After unpacking 11.2GB will be freed'', don't be afraid. [http://fink.sourceforge.net Fink] has evolved into a different way of managing packet's size and some old (&amp;quot;old&amp;quot;: at least some months old) packages' sizes aren't handled correctly on the output. If this is your case, devide the number by 1024. So, what the above example really means is: ''After unpacking 11.2MB will be freed''.&lt;br /&gt;
&lt;br /&gt;
*If you get an error like this: ''You cannot open the application &amp;quot;amule&amp;quot; because it may be damaged or incomplete'', right click on ''amule'', then click on ''Show Packages Contents'', go to &amp;quot;Contents&amp;quot;&amp;gt;&amp;quot;MacOS&amp;quot;&amp;gt; and double click on ''amule''. Next time you start from ''aMule.app'' it will run fine. If you still get the same error, move ''aMule.app'' to the desktop and run it from there.&lt;/div&gt;</summary>
		<author><name>Ken</name></author>	</entry>

	<entry>
		<id>http://test.amule.szerverem.hu/wiki/AMule_makes_everything_slow</id>
		<title>AMule makes everything slow</title>
		<link rel="alternate" type="text/html" href="http://test.amule.szerverem.hu/wiki/AMule_makes_everything_slow"/>
				<updated>2005-04-19T00:13:01Z</updated>
		
		<summary type="html">&lt;p&gt;Ken: Added &amp;quot;Max new connections / 5 secs&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;center&amp;gt;'''English''' | [[AMule_makes_everything_slow-nl|Nederlands]] | [[AMule_makes_everything_slow-es|Español]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== [[aMule]] makes everything slow ==&lt;br /&gt;
&lt;br /&gt;
So when you are running [[aMule]], suddenly every other application using the net runs slow. Then you should read this document carefully.&lt;br /&gt;
&lt;br /&gt;
== How to fix this problem ==&lt;br /&gt;
&lt;br /&gt;
Well, the reason is that you have badly configured [[aMule]]. Check the following:&lt;br /&gt;
&lt;br /&gt;
*&amp;quot;Preferences&amp;quot;-&amp;gt;&amp;quot;Connection&amp;quot;-&amp;gt;&amp;quot;Bandwidth Limits&amp;quot;-&amp;gt;&amp;quot;Upload&amp;quot;: If this value is very high, so high that it takes more than 75% of your upload bandwidth, you will get very bad downloading speeds, since most packets on the internet are [http://www.faqs.org/faqs/internet/tcp-ip/resource-list TCP] packets, which require both up and down packets. In other words, to download something, you need to upload some information.&lt;br /&gt;
*&amp;quot;Preferences&amp;quot;-&amp;gt;&amp;quot;Connection&amp;quot;-&amp;gt;&amp;quot;Max Sources per File&amp;quot;-&amp;gt;&amp;quot;Hard Limit&amp;quot;: This specifies the maximum amount of sources you allow for each file being downloaded. Each source periodically requires a connection, so more sources require more connections and so, a bit of bandwidth. Have in mind that if you are downloading ''F'' files at the same time (where ''F'' is a number) and you set Hard Limit's value to ''X'' (where ''X'' is a number), you may allow up to ''X''*''F'' sources overall.&lt;br /&gt;
*&amp;quot;Preferences&amp;quot;-&amp;gt;&amp;quot;Connection&amp;quot;-&amp;gt;&amp;quot;Connection Limits&amp;quot;-&amp;gt;&amp;quot;Max Connections&amp;quot;: This specifies the maximum amount of connections you allow [[aMule]] to have open at the same time. Once again, each connection takes a bit of your bandwidth so, adjust it to whatever suits you.&lt;br /&gt;
*&amp;quot;Preferences&amp;quot;-&amp;gt;&amp;quot;Core Tweaks&amp;quot;-&amp;gt;&amp;quot;Max new connections / 5 secs&amp;quot;: This specifies the maximum number of new connections you allow [[aMule]] to open in any 5 second period. Certain routers can't cope with a lot of connections being opened in a short period of time.  They may slow down or they may lock up.  Reduce this setting if your router exhibits this problem.&lt;br /&gt;
*&amp;quot;Preferences&amp;quot;-&amp;gt;&amp;quot;Core tweaks&amp;quot;-&amp;gt;&amp;quot;Verbose log&amp;quot;: On old [[wxWidgets]] versions (prior to 2.5.4), verbose log filling the servers log causes high CPU usage. Disable it.&lt;br /&gt;
*Files with auto-priority must be set to other than auto if you find hard disk usage is too high.&lt;br /&gt;
&lt;br /&gt;
== What are the values that suit my needs ==&lt;br /&gt;
&lt;br /&gt;
This will depend on your connection type ([http://en.wikipedia.org/wiki/Integrated_Services_Digital_Network ISDN], Modem, [http://en.wikipedia.org/wiki/DSL DSL], Cable, T1, etc...), your [http://en.wikipedia.org/wiki/ISP ISP], the bandwidth your other apps need and the amount of files you are downloading (also, in the [http://en.wikipedia.org/wiki/CPU CPU] if it is slow).&lt;br /&gt;
&lt;br /&gt;
As you see, it is very personal and it's impossible to tell what suits your needs and what not. The only way to get it right is to go testing. The procedure is:&lt;br /&gt;
&lt;br /&gt;
*Set it to some value.&lt;br /&gt;
**If it's ok: then tweak those values a little to see if you can get some more connections (improving the speed) without loosing effectiveness on the other apps.&lt;br /&gt;
**If the other apps suffer from lack of bandwidth: lower the values so that [[aMule]] takes less bandwidth.&lt;br /&gt;
*Repeat the above steps until you find the values which suit better your needs.&lt;/div&gt;</summary>
		<author><name>Ken</name></author>	</entry>

	<entry>
		<id>http://test.amule.szerverem.hu/wiki/Configure</id>
		<title>Configure</title>
		<link rel="alternate" type="text/html" href="http://test.amule.szerverem.hu/wiki/Configure"/>
				<updated>2005-03-29T09:47:41Z</updated>
		
		<summary type="html">&lt;p&gt;Ken: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{| width=&amp;quot;90%&amp;quot; align=&amp;quot;left&amp;quot;&lt;br /&gt;
|&lt;br /&gt;
== Introduction ==&lt;br /&gt;
&lt;br /&gt;
''configure'' configures [[aMule]] to adapt to many kinds of systems.&lt;br /&gt;
&lt;br /&gt;
Its purpose is to make it easy to port it to many platforms and to compile it and use it in all platforms in the very same way.&lt;br /&gt;
&lt;br /&gt;
You can set lots of parameters in it to adapt it to your system and to tweak its features.&lt;br /&gt;
&lt;br /&gt;
'''NOTE:''' This article is focused in [[aMule]]'s ''configure''. Other ''configure'' scripts work in a similar way, but their options will differ. This article might be useful for them as well, but have in mind that they might have options not listed here and lack some listed here too.&lt;br /&gt;
&lt;br /&gt;
== Main usage ==&lt;br /&gt;
&lt;br /&gt;
Its usage is ''./configure [OPTION]... [VARIABLE=VALUE]...''&lt;br /&gt;
&lt;br /&gt;
So, as you can see, you can define its behaviour both through [[#Options|options]] and through [[#Variables|variables]]&lt;br /&gt;
&lt;br /&gt;
== Options ==&lt;br /&gt;
&lt;br /&gt;
You can define one or more options. The available options in [[aMule]]'s ''configure'' are listed below. To better understand their meaning, they have been grouped into several tables with options which affect the behaviour of ''configure'' in a similar way.&lt;br /&gt;
&lt;br /&gt;
Please note that ''configure'' will (in most cases) not complain if you enter an invalid option or variable. So make sure you enter the options correctly (no typos) or they will have no effect and configure won't behave in the way you expected.&lt;br /&gt;
&lt;br /&gt;
=== Main options ===&lt;br /&gt;
&lt;br /&gt;
These options should exist in any ''configure'' script around the world. They won't run the ''configure'' script to configure your application's compilation, but only output information you might need.&lt;br /&gt;
&lt;br /&gt;
{| border=1&lt;br /&gt;
|+ Basic options&lt;br /&gt;
|''-h'' or ''--help'' || This will display a help message summing up all ''configure'' options&lt;br /&gt;
|-&lt;br /&gt;
|''-V'' or ''--version'' || This will display the version information&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Non-compilation common options ===&lt;br /&gt;
&lt;br /&gt;
These options should also exist on any ''configure'' script around the world. They will set some non-compilation related preferences.&lt;br /&gt;
&lt;br /&gt;
{| border=1&lt;br /&gt;
|+ Options directly related to the ''configure'' script&lt;br /&gt;
|''-q'' or ''--quiet'' or ''--silent'' || Do not print the `checking...' messages, only the final summed up ouput&lt;br /&gt;
|-&lt;br /&gt;
|''--cache-file=FILE'' || Store the checkings' ouputs in '''FILE''' in a script format, so you can reuse without the need to rerun ''configure'' (read the cached file for more information)&lt;br /&gt;
|-&lt;br /&gt;
|''-C'' or ''--config-cache || Same as ''--cache-file=config.cache''&lt;br /&gt;
|-&lt;br /&gt;
|''-n'' or ''--no-create || Just run ''configure'', but do not create any files&lt;br /&gt;
|-&lt;br /&gt;
|''--srcdir=DIR'' || Look for the sources in '''DIR'''. By default, the ''configure'' dir or its parent (''../'')&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Common options ===&lt;br /&gt;
&lt;br /&gt;
These options should also exist on any ''configure'' script around the world. This time, these ones will affect the compilation of the application, so be careful when using them. You should take a close look at the application's ''README'' document (if available) if you want to use any of them (and even if you don't, still take a look at it, since you might '''have''' to use some). &lt;br /&gt;
&lt;br /&gt;
{| border=1&lt;br /&gt;
|+ Installation directories options&lt;br /&gt;
| ''--prefix=PREFIX'' || Set where to install architecture-independent files (data) in '''PREFIX'''. By dafault, this is set to ''/usr/local''&lt;br /&gt;
|-&lt;br /&gt;
| --exec-prefix=EPREFIX || Set where to install architecture-dependent files (mainly binaries) in '''EPREFIX'''. By default, this is set to the same value as '''PREFIX'''.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
{| border=1&lt;br /&gt;
|+ Advanced installation directories options&lt;br /&gt;
| ''--bindir=DIR'' || Where to store user executables. By default, '''''EPREFIX'''/bin''&lt;br /&gt;
|-&lt;br /&gt;
| ''--sbindir=DIR'' || Where to store system administrator executables. By default, '''''EPREFIX'''/sbin''&lt;br /&gt;
|-&lt;br /&gt;
| ''--libexecdir=DIR'' || Where to store program executable. By default '''''EPREFIX'''/libexeec''&lt;br /&gt;
|-&lt;br /&gt;
| ''--datadir=DIR'' || Where to store read-only architecture independent data. By default, '''''EPREFIX'''/share''&lt;br /&gt;
|-&lt;br /&gt;
| ''--sysconfdir=DIR'' || Where to install read-only single-machine data. By default, '''''PREFIX'''/etc''&lt;br /&gt;
|-&lt;br /&gt;
| ''--sharedstatedir=DIR'' || Where to store modifiable architacture-independent data. By default '''''PREFIX'''/com''&lt;br /&gt;
|-&lt;br /&gt;
| ''--localstatedir=DIR'' || Where to store modifiable single-machine data. By default, '''''PREFIX'''/var''&lt;br /&gt;
|-&lt;br /&gt;
| ''--libdir=DIR || Where to search libs object code libraries. By default, '''''EPREFIX'''/lib''&lt;br /&gt;
|-&lt;br /&gt;
| ''--includedir=DIR'' || Directory containing the [http://en.wikipedia.org/wiki/C_programming_language C] header files. By default, '''''PREFIX'''''/include''&lt;br /&gt;
|-&lt;br /&gt;
| ''--oldincludedir=DIR'' || Directory containing [http://en.wikipedia.org/wiki/C_programming_language C] header files for non-GCC. By default, ''/usr/include''&lt;br /&gt;
|-&lt;br /&gt;
| ''--infodir=DIR'' || Where to store info and documentation files. By default, '''''EPREFIX'''/info''&lt;br /&gt;
|-&lt;br /&gt;
| ''--mandir=DIR'' || Where to store man pages. By default, '''''EPREFIX'''/man&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
{| border=1&lt;br /&gt;
|+ General rule to program enabling and dirs specification&lt;br /&gt;
| ''--PROGRAM-prefix=PREFIX'' || Prepend '''PREFIX''' to installed '''PROGRAM''' directories&lt;br /&gt;
|-&lt;br /&gt;
| ''--PROGRAM-suffix=SUFFIX'' || Append '''SUFFIX''' to installed '''PROGRAM''' directories&lt;br /&gt;
|-&lt;br /&gt;
| ''--PROGRAM-transform-name=SUBST'' || Run ''[http://www.gnu.org/software/sed/sed.html sed] '''SUBST''''' on installed '''PROGRAM''' names&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
{| border=1&lt;br /&gt;
|+ General rule to enabling or disabling features (sometimes it enables or disables the compilation of a program)&lt;br /&gt;
| ''--disable-FEATURE'' || Do not include '''FEATURE'''. Equivalent to ''--enable-'''FEATURE'''=no'' (see below)&lt;br /&gt;
|-&lt;br /&gt;
| ''--enable-FEATURE'' || Include '''FEATURE'''. Equivalent to ''--enable-'''FEATURE'''=yes'' (see below)&lt;br /&gt;
|-&lt;br /&gt;
| ''--enable-FEATURE=VALUE'' || Include '''FEATURE''' and specify it's value to '''VALUE'''. The meaning of the value should be explained in the ''configure --help'' output of the script&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
{| border=1&lt;br /&gt;
|+ &lt;br /&gt;
| ''--without-PACKAGE'' || Do not use '''PACKAGE'''. Equivalent to ''--with-'''PACKAGE'''=no'' (see below)&lt;br /&gt;
|-&lt;br /&gt;
| ''--with-PACKAGE'' || use PACKAGE. Equivalent to ''--with-'''PACKAGE'''=yes'' (see below)&lt;br /&gt;
|-&lt;br /&gt;
| ''--with-PACKAGE=VALUE'' || Use '''PACKAGE''' and set its value to '''VALUE'''&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
{| border=1&lt;br /&gt;
|+ System specifications&lt;br /&gt;
| ''--build=BUILD'' || Configure for building on '''BUILD''' platform. By default, it guesses the platform it is being run on&lt;br /&gt;
|-&lt;br /&gt;
| ''--host=HOST'' || Cross-compile to build programs to run on '''HOST''' platforms. By default, same as '''BUILD'''&lt;br /&gt;
|-&lt;br /&gt;
| ''--target=TARGET'' || Configure for building compilers for '''TARGET''' platfroms. By default, same as '''HOST'''&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Very-common options ===&lt;br /&gt;
&lt;br /&gt;
In most ''configure'' scripts you will also be able to use these options.&lt;br /&gt;
&lt;br /&gt;
{| border=1&lt;br /&gt;
|+ Quite common compiler options&lt;br /&gt;
| ''--with-gnu-ld'' || Use the [http://www.gnu.org/software/binutils/manual/ld-2.9.1/ld.html GNU ld] as linker, without testing if it is the default linker in the system&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
{| border=1&lt;br /&gt;
|+ X directory specifications&lt;br /&gt;
| ''--with-x'' || Use the [http://www.xfree86.org X Window System]&lt;br /&gt;
|-&lt;br /&gt;
| ''--x-includes=DIR'' || '''DIR''' contains [http://www.xfree86.org X]'s include files&lt;br /&gt;
|-&lt;br /&gt;
| ''--x-libraries=DIR'' || '''DIR''' contains [http://www.xfree86.org X]'s libraries&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== [[aMule]] options ===&lt;br /&gt;
&lt;br /&gt;
The following options are specific to [[aMule]]'s ''configure'' script. They will allow you to enable and disable them, so you should really take a look at them or you might sadly find out you lack things you would like to have in your [[aMule]] system ;-)&lt;br /&gt;
&lt;br /&gt;
{| border=1&lt;br /&gt;
|+ Developer options&lt;br /&gt;
|-&lt;br /&gt;
| ''--enable-maintainer-mode'' || Activate some extra instructions only useful for developers (and totaly non-recommended to normal users)&lt;br /&gt;
|-&lt;br /&gt;
| ''--disable-dependency-tracking'' || Makes the application compile faster, but causes problems if you change the source code and try to compile again. Dependency tracking allows the make process to know which things to rebuild when something changes. If you do not plan to compile the application again with those same sources, you can safely use this option&lt;br /&gt;
|-&lt;br /&gt;
| ''--enable-dependency-tracking'' || Keep track of the dependencies so that on next build, only changed files will be recompiled. It slows down the compilation a little. This is the default&lt;br /&gt;
|-&lt;br /&gt;
| ''--enable-ccache'' || Enable [http://ccache.samba.org ccache]. This will make following compilations faster since only the non-modified bits of code will be recompiled. If you don't plan to compile [[aMule]] very often, don't enable this, since it takes longer to compile on the first compilation and it requires lots of disk space&lt;br /&gt;
|-&lt;br /&gt;
| ''--enable-profile'' || Enable code profiling (which allows to see how much time and resources are spent on each part of the code, though it will make [[aMule]] run much slower, so, in most cases, don't use it). The output file is ''gmon.out'' and can be viewed with ''gprof''. For more information, ''man [http://www.cs.utah.edu/dept/old/texinfo/as/gprof_toc.html gprof]'' and ''man [http://gcc.gnu.org gcc]'' (in the man pages of ''[http://gcc.gnu.org gcc]'', search for the command line option ''-pg'')&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
{| border=1&lt;br /&gt;
|+ Compilation tweaks&lt;br /&gt;
| ''--disable-debug'' || Disables outputing information of the application execution. This information is useful to track bugs, so you might not want to use this option or you will not be able to report bugs properly&lt;br /&gt;
|-&lt;br /&gt;
| ''--enable-optimize'' || Optimizes the code to run (a little) faster. Using this option will not allow you to create useful bug reports so you might not want to enable it&lt;br /&gt;
|-&lt;br /&gt;
| ''--enable-optimise'' || Same as ''--enable-optimize'', but is deprecated (it is still there for backwards compatibility only)&lt;br /&gt;
|-&lt;br /&gt;
| ''--disable-rpath'' || Do not write the libraries' path into the binary. Useful only if you plan to move the binary to other systems or if you move your libraries often. Only use it if you know what you're doing, since it will make [[aMule]] run slower&lt;br /&gt;
|-&lt;br /&gt;
| ''--enable-static'' || Creates statically linked executables, which means that they will need no libraries since any needed library will be included in the executable file. The executable might run faster, and will be easily portable between systems using the same platform, but will be incredibly bigger in size&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
{| border=1&lt;br /&gt;
|+ Compilation of external libraries&lt;br /&gt;
| ''--disable-embedded_crypto'' || Do not use [[aMule]]'s cryptography code, instead, use external libraries' code. This option is not recommended and it could possibly break the compilation&lt;br /&gt;
|-&lt;br /&gt;
| ''--disable-gsocket'' || Do not use [[aMule]]'s ''gsocket.c'' implementation. Do not use it unless you are '''very''' sure of what you are doing! (On [[wxWidgets]] 2.4, the default ''gsocket.c'' code gives [[Low ID]]s on restart)&lt;br /&gt;
|-&lt;br /&gt;
| ''--disable-nls'' || Do not use [http://www.vitavoom.com/postgresql-docs/nls.html Native Language Support]. It will disable translations, so better don't use it&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
{| border=1&lt;br /&gt;
|+ Compilation hardcodings&lt;br /&gt;
| ''--disable-gtk'' || Disable using pure [http://www.gtk.org GTK] code in [[aMule]] (pure [http://www.gtk.org GTK] code is only used in little parts of code where no universal code could be used). Do not disable it unless you know what you're doing (since some features may not be compiled)&lt;br /&gt;
|-&lt;br /&gt;
| ''--disable-systray'' || Do not include a SysTray into the [[aMule]] build. Only [[wxWidgets]] 2.4.2 users with no [http://www.gtk.org GTK] should use it. Others should disable SysTray in [[aMule]]'s preferences&lt;br /&gt;
|-&lt;br /&gt;
| ''--enable-utf8-systray'' || Use [http://www.unicode.org UTF-8] encoded strings in [[aMule]]'s SysTray&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
{| border=1&lt;br /&gt;
|+ [[aMule]] binaries selection&lt;br /&gt;
| ''--disable-monolithic'' || disable building of the [[aMule|monolithic aMule]] app. This is normally not recommended, unless you really know what you are doing (e.g. to compile only the [[aMuled|daemon]])&lt;br /&gt;
|-&lt;br /&gt;
| ''--enable-amule-daemon'' || Compile [[aMuled|aMule daemon]]&lt;br /&gt;
|-&lt;br /&gt;
| ''--enable-amulecmd'' || Compile the [[aMuleCMD|aMule command line client]]&lt;br /&gt;
|-&lt;br /&gt;
| ''--enable-amulecmdgui'' || Compile [[aMuleCMDDLG|aMule command line client (GUI version)]]&lt;br /&gt;
|-&lt;br /&gt;
| ''--enable-webserver'' || Compile [[aMuleWeb|aMule's WebServer]]&lt;br /&gt;
|-&lt;br /&gt;
| ''--enable-webservergui'' || Compile [[aMuleWebDLG|aMule's WebServer (GUI version)]]&lt;br /&gt;
|-&lt;br /&gt;
| ''--enable-amule-gui'' || Compile [[aMuleGUI|aMule remote GUI]]&lt;br /&gt;
|-&lt;br /&gt;
| ''--enable-cas'' || Compile [[CAS|C aMule Statistics]]&lt;br /&gt;
|-&lt;br /&gt;
| ''--enable-wxcas'' || Compile [[wxCAS|aMule GUI Statistics]]&lt;br /&gt;
|-&lt;br /&gt;
| ''--disable-ed2k'' || Don't compile [[ed2k command|aMule's ed2k links handler]]&lt;br /&gt;
|-&lt;br /&gt;
| ''--enable-alc'' || Compile [[aLinkCreator|aMuleLinkCreator GUI version]]&lt;br /&gt;
|-&lt;br /&gt;
| ''--enable-alcc'' || Compile [[aLinCreatorConsole|aMuleLinkCreator for console]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
{| border=1&lt;br /&gt;
|+ Configure tweaks&lt;br /&gt;
| ''--disable-gtktest'' || Do not try to compile a test [http://www.gtk.org GTK] (either [http://www.gtk.org GTK]1 or [http://www.gtk.org GTK]2 depending on your system's configuration) program to see if your system has a proper [http://www.gtk.org GTK] configuration. This will make the ''configure'' script run a (very) little faster, but you should still not use it unless you know what you are doing, since the ''configure'' script could miss some tests.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== [[aMule]] compilation settings ===&lt;br /&gt;
&lt;br /&gt;
This options are specific to [[aMule]]'s configure script, but they are not directly related to [[aMule]]. They just tell were some libraries or headers are located in your system, so that [[aMule]] can find them when compiling. Use them if you have those files in non-standard paths or when you know what you are doing.&lt;br /&gt;
&lt;br /&gt;
To better understand these options, take a look at the [[#Common options|common options]] chapter in this article.&lt;br /&gt;
&lt;br /&gt;
{| border=1&lt;br /&gt;
|+ [http://www.gzip.org/zlib zLib]&lt;br /&gt;
| ''--with-zlib=PREFIX'' || Look for [http://www.gzip.org/zlib zLib] files in '''PREFIX'''&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
{| border=1&lt;br /&gt;
|+ [http://curl.haxx.se Curl]&lt;br /&gt;
| ''--with-curl-config=CONFIG'' || '''CONFIG''' is the path of ''curl-config''&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
{| border=1&lt;br /&gt;
|+ [http://www.boutell.com/gd LibGD]&lt;br /&gt;
| ''--with-gdlib-prefix=PREFIX'' || Look for [http://www.boutell.com/gd LibGD] files in '''PREFIX'''&lt;br /&gt;
|-&lt;br /&gt;
| ''--with-gdlib-exec-prefix=PREFIX'' || Look for GDLib libraries in '''PREFIX'''. By default, looks for them in the path specified in ''--with-gdlib-exec-prefix''&lt;br /&gt;
|-&lt;br /&gt;
| ''--with-gdlib-config=CONFIG'' || '''CONFIG''' is the path of ''gdlib-config''&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
{| border=1&lt;br /&gt;
|+ [http://www.libpng.org LibPNG]&lt;br /&gt;
| ''--with-libpng-prefix=PREFIX'' || Look for [http://www.libpng.org LibPNG] files in '''PREFIX'''&lt;br /&gt;
|-&lt;br /&gt;
| ''--with-libpng-exec-prefix=PREFIX'' || Look for [http://www.libpng.org LibPNG] libraries in '''PREFIX'''. By default, looks for them in the path specified in ''--with-libpng-exec-prefix''&lt;br /&gt;
|-&lt;br /&gt;
| ''--with-libpng-config=CONFIG'' || '''CONFIG''' is the path of ''libpng-config''&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
{| border=1&lt;br /&gt;
|+ [[wxWidgets]]&lt;br /&gt;
| ''--with-wx-prefix=PREFIX'' || Look for [[wxWidgets]] files in '''PREFIX'''&lt;br /&gt;
|-&lt;br /&gt;
| ''--with-wx-exec-prefix=PREFIX'' || Look for [[wxWidgets]] libraries in '''PREFIX'''. By default, looks for them in the path specified in ''--with-wx-exec-prefix''&lt;br /&gt;
|-&lt;br /&gt;
| ''--with-wx-config=CONFIG'' || '''CONFIG''' is the path of ''wx-config''&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
{| border=1&lt;br /&gt;
|+ [[wxBase]]&lt;br /&gt;
| ''--with-wxbase-prefix=PREFIX'' || Look for [[wxBase]] files in '''PREFIX'''&lt;br /&gt;
|-&lt;br /&gt;
| ''--with-wxbase-exec-prefix=PREFIX'' || Look for [[wxBase]] libraries in '''PREFIX'''. By default, looks for them in the path specified in ''--with-wxbase-exec-prefix''&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| ''--with-wxbase-config=CONFIG'' || '''CONFIG''' is the path of ''wxbase-config''&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
{| border=1&lt;br /&gt;
|+ [http://www.gtk.org GTK]&lt;br /&gt;
| ''--with-gtk-prefix=PREFIX'' || Look for [http://www.gtk.org GTK] (not [http://www.gtk.org GTK]2) files in '''PREFIX'''&lt;br /&gt;
|-&lt;br /&gt;
| ''--with-gtk-exec-prefix=PREFIX'' || Look for [http://www.gtk.org GTK] (not [http://www.gtk.org GTK]2) libraries in '''PREFIX'''. By default, looks for them in the path specified in ''--with-gtk-exec-prefix''&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
{| border=1&lt;br /&gt;
|+ [http://www.openssl.org/docs/crypto/crypto.html Crypto++]&lt;br /&gt;
| ''--with-crypto-prefix=PREFIX'' || Look for [http://www.openssl.org/docs/crypto/crypto.html Crypto++] files in '''PREFIX'''&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
{| border=1&lt;br /&gt;
|+ [http://www.gnu.org/software/libiconv LibIConv]&lt;br /&gt;
| ''--with-libiconv-prefix=PREFIX'' || Look for [http://www.gnu.org/software/libiconv LibIConv] files in '''''PREFIX'''/include'' and '''''PREFIX'''/lib''&lt;br /&gt;
|-&lt;br /&gt;
| ''--without-libiconv-prefix'' || Don't search for [http://www.gnu.org/software/libiconv LibIConv] in includedir and libdir TODO&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
{| border=1&lt;br /&gt;
|+ [http://www.gnu.org/software/gettext GetText]&lt;br /&gt;
| ''--with-included-gettext'' || Use the [http://www.gnu.org/software/gettext GNU GetText] library included here TODO&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
{| border=1&lt;br /&gt;
|+ [http://gnuwin32.sourceforge.net/packages/libintl.htm LibIntl]&lt;br /&gt;
| ''--with-libintl-prefix=PREFIX'' || Look for [http://gnuwin32.sourceforge.net/packages/libintl.htm LibIntl] files in '''''PREFIX'''/include''' and '''''PREFIX'''/lib''''&lt;br /&gt;
|-&lt;br /&gt;
| ''--without-libintl-prefix'' || Don't search for [http://gnuwin32.sourceforge.net/packages/libintl.htm LibIntl] in includedir and libdir TODO&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
{| border=1&lt;br /&gt;
|+ [http://ccache.samba.org ccache]&lt;br /&gt;
| ''--with-ccache-prefix=PREFIX'' || Look for [http://ccache.samba.org ccache] files in '''PREFIX'''&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Variables ==&lt;br /&gt;
&lt;br /&gt;
Before you take a look at the [[#Variables and what they mean|variables and what they mean]], you must take a look at the two variable [[#Usage types|usage types]] available.&lt;br /&gt;
&lt;br /&gt;
=== Usage types ===&lt;br /&gt;
&lt;br /&gt;
You can either use [[#Environment variables|environment variables]] or you can [[#Configure variables|enter variables directly into the ''configure'' command]].&lt;br /&gt;
&lt;br /&gt;
==== Environment variables ====&lt;br /&gt;
&lt;br /&gt;
If you plan to use environment variables, you will affect the behaviour of ''configure'' and any other program you run in that same shell until you end your session. You must set them '''before''' running configure. To set them, run&lt;br /&gt;
&lt;br /&gt;
 export ''VAR=VALUE'''&lt;br /&gt;
&lt;br /&gt;
where ''VAR'' is the name of the environmental variable and ''VALUE'' is it's value.&lt;br /&gt;
&lt;br /&gt;
==== Configure variables ====&lt;br /&gt;
&lt;br /&gt;
If you don't want to use environment variables, you can pass them into the ''configure'' command, this way:&lt;br /&gt;
&lt;br /&gt;
 configure VAR=VALUE&lt;br /&gt;
&lt;br /&gt;
where ''VAR'' stands for the variable name and ''VALUE'' is its value.&lt;br /&gt;
&lt;br /&gt;
=== Variables and what they mean ===&lt;br /&gt;
&lt;br /&gt;
Do '''NOT''' touch these variables if you don't know what you are doing!&lt;br /&gt;
&lt;br /&gt;
This are some of the most commonly used variables for ''configure'':&lt;br /&gt;
&lt;br /&gt;
{| border=1&lt;br /&gt;
|+ Variables&lt;br /&gt;
| ''CC'' || [http://en.wikipedia.org/wiki/C_programming_language C] compiler command to use&lt;br /&gt;
|-&lt;br /&gt;
| ''CXX'' || [http://en.wikipedia.org/wiki/C_Plus_Plus C++] compiler command to use (e.g. ''[http://gcc.gnu.org g++]'')&lt;br /&gt;
|-&lt;br /&gt;
| ''CPP'' || [http://en.wikipedia.org/wiki/C_programming_language C] preprocessor command to use&lt;br /&gt;
|-&lt;br /&gt;
| ''CFLAGS'' || [http://en.wikipedia.org/wiki/C_programming_language C] compiler flags&lt;br /&gt;
|-&lt;br /&gt;
| ''CXXCPP'' || [http://en.wikipedia.org/wiki/C_Plus_Plus C++] preprocessor command to use&lt;br /&gt;
|-&lt;br /&gt;
| ''CXXFLAGS'' || [http://en.wikipedia.org/wiki/C_Plus_Plus C++] compiler flags&lt;br /&gt;
|-&lt;br /&gt;
| ''LDFLAGS'' || Linker flags. Usually used to specify additional library directories (e.g. ''LDFLAGS=&amp;quot;-L/usr/lib&amp;quot;'')&lt;br /&gt;
|-&lt;br /&gt;
| ''CPPFLAGS'' || [http://en.wikipedia.org/wiki/C_programming_language C]/[http://en.wikipedia.org/wiki/C_Plus_Plus C++] preprocessor flags (e.g. ''CPPFLAGS=&amp;quot;-I/usr/include&amp;quot;'')&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== More information ==&lt;br /&gt;
&lt;br /&gt;
This article is mainly an explanation (dummy-proof) of the output of ''configure --help''.&lt;br /&gt;
&lt;br /&gt;
Anyway, it could (rarely) be out of date. So, if there's something you want to do with ''configure'' that is not listed here, run ''configure --help'' and see if it is listed there.&lt;br /&gt;
&lt;br /&gt;
Of course, you can always take a look at the [http://www.airs.com/ian/configure GNU configure page].&lt;br /&gt;
|&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Ken</name></author>	</entry>

	<entry>
		<id>http://test.amule.szerverem.hu/wiki/HowTo_compile_on_Mac</id>
		<title>HowTo compile on Mac</title>
		<link rel="alternate" type="text/html" href="http://test.amule.szerverem.hu/wiki/HowTo_compile_on_Mac"/>
				<updated>2005-03-04T05:26:11Z</updated>
		
		<summary type="html">&lt;p&gt;Ken: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;The following steps will lead you to install [[aMule]] in your [http://www.apple.com/macosx MacOS X] box.&lt;br /&gt;
&lt;br /&gt;
Alternatively, you can get recent ready-to-use binaries of [[aMule]] for [http://www.apple.com/macosx MacOS X] from the following thread on the forum: http://forum.amule.org/thread.php?threadid=5051&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
This HowTo is written to compile and install [[aMule]] 2.0.0-rc8. It will not work for older versions. Please note that you should always download the latest [[aMule]] version available.&lt;br /&gt;
&lt;br /&gt;
'''NOTE:''' This document explains how to download files using [http://curl.haxx.se curl]. However, [http://curl.haxx.se curl] might not be installed on your system: either install it (you can use [http://fink.sourceforge.net Fink] to install it) or download the files with whatever application you want (maybe your web browser), but place them in the directory that's being used on each part of the guide, otherwise the commands that are shown here will not work.&lt;br /&gt;
&lt;br /&gt;
== Setting up the required environment ==&lt;br /&gt;
&lt;br /&gt;
These steps are one-time-only steps necessary for the steps in the following sections to work properly.&lt;br /&gt;
&lt;br /&gt;
# [http://developer.apple.com/tools/xcode Xcode]&lt;br /&gt;
## Install [http://developer.apple.com/tools/xcode Xcode Tools] from http://developer.apple.com/tools/download&lt;br /&gt;
## &amp;quot;Member Site&amp;quot;-&amp;gt;&amp;quot;Log In&amp;quot;-&amp;gt;&amp;quot;Download Software&amp;quot;-&amp;gt;&amp;quot;Developer Tools&amp;quot;-&amp;gt;&amp;quot;Download Xcode Tools last release&amp;quot;&amp;gt;&amp;quot;Install&amp;quot;&lt;br /&gt;
# [http://fink.sourceforge.net Fink]&lt;br /&gt;
## Install (or verify installation if already installed) [http://fink.sourceforge.net Fink] from http://fink.sourceforge.net/download&lt;br /&gt;
# [http://www.gnu.org/software/gettext gettext]&lt;br /&gt;
## Using [http://fink.sourceforge.net Fink], install [http://www.gnu.org/software/gettext gettext].  Read [http://fink.sourceforge.net/download Fink's installation guide] to learn how to install applications through [http://fink.sourceforge.net Fink] (the [http://www.gnu.org/software/gettext gettext] package is ''gettext'').&lt;br /&gt;
# Working directories&lt;br /&gt;
## Make ''amule'' dir in your home directory: ''mkdir ~/amule''&lt;br /&gt;
## Make ''wxmac'' dir in your home directory: ''mkdir ~/wxmac''&lt;br /&gt;
&lt;br /&gt;
== Obtaining [[wxMac]] sources ==&lt;br /&gt;
&lt;br /&gt;
# Enter the ''wxmac'' directory: ''cd ~/wxmac''&lt;br /&gt;
# Get the [[wxMac]] source tarball and place it in your ''~/wxmac'' directory: ''curl -O http://dl.sourceforge.net/wxwindows/wxMac-2.5.4.tar.gz''&lt;br /&gt;
# Extract it: ''tar -xzf wxMac-2.5.4.tar.gz''&lt;br /&gt;
# '''Optional:''' You may delete the archive after extracting its contents: ''rm wxMac-2.5.4.tar.gz''&lt;br /&gt;
&lt;br /&gt;
== Installing [[wxMac]] from sources ==&lt;br /&gt;
&lt;br /&gt;
# Enter the directory containing the [[wxMac]] sources: ''cd ~/wxmac/wxMac-2.5.4''&lt;br /&gt;
# Directory ''build'' should already be there. If not, create it with: ''mkdir build''&lt;br /&gt;
# Now enter ''build'' directory: ''cd build''&lt;br /&gt;
# Prepare the compilation: ''../configure''&lt;br /&gt;
# And compile: ''make''&lt;br /&gt;
# Now install [[wxMac]] compilation: ''sudo make install''&lt;br /&gt;
# Get back to your home directory, you're done: ''cd ~''&lt;br /&gt;
# '''Optional:''' If everything went ok, you can safely remove the [[wxMac]] sources (not recommended, since you might want to compile it again someday): ''rm -r ~/wxmac''&lt;br /&gt;
&lt;br /&gt;
== Compiling and installing [[aMule]] ==&lt;br /&gt;
&lt;br /&gt;
# Enter the ''amule'' directory: ''cd ~/amule''&lt;br /&gt;
# Get [[aMule]]'s latest source code (aMule 2.0.0-rc8 sourcecode: [http://download.berlios.de/amule/aMule-2.0.0rc8.tar.bz2 http://download.berlios.de/amule/aMule-2.0.0rc8.tar.bz2]) and place it in your ''~/amule'' directory: ''curl -O http://download.berlios.de/amule/aMule-2.0.0rc8.tar.bz2''&lt;br /&gt;
# Extract it: ''tar -xjf aMule-2.0.0rc8.tar.bz2''&lt;br /&gt;
# Enter [[aMule]]'s sources directory: ''cd aMule-2.0.0rc8''&lt;br /&gt;
# Prepare the compilation (thanks to '''one_2_one''' and '''Babboia''' for his test&amp;amp;fix): ''./configure --disable-systray --disable-gtk --with-wx-config=/usr/local/bin/wx-config''&lt;br /&gt;
# And compile it: ''make''&lt;br /&gt;
# '''Optional:''' You can reduce the size of [[aMule]] from 44MB to 3MB by doing the following (anyway, this will make the [[aMule]] binary lose debug info, so you'll be unable to report problems to the [[aMule devs|aMule Team]] to make [[aMule]] a better program; so, it is not recommended): ''strip src/amule''&lt;br /&gt;
# Copy the ''amule'' binary to the app-Container directory: ''cp src/amule aMule.app/Contents/MacOS/'' ('''NOTE:''' If the ''MacOS'' directory is missing in ''aMule.app'', create it by typing ''mkdir aMule.app/Contents/MacOS'' before executing the previous command. Thanks to '''dan''' for the tip)&lt;br /&gt;
# And copy ''aMule.app'' directory to your Applications folder: ''cp -R aMule.app /Applications''&lt;br /&gt;
# Get back to your home directory, you're done: ''cd ~''&lt;br /&gt;
# If everything went OK, you can safely remove the downloaded packages:&lt;br /&gt;
## Remove [[aMule]]'s sources package: ''rm ~/amule/aMule-2.0.0rc8.tar.bz2''&lt;br /&gt;
## Optionally remove the extracted [[aMule]] sources (not recommended, since you might want to compile it again someday): ''rm -r ~/amule''&lt;br /&gt;
&lt;br /&gt;
== Problems and solutions ==&lt;br /&gt;
&lt;br /&gt;
*If [http://fink.sourceforge.net Fink] reports something like: ''After unpacking 11.2GB will be freed'', don't be afraid. [http://fink.sourceforge.net Fink] has evolved into a different way of managing packet's size and some old (&amp;quot;old&amp;quot;: at least some months old) packages' sizes aren't handled correctly on the output. If this is your case, devide the number by 1024. So, what the above example really means is: ''After unpacking 11.2MB will be freed''.&lt;br /&gt;
&lt;br /&gt;
*If you get an error like this: ''You cannot open the application &amp;quot;amule&amp;quot; because it may be damaged or incomplete'', right click on ''amule'', then click on ''Show Packages Contents'', go to &amp;quot;Contents&amp;quot;&amp;gt;&amp;quot;MacOS&amp;quot;&amp;gt; and double click on ''amule''. Next time you start from ''aMule.app'' it will run fine. If you still get the same error, move ''aMule.app'' to the desktop and run it from there.&lt;br /&gt;
&lt;br /&gt;
== Older releases ==&lt;br /&gt;
&lt;br /&gt;
In older releases ([[aMule]] 2.0.0-rc7 and earlier), the app container wasn't included with the sources. If you are compiling any of this older releases and do not whish to upgrade (remember it is '''strongly''' recommended to upgrade to the latest release), you can:&lt;br /&gt;
&lt;br /&gt;
*Download the latest [[aMule]] sources and get the app container from there (recommended option).&lt;br /&gt;
*Download [http://download.berlios.de/amule/aMule-App-Container.tar.bz2 aMule's app-Container]: ''curl -O http://download.berlios.de/amule/aMule-App-Container.tar.bz2''&lt;br /&gt;
&lt;br /&gt;
You must extract the app container in your ''amule'' directory: possible ''~/amule''&lt;br /&gt;
To extract it: ''tar -xjf aMule-App-Container.tar.bz2''&lt;br /&gt;
&lt;br /&gt;
'''NOTE:''' If the app-Container failed to extract try running this command instead of the app-Container extraction step: ''mkdir -p aMule.app/Contents/MacOS''&lt;br /&gt;
&lt;br /&gt;
Once the installation is finished, you can safely remove the app-Container package: ''rm aMule-App-Container.tar.bz2''&lt;/div&gt;</summary>
		<author><name>Ken</name></author>	</entry>

	<entry>
		<id>http://test.amule.szerverem.hu/wiki/HowTo_compile_on_Mac</id>
		<title>HowTo compile on Mac</title>
		<link rel="alternate" type="text/html" href="http://test.amule.szerverem.hu/wiki/HowTo_compile_on_Mac"/>
				<updated>2005-02-15T11:17:05Z</updated>
		
		<summary type="html">&lt;p&gt;Ken: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;The following steps will lead you to install [[aMule]] in your [http://www.apple.com/macosx MacOS X] box.&lt;br /&gt;
&lt;br /&gt;
Alternatively, you can get recent ready-to-use binaries of [[aMule]] for [http://www.apple.com/macosx MacOS X] from the following thread on the forum: http://forum.amule.org/thread.php?threadid=5051&amp;amp;sid=&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
This HowTo is written to compile and install [[aMule]] 2.0.0-rc8. It will not work for older versions. Please note that you should always download the latest [[aMule]] version available.&lt;br /&gt;
&lt;br /&gt;
'''NOTE:''' This document explains how to download files using [http://curl.haxx.se curl]. However, [http://curl.haxx.se curl] might not be installed on your system: either install it (you can use [http://fink.sourceforge.net Fink] to install it) or download the files with whatever application you want (maybe your web browser), but place them in the directory that's being used on each part of the guide, otherwise the commands that are shown here will not work.&lt;br /&gt;
&lt;br /&gt;
== Setting up the required environment ==&lt;br /&gt;
&lt;br /&gt;
These steps are one-time-only steps necessary for the steps in the following sections to work properly.&lt;br /&gt;
&lt;br /&gt;
# [http://developer.apple.com/tools/xcode Xcode]&lt;br /&gt;
## Install [http://developer.apple.com/tools/xcode Xcode Tools] from http://developer.apple.com/tools/download&lt;br /&gt;
## &amp;quot;Member Site&amp;quot;-&amp;gt;&amp;quot;Log In&amp;quot;-&amp;gt;&amp;quot;Download Software&amp;quot;-&amp;gt;&amp;quot;Developer Tools&amp;quot;-&amp;gt;&amp;quot;Download Xcode Tools last release&amp;quot;&amp;gt;&amp;quot;Install&amp;quot;&lt;br /&gt;
# [http://fink.sourceforge.net Fink]&lt;br /&gt;
## Install (or verify installation if already installed) [http://fink.sourceforge.net Fink] from http://fink.sourceforge.net/download&lt;br /&gt;
# [http://www.gnu.org/software/gettext gettext]&lt;br /&gt;
## Using [http://fink.sourceforge.net Fink], install [http://www.gnu.org/software/gettext gettext].  Read [http://fink.sourceforge.net/download Fink's installation guide] to learn how to install applications through [http://fink.sourceforge.net Fink] (the [http://www.gnu.org/software/gettext gettext] package is ''gettext'').&lt;br /&gt;
# Working directories&lt;br /&gt;
## Make ''amule'' dir in your home directory: ''mkdir ~/amule''&lt;br /&gt;
## Make ''wxmac'' dir in your home directory: ''mkdir ~/wxmac''&lt;br /&gt;
&lt;br /&gt;
== Obtaining [[wxMac]] sources ==&lt;br /&gt;
&lt;br /&gt;
'''ATTENTION:''' [[wxMac]] 2.5.3 has a couple of bugs which cause [[aMule]] 2.0.0-rc8 to crash. One bug causes [[aMule]] to crash just after starting up, the other causes it to crash at a random later time :-(. The only work-around is to pull the [[wxWidgets]] sources from [[wx-cvs|CVS]]!&lt;br /&gt;
&lt;br /&gt;
You have two options, downloading a [[wx-cvs|CVS]] snapshot or performing a checkout through the [[wxWidgets]] [[wx-cvs|CVS]] server.  The snapshot may be faster to download; the [[wx-cvs|CVS]] server will give you the most up-to-date sources and the most flexibility if you need sources from a previous day (for example, to avoid bugs that may crop up in the ever-changing source).  On the other hand, the sources from the snapshot, once extracted, take nearly 6 times as much disk space as those checked out from the [[wx-cvs|CVS]] server because they include files not necessary for compiling on [http://macosx.apple.com MacOS X].&lt;br /&gt;
&lt;br /&gt;
=== '''Option 1:''' Obtaining [[wxMac]] sources from [[wx-cvs|CVS]] snapshot ===&lt;br /&gt;
&lt;br /&gt;
These instructions were adapted from http://wxwidgets.org/cvs.htm&lt;br /&gt;
&lt;br /&gt;
# Enter the ''wxmac'' directory: ''cd ~/wxmac''&lt;br /&gt;
# Get the [[wxMac]] [[wx-cvs|CVS]] snapshot (found at http://wxwindows.sourceforge.net/snapshots as ''wx-cvs.tar.bz2'') and place it in your ''~/wxmac'' directory: ''curl -O http://biolpc22.york.ac.uk/pub/CVS_HEAD/wx-cvs.tar.bz2''&lt;br /&gt;
# Extract it: ''tar -xjf wx-cvs.tar.bz2''&lt;br /&gt;
# '''Optional:''' You may delete the archive after extracting its contents: ''rm wx-cvs.tar.bz2''&lt;br /&gt;
&lt;br /&gt;
=== '''Option 2:''' Obtaining [[wxMac]] sources from [[wx-cvs|CVS]] server ===&lt;br /&gt;
&lt;br /&gt;
These instructions were adapted from http://wxwidgets.org/cvs.htm&lt;br /&gt;
&lt;br /&gt;
# Enter the ''wxmac'' directory: ''cd ~/wxmac''&lt;br /&gt;
# Login (anonymously) to the wxWidgets CVS server (when prompted, enter ''anoncvs'' as the password): ''cvs -d :pserver:anoncvs@cvs.wxwidgets.org:/pack/cvsroots/wxwidgets login''&lt;br /&gt;
# Checkout the [[wxMac]] sources from CVS: ''cvs -d :pserver:anoncvs@cvs.wxwidgets.org:/pack/cvsroots/wxwidgets checkout wxMac''&lt;br /&gt;
&lt;br /&gt;
== Installing [[wxMac]] from sources ==&lt;br /&gt;
&lt;br /&gt;
# Enter the directory containing the [[wxMac]] sources: ''cd ~/wxmac/wxWidgets''&lt;br /&gt;
# Directory ''build'' should already be there. If not, create it with: ''mkdir build''&lt;br /&gt;
# Now enter ''build'' directory: ''cd build''&lt;br /&gt;
# Prepare the compilation: ''../configure''&lt;br /&gt;
# And compile: ''make''&lt;br /&gt;
# Now install [[wxMac]] compilation: ''sudo make install''&lt;br /&gt;
# Get back to your home directory, you're done: ''cd ~''&lt;br /&gt;
# '''Optional:''' If everything went ok, you can safely remove the [[wxMac]] sources (not recommended, since you might want to compile it again someday): ''rm -r ~/wxmac''&lt;br /&gt;
&lt;br /&gt;
== Compiling and installing [[aMule]] ==&lt;br /&gt;
&lt;br /&gt;
# Enter the ''amule'' directory: ''cd ~/amule''&lt;br /&gt;
# Get [[aMule]]'s latest source code (aMule 2.0.0-rc8 sourcecode: [http://download.berlios.de/amule/aMule-2.0.0rc8.tar.bz2 http://download.berlios.de/amule/aMule-2.0.0rc8.tar.bz2]) and place it in your ''~/amule'' directory: ''curl -O http://download.berlios.de/amule/aMule-2.0.0rc8.tar.bz2''&lt;br /&gt;
# Extract it: ''tar -xjf aMule-2.0.0rc8.tar.bz2''&lt;br /&gt;
# Enter [[aMule]]'s sources directory: ''cd aMule-2.0.0rc8''&lt;br /&gt;
# Prepare the compilation (thanks to '''one_2_one''' and '''Babboia''' for his test&amp;amp;fix): ''./configure --disable-systray --disable-gtk --with-wx-config=/usr/local/bin/wx-config''&lt;br /&gt;
# And compile it: ''make''&lt;br /&gt;
# '''Optional:''' You can reduce the size of [[aMule]] from 44MB to 3MB by doing the following (anyway, this will make the [[aMule]] binary lose debug info, so you'll be unable to report problems to the [[aMule devs|aMule Team]] to make [[aMule]] a better program; so, it is not recommended): ''strip src/amule''&lt;br /&gt;
# Copy the ''amule'' binary to the app-Container directory: ''cp src/amule aMule.app/Contents/MacOS/'' ('''NOTE:''' If the ''MacOS'' directory is missing in ''aMule.app'', create it by typing ''mkdir aMule.app/Contents/MacOS'' before executing the previous command. Thanks to '''dan''' for the tip)&lt;br /&gt;
# And copy ''aMule.app'' directory to your Applications folder: ''cp -R aMule.app /Applications''&lt;br /&gt;
# Get back to your home directory, you're done: ''cd ~''&lt;br /&gt;
# If everything went OK, you can safely remove the downloaded packages:&lt;br /&gt;
## Remove [[aMule]]'s sources package: ''rm ~/amule/aMule-2.0.0rc8.tar.bz2''&lt;br /&gt;
## Optionally remove the extracted [[aMule]] sources (not recommended, since you might want to compile it again someday): ''rm -r ~/amule''&lt;br /&gt;
&lt;br /&gt;
== Problems and solutions ==&lt;br /&gt;
&lt;br /&gt;
*If [http://fink.sourceforge.net Fink] reports something like: ''After unpacking 11.2GB will be freed'', don't be afraid. [http://fink.sourceforge.net Fink] has evolved into a different way of managing packet's size and some old (&amp;quot;old&amp;quot;: at least some months old) packages' sizes aren't handled correctly on the output. If this is your case, devide the number by 1024. So, what the above example really means is: ''After unpacking 11.2MB will be freed''.&lt;br /&gt;
&lt;br /&gt;
*If you get an error like this: ''You cannot open the application &amp;quot;amule&amp;quot; because it may be damaged or incomplete'', right click on ''amule'', then click on ''Show Packages Contents'', go to &amp;quot;Contents&amp;quot;&amp;gt;&amp;quot;MacOS&amp;quot;&amp;gt; and double click on ''amule''. Next time you start from ''aMule.app'' it will run fine. If you still get the same error, move ''aMule.app'' to the desktop and run it from there.&lt;br /&gt;
&lt;br /&gt;
== Older releases ==&lt;br /&gt;
&lt;br /&gt;
In older releases ([[aMule]] 2.0.0-rc7 and earlier), the app container wasn't included with the sources. If you are compiling any of this older releases and do not whish to upgrade (remember it is '''strongly''' recommended to upgrade to the latest release), you can:&lt;br /&gt;
&lt;br /&gt;
*Download the latest [[aMule]] sources and get the app container from there (recommended option).&lt;br /&gt;
*Download [http://download.berlios.de/amule/aMule-App-Container.tar.bz2 aMule's app-Container]: ''curl -O http://download.berlios.de/amule/aMule-App-Container.tar.bz2''&lt;br /&gt;
&lt;br /&gt;
You must extract the app container in your ''amule'' directory: possible ''~/amule''&lt;br /&gt;
To extract it: ''tar -xjf aMule-App-Container.tar.bz2''&lt;br /&gt;
&lt;br /&gt;
'''NOTE:''' If the app-Container failed to extract try running this command instead of the app-Container extraction step: ''mkdir -p aMule.app/Contents/MacOS''&lt;br /&gt;
&lt;br /&gt;
Once the installation is finished, you can safely remove the app-Container package: ''rm aMule-App-Container.tar.bz2''&lt;/div&gt;</summary>
		<author><name>Ken</name></author>	</entry>

	<entry>
		<id>http://test.amule.szerverem.hu/wiki/HowTo_compile_on_Mac</id>
		<title>HowTo compile on Mac</title>
		<link rel="alternate" type="text/html" href="http://test.amule.szerverem.hu/wiki/HowTo_compile_on_Mac"/>
				<updated>2005-01-31T20:31:16Z</updated>
		
		<summary type="html">&lt;p&gt;Ken: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;The following steps will lead you to install [[aMule]] in your [http://www.apple.com/macosx MacOS X] box.&lt;br /&gt;
&lt;br /&gt;
You can get also the most recent binnary of [[aMule]] for [http://www.apple.com/macosx MacOS X] dowloading this: http://download.berlios.de/amule/aMule.zip&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
This HowTo is written to compile and install [[aMule]] 2.0.0-rc8. It will not work for older versions. Please note that you should always download the latest [[aMule]] version available.&lt;br /&gt;
&lt;br /&gt;
'''NOTE:''' This document explains how to download files using [http://curl.haxx.se curl]. However, [http://curl.haxx.se curl] might not be installed on your system: either install it (you can use [http://fink.sourceforge.net Fink] to install it) or download the files with whatever application you want (maybe your web browser), but place them in the directory that's being used on each part of the guide, otherwise the commands that are shown here will not work.&lt;br /&gt;
&lt;br /&gt;
== Setting up the required environment ==&lt;br /&gt;
&lt;br /&gt;
These steps are one-time-only steps necessary for the steps in the following sections to work properly.&lt;br /&gt;
&lt;br /&gt;
# [http://developer.apple.com/tools/xcode Xcode]&lt;br /&gt;
## Install [http://developer.apple.com/tools/xcode Xcode Tools] from http://developer.apple.com/tools/download&lt;br /&gt;
## &amp;quot;Getting ADC ID&amp;quot;-&amp;gt;&amp;quot;Log In&amp;quot;-&amp;gt;&amp;quot;Download Software&amp;quot;-&amp;gt;&amp;quot;Developer Tools&amp;quot;-&amp;gt;&amp;quot;Download Xcode Tools last release&amp;quot;&amp;gt;&amp;quot;Install&amp;quot;&lt;br /&gt;
# [http://fink.sourceforge.net Fink]&lt;br /&gt;
## Install (or verify installation if already installed) [http://fink.sourceforge.net Fink] from http://fink.sourceforge.net/download&lt;br /&gt;
# [http://www.gnu.org/software/gettext gettext]&lt;br /&gt;
## Using [http://fink.sourceforge.net Fink], install [http://www.gnu.org/software/gettext gettext].  Read [http://fink.sourceforge.net/download Fink's installation guide] to learn how to install applications through [http://fink.sourceforge.net Fink] (the [http://www.gnu.org/software/gettext gettext] package is ''gettext'').&lt;br /&gt;
# Working directories&lt;br /&gt;
## Make ''amule'' dir in your home directory: ''mkdir ~/amule''&lt;br /&gt;
## Make ''wxmac'' dir in your home directory: ''mkdir ~/wxmac''&lt;br /&gt;
&lt;br /&gt;
== Obtaining [[wxMac]] sources ==&lt;br /&gt;
&lt;br /&gt;
'''ATTENTION:''' [[wxMac]] 2.5.3 has a couple of bugs which cause [[aMule]] 2.0.0-rc8 to crash. One bug causes [[aMule]] to crash just after starting up, the other causes it to crash at a random later time :-(. The only work-around is to pull the [[wxWidgets]] sources from [[wx-cvs|CVS]]!&lt;br /&gt;
&lt;br /&gt;
You have two options, downloading a [[wx-cvs|CVS]] snapshot or performing a checkout through the [[wxWidgets]] [[wx-cvs|CVS]] server.  The snapshot may be faster to download; the [[wx-cvs|CVS]] server will give you the most up-to-date sources and the most flexibility if you need sources from a previous day (for example, to avoid bugs that may crop up in the ever-changing source).  On the other hand, the sources from the snapshot, once extracted, take nearly 6 times as much disk space as those checked out from the [[wx-cvs|CVS]] server because they include files not necessary for compiling on [http://macosx.apple.com MacOS X].&lt;br /&gt;
&lt;br /&gt;
=== '''Option 1:''' Obtaining [[wxMac]] sources from [[wx-cvs|CVS]] snapshot ===&lt;br /&gt;
&lt;br /&gt;
These instructions were adapted from http://wxwidgets.org/cvs.htm&lt;br /&gt;
&lt;br /&gt;
# Enter the ''wxmac'' directory: ''cd ~/wxmac''&lt;br /&gt;
# Get the [[wxMac]] [[wx-cvs|CVS]] snapshot (found at http://wxwindows.sourceforge.net/snapshots as ''wx-cvs.tar.bz2'') and place it in your ''~/wxmac'' directory: ''curl -O http://biolpc22.york.ac.uk/pub/CVS_HEAD/wx-cvs.tar.bz2''&lt;br /&gt;
# Extract it: ''tar -xjf wx-cvs.tar.bz2''&lt;br /&gt;
# '''Optional:''' You may delete the archive after extracting its contents: ''rm wx-cvs.tar.bz2''&lt;br /&gt;
&lt;br /&gt;
=== '''Option 2:''' Obtaining [[wxMac]] sources from [[wx-cvs|CVS]] server ===&lt;br /&gt;
&lt;br /&gt;
These instructions were adapted from http://wxwidgets.org/cvs.htm&lt;br /&gt;
&lt;br /&gt;
# Enter the ''wxmac'' directory: ''cd ~/wxmac''&lt;br /&gt;
# Login (anonymously) to the wxWidgets CVS server (when prompted, enter ''anoncvs'' as the password): ''cvs -d :pserver:anoncvs@cvs.wxwidgets.org:/pack/cvsroots/wxwidgets login''&lt;br /&gt;
# Checkout the [[wxMac]] sources from CVS: ''cvs -d :pserver:anoncvs@cvs.wxwidgets.org:/pack/cvsroots/wxwidgets checkout wxMac''&lt;br /&gt;
&lt;br /&gt;
== '''Optional:''' Patching the [[wxMac]] sources ==&lt;br /&gt;
&lt;br /&gt;
The [[wxMac]] sources still contain some bugs which cause [[aMule]] to leak memory.  Patches to fix [[wxMac]] have been submitted to the [[wxWidgets]] team.  These patches have not yet been approved by the wxWidgets developers and so should be considered experimental and approached with caution.&lt;br /&gt;
&lt;br /&gt;
# Enter the ''wxmac'' directory: ''cd ~/wxmac''&lt;br /&gt;
# Patch some memory leaks in [[wxMac]].&lt;br /&gt;
## Download the patch files: ''curl &amp;quot;http://sourceforge.net/tracker/download.php?group_id=9863&amp;amp;atid=309863&amp;amp;file_id=112952&amp;amp;aid=1088052&amp;quot; -o ctable.patch &amp;quot;http://sourceforge.net/tracker/download.php?group_id=9863&amp;amp;atid=309863&amp;amp;file_id=112949&amp;amp;aid=1088038&amp;quot; -o bitmap.patch''&lt;br /&gt;
## Apply the patches: ''cat ctable.patch bitmap.patch | patch -p0 -d wxWidgets''&lt;br /&gt;
&lt;br /&gt;
== Installing [[wxMac]] from sources ==&lt;br /&gt;
&lt;br /&gt;
# Enter the directory containing the [[wxMac]] sources: ''cd ~/wxmac/wxWidgets''&lt;br /&gt;
# Directory ''build'' should already be there. If not, create it with: ''mkdir build''&lt;br /&gt;
# Now enter ''build'' directory: ''cd build''&lt;br /&gt;
# Prepare the compilation: ''../configure''&lt;br /&gt;
# And compile: ''make''&lt;br /&gt;
# Now install [[wxMac]] compilation: ''sudo make install''&lt;br /&gt;
# Get back to your home directory, you're done: ''cd ~''&lt;br /&gt;
# '''Optional:''' If everything went ok, you can safely remove the [[wxMac]] sources (not recommended, since you might want to compile it again someday): ''rm -r ~/wxmac''&lt;br /&gt;
&lt;br /&gt;
== Compiling and installing [[aMule]] ==&lt;br /&gt;
&lt;br /&gt;
# Enter the ''amule'' directory: ''cd ~/amule''&lt;br /&gt;
# Get [[aMule]]'s latest source code (aMule 2.0.0-rc8 sourcecode: [http://download.berlios.de/amule/aMule-2.0.0rc8.tar.bz2 http://download.berlios.de/amule/aMule-2.0.0rc8.tar.bz2]) and place it in your ''~/amule'' directory: ''curl -O http://download.berlios.de/amule/aMule-2.0.0rc8.tar.bz2''&lt;br /&gt;
# Extract it: ''tar -xjf aMule-2.0.0rc8.tar.bz2''&lt;br /&gt;
# Enter [[aMule]]'s sources directory: ''cd aMule-2.0.0rc8''&lt;br /&gt;
# Prepare the compilation (thanks to '''one_2_one''' and '''Babboia''' for his test&amp;amp;fix): ''./configure --disable-systray --disable-gtk --with-wx-config=/usr/local/bin/wx-config''&lt;br /&gt;
# And compile it: ''make''&lt;br /&gt;
# '''Optional:''' You can reduce the size of [[aMule]] from 44MB to 3MB by doing the following (anyway, this will make the [[aMule]] binary lose debug info, so you'll be unable to report problems to the [[aMule devs|aMule Team]] to make [[aMule]] a better program; so, it is not recommended): ''strip src/amule''&lt;br /&gt;
# Copy the ''amule'' binary to the app-Container directory: ''cp src/amule aMule.app/Contents/MacOS/'' ('''NOTE:''' If the ''MacOS'' directory is missing in ''aMule.app'', create it by typing ''mkdir aMule.app/Contents/MacOS'' before executing the previous command. Thanks to '''dan''' for the tip)&lt;br /&gt;
# And copy ''aMule.app'' directory to your Applications folder: ''cp -R aMule.app /Applications''&lt;br /&gt;
# Get back to your home directory, you're done: ''cd ~''&lt;br /&gt;
# If everything went OK, you can safely remove the downloaded packages:&lt;br /&gt;
## Remove [[aMule]]'s sources package: ''rm ~/amule/aMule-2.0.0rc8.tar.bz2''&lt;br /&gt;
## Optionally remove the extracted [[aMule]] sources (not recommended, since you might want to compile it again someday): ''rm -r ~/amule''&lt;br /&gt;
&lt;br /&gt;
== Problems and solutions ==&lt;br /&gt;
&lt;br /&gt;
*If [http://fink.sourceforge.net Fink] reports something like: ''After unpacking 11.2GB will be freed'', don't be afraid. [http://fink.sourceforge.net Fink] has evolved into a different way of managing packet's size and some old (&amp;quot;old&amp;quot;: at least some months old) packages' sizes aren't handled correctly on the output. If this is your case, devide the number by 1024. So, what the above example really means is: ''After unpacking 11.2MB will be freed''.&lt;br /&gt;
&lt;br /&gt;
*If you get an error like this: ''You cannot open the application &amp;quot;amule&amp;quot; because it may be damaged or incomplete'', right click on ''amule'', then click on ''Show Packages Contents'', go to &amp;quot;Contents&amp;quot;&amp;gt;&amp;quot;MacOS&amp;quot;&amp;gt; and double click on ''amule''. Next time you start from ''aMule.app'' it will run fine. If you still get the same error, move ''aMule.app'' to the desktop and run it from there.&lt;br /&gt;
&lt;br /&gt;
== Older releases ==&lt;br /&gt;
&lt;br /&gt;
In older releases ([[aMule]] 2.0.0-rc7 and earlier), the app container wasn't included with the sources. If you are compiling any of this older releases and do not whish to upgrade (remember it is '''strongly''' recommended to upgrade to the latest release), you can:&lt;br /&gt;
&lt;br /&gt;
*Download the latest [[aMule]] sources and get the app container from there (recommended option).&lt;br /&gt;
*Download [http://download.berlios.de/amule/aMule-App-Container.tar.bz2 aMule's app-Container]: ''curl -O http://download.berlios.de/amule/aMule-App-Container.tar.bz2''&lt;br /&gt;
&lt;br /&gt;
You must extract the app container in your ''amule'' directory: possible ''~/amule''&lt;br /&gt;
To extract it: ''tar -xjf aMule-App-Container.tar.bz2''&lt;br /&gt;
&lt;br /&gt;
'''NOTE:''' If the app-Container failed to extract try running this command instead of the app-Container extraction step: ''mkdir -p aMule.app/Contents/MacOS''&lt;br /&gt;
&lt;br /&gt;
Once the installation is finished, you can safely remove the app-Container package: ''rm aMule-App-Container.tar.bz2''&lt;/div&gt;</summary>
		<author><name>Ken</name></author>	</entry>

	<entry>
		<id>http://test.amule.szerverem.hu/wiki/Coding_Style</id>
		<title>Coding Style</title>
		<link rel="alternate" type="text/html" href="http://test.amule.szerverem.hu/wiki/Coding_Style"/>
				<updated>2005-01-30T20:53:41Z</updated>
		
		<summary type="html">&lt;p&gt;Ken: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This page details the coding style that should be adopted when writing changes to the aMule codebase.&lt;br /&gt;
&lt;br /&gt;
== Formatting ==&lt;br /&gt;
=== Indenting ===&lt;br /&gt;
==== Use tabs ====&lt;br /&gt;
Always use tabs for indenting, do not use spaces. The size of each tab should be equal to 4 spaces.&lt;br /&gt;
&lt;br /&gt;
==== Scopes ====&lt;br /&gt;
Indent inside new scopes, including classes, structs, functions, etc. &lt;br /&gt;
  &lt;br /&gt;
Examples:&lt;br /&gt;
  if ( false ) {&lt;br /&gt;
    ...&lt;br /&gt;
  } else {&lt;br /&gt;
    ...&lt;br /&gt;
  }&lt;br /&gt;
&lt;br /&gt;
  class foo&lt;br /&gt;
  {&lt;br /&gt;
    foo() {&lt;br /&gt;
      ...&lt;br /&gt;
    }&lt;br /&gt;
  }&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Whitespace ===&lt;br /&gt;
Place whitespace between brackets and keywords, and between operators and variables:&lt;br /&gt;
  &lt;br /&gt;
  if (something == true);&lt;br /&gt;
   &lt;br /&gt;
rather than&lt;br /&gt;
&lt;br /&gt;
  if(something==true);&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Brackets ===&lt;br /&gt;
Brackets are placed on the same line as the construct with the exception of non-inlined functions, structs and classes. Perfer the usage of brackets, even when optional, as in the case of if/while/etc blocks.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Misc ===&lt;br /&gt;
* When using the trinary operator, place brackets to promote readability.&lt;br /&gt;
* Add a space after the &amp;quot;//&amp;quot; chars when writing comments.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Documenting comments ==&lt;br /&gt;
Always remember to documment new functions and classes! Examples of documented classes can be found in can be found in CMD4Hash.h, BarShader.*, ServerListCtrl.* and others. More information on the usage and syntax of doxygen can be found in the doxygen documentation.&lt;br /&gt;
&lt;br /&gt;
Use the following format, which is doxygen compatible.&lt;br /&gt;
&lt;br /&gt;
=== Functions, classes, structs,  etc. === &lt;br /&gt;
   /**&lt;br /&gt;
    * &amp;lt;Short description&amp;gt;&lt;br /&gt;
    *&lt;br /&gt;
    * [@param &amp;lt;Param_1 description&amp;gt;]&lt;br /&gt;
    * [@param &amp;lt;Param_n description&amp;gt;]&lt;br /&gt;
    * [@return &amp;lt;return value description&amp;gt;]&lt;br /&gt;
    *&lt;br /&gt;
    * [Long description]&lt;br /&gt;
    * [@see &amp;lt;reference to other relevant function&amp;gt;]&lt;br /&gt;
    */&lt;br /&gt;
&lt;br /&gt;
=== Variables, typedefs, constants, etc. ===&lt;br /&gt;
   //! &amp;lt;Description&amp;gt;&lt;br /&gt;
  &lt;br /&gt;
&lt;br /&gt;
== Coding ==&lt;br /&gt;
=== Naming Style ===&lt;br /&gt;
Always try to use descriptive names, except when it adds nothing to the readability, such as iterator varibles and counters (it, i, x, y, etc).&lt;br /&gt;
&lt;br /&gt;
Functions:&lt;br /&gt;
 * Function names should follow the AllWordsAreUppercase convention&lt;br /&gt;
 * Function arguments should follow the conventions for local varibles&lt;br /&gt;
     described below&lt;br /&gt;
&lt;br /&gt;
Variables:&lt;br /&gt;
 * Names should follow the firstWordLowerCaseRestUpperCase convention &lt;br /&gt;
 * Prefix global variables with g_&lt;br /&gt;
 * Prefix static variables with s_&lt;br /&gt;
 * Prefix member variables with m_&lt;br /&gt;
&lt;br /&gt;
Classes:&lt;br /&gt;
 * Prefix classnames with &amp;quot;C&amp;quot;&lt;br /&gt;
 * Names should follow the AllWordsAreUppercase convention&lt;br /&gt;
&lt;br /&gt;
Constants:&lt;br /&gt;
 * Use ALLUPPERCASE names&lt;br /&gt;
 &lt;br /&gt;
Filenames:&lt;br /&gt;
 * For classes, use the classname without the &amp;quot;C&amp;quot; prefix.&lt;br /&gt;
   &lt;br /&gt;
&lt;br /&gt;
=== Const Correctness ===&lt;br /&gt;
Remember to mark functions and arguments (pointers, references) as const where possible. This increases the ability for us to write safer code and is a good thing.&lt;br /&gt;
&lt;br /&gt;
====  Consts vs. Defines ====&lt;br /&gt;
Whenever possible, prefer const variables to pre-compiler defines. We've already had problems with nameclashing caused by defines, so me might as well not increase the chances of it happening again. Actual constants also has the major advantage that we gain proper type-safety.&lt;br /&gt;
&lt;br /&gt;
==== References ====&lt;br /&gt;
Always use references where passing large datatypes suchs as wxString and CMD4Hash and only use non-const references if we are going to change the passed variables&lt;br /&gt;
&lt;br /&gt;
=== Hacks ===&lt;br /&gt;
Always try to avoid odd hacks and in general try to avoid abnormal stuff, assignments in if constructs and the like for instance should be avoided when possible. Also try to avoid the usage of void pointers as they result in a almost total loss of type-safety.&lt;br /&gt;
&lt;br /&gt;
=== Helper-functions ===&lt;br /&gt;
Helper functions which can have use across the app should be placed in otherfunctions.h&lt;br /&gt;
&lt;br /&gt;
Whenever possible, prefer wxWidgets functions to system calls, as this reduces the dependencies on specific function-calls that may or may not be available on other platforms.&lt;/div&gt;</summary>
		<author><name>Ken</name></author>	</entry>

	<entry>
		<id>http://test.amule.szerverem.hu/wiki/HowTo_compile_on_Mac</id>
		<title>HowTo compile on Mac</title>
		<link rel="alternate" type="text/html" href="http://test.amule.szerverem.hu/wiki/HowTo_compile_on_Mac"/>
				<updated>2005-01-18T16:43:15Z</updated>
		
		<summary type="html">&lt;p&gt;Ken: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;The following steps will lead you to install [[aMule]] in your [http://www.apple.com/macosx MacOS X] box.&lt;br /&gt;
&lt;br /&gt;
You can get also the most recent binnary of [[aMule]] for [http://www.apple.com/macosx MacOS X] dowloading this: http://download.berlios.de/amule/aMule.zip&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
This HowTo is written to compile and install [[aMule]] 2.0.0-rc8. It will not work for older versions. Please note that you should always download the latest [[aMule]] version available.&lt;br /&gt;
&lt;br /&gt;
'''NOTE:''' This document explains how to download files using [http://curl.haxx.se curl]. However, [http://curl.haxx.se curl] might not be installed on your system: either install it (you can use [http://fink.sourceforge.net Fink] to install it) or download the files with whatever application you want (maybe your web browser), but place them in the directory that's being used on each part of the guide, otherwise the commands that are shown here will not work.&lt;br /&gt;
&lt;br /&gt;
== Setting up the required environment ==&lt;br /&gt;
&lt;br /&gt;
These steps are one-time-only steps necessary for the steps in the following sections to work properly.&lt;br /&gt;
&lt;br /&gt;
# Xcode&lt;br /&gt;
## Install [http://developer.apple.com/tools/xcode Xcode Tools] from http://developer.apple.com/tools/download&lt;br /&gt;
## &amp;quot;Getting ADC ID&amp;quot;-&amp;gt;&amp;quot;Log In&amp;quot;-&amp;gt;&amp;quot;Download Software&amp;quot;-&amp;gt;&amp;quot;Developer Tools&amp;quot;-&amp;gt;&amp;quot;Download Xcode Tools last release&amp;quot;&amp;gt;&amp;quot;Install&amp;quot;&lt;br /&gt;
# Fink&lt;br /&gt;
## Install (or verify installation if already installed) [http://fink.sourceforge.net Fink] from http://fink.sourceforge.net/download&lt;br /&gt;
# gettext&lt;br /&gt;
## Using [http://fink.sourceforge.net Fink], install [http://www.gnu.org/software/gettext gettext].  Read [http://fink.sourceforge.net/download Fink's installation guide] to learn how to install applications through [http://fink.sourceforge.net Fink] (the [http://www.gnu.org/software/gettext gettext] package is ''gettext'').&lt;br /&gt;
# Working directories&lt;br /&gt;
## Make ''amule'' dir in your home directory: ''mkdir ~/amule''&lt;br /&gt;
## Make ''wxmac'' dir in your home directory: ''mkdir ~/wxmac''&lt;br /&gt;
&lt;br /&gt;
== Obtaining [[wxMac]] sources ==&lt;br /&gt;
&lt;br /&gt;
'''ATTENTION:''' [[wxMac]] 2.5.3 has a couple of bugs which cause [[aMule]] 2.0.0-rc8 to crash. One bug causes [[aMule]] to crash just after starting up, the other causes it to crash at a random later time :-(. The only work-around is to pull the wxWidgets sources from CVS!&lt;br /&gt;
&lt;br /&gt;
You have two options, downloading a CVS snapshot or performing a checkout through the wxWidgets CVS server.  The snapshot may be faster to download; the CVS server will give you the most up-to-date sources and the most flexibility if you need sources from a previous day (for example, to avoid bugs that may crop up in the ever-changing source).  On the other hand, the sources from the snapshot, once extracted, take nearly 6 times as much disk space as those checked out from the CVS server because they include files not necessary for compiling on Mac OS X.&lt;br /&gt;
&lt;br /&gt;
'''NOTE:''' As of 2005-01-18, the wxMac developers have approved the patch for the last of these crashing bugs.  Therefore, it is no longer necessary for you to apply any patches yourself.  A checkout from the CVS server will include the fix.  The CVS snapshot won't include the fix until 2005-01-19, so until then use the CVS server checkout method.&lt;br /&gt;
&lt;br /&gt;
=== '''Option 1:''' Obtaining [[wxMac]] sources from CVS snapshot ===&lt;br /&gt;
&lt;br /&gt;
These instructions were adapted from http://wxwidgets.org/cvs.htm&lt;br /&gt;
&lt;br /&gt;
# Enter the ''wxmac'' directory: ''cd ~/wxmac''&lt;br /&gt;
# Get the [[wxMac]] CVS snapshot (found at [http://wxwindows.sourceforge.net/snapshots/ http://wxwindows.sourceforge.net/snapshots/] as ''wx-cvs.tar.bz2'') and place it in your ''~/wxmac'' directory: ''curl -O http://biolpc22.york.ac.uk/pub/CVS_HEAD/wx-cvs.tar.bz2''&lt;br /&gt;
# Extract it: ''tar -xjf wx-cvs.tar.bz2''&lt;br /&gt;
# '''Optional:''' You may delete the archive after extracting its contents: ''rm wx-cvs.tar.bz2''&lt;br /&gt;
&lt;br /&gt;
=== '''Option 2:''' Obtaining [[wxMac]] sources from CVS server ===&lt;br /&gt;
&lt;br /&gt;
These instructions were adapted from http://wxwidgets.org/cvs.htm&lt;br /&gt;
&lt;br /&gt;
# Enter the ''wxmac'' directory: ''cd ~/wxmac''&lt;br /&gt;
# Login (anonymously) to the wxWidgets CVS server (when prompted, enter ''anoncvs'' as the password): ''cvs -d :pserver:anoncvs@cvs.wxwidgets.org:/pack/cvsroots/wxwidgets login''&lt;br /&gt;
# Checkout the [[wxMac]] sources from CVS: ''cvs -d :pserver:anoncvs@cvs.wxwidgets.org:/pack/cvsroots/wxwidgets checkout wxMac''&lt;br /&gt;
&lt;br /&gt;
== '''Optional:''' Patching the [[wxMac]] sources ==&lt;br /&gt;
&lt;br /&gt;
'''NOTE:''' As explained above, it is no longer necessary to patch the [[wxMac]] sources to avoid crashing bugs.  This section remains for those adventurous souls willing to apply the as-yet-unapproved patches for some memory leaks.&lt;br /&gt;
&lt;br /&gt;
The [[wxMac]] sources still contain some bugs which cause aMule to leak memory.  Patches to fix [[wxMac]] have been submitted to the wxWidgets team.  These patches have not yet been approved by the wxWidgets developers and so should be considered experimental and approached with caution.&lt;br /&gt;
&lt;br /&gt;
# Enter the ''wxmac'' directory: ''cd ~/wxmac''&lt;br /&gt;
# Patch some memory leaks in [[wxMac]].&lt;br /&gt;
## Download the patch files: ''curl &amp;quot;http://sourceforge.net/tracker/download.php?group_id=9863&amp;amp;atid=309863&amp;amp;file_id=112952&amp;amp;aid=1088052&amp;quot; -o ctable.patch &amp;quot;http://sourceforge.net/tracker/download.php?group_id=9863&amp;amp;atid=309863&amp;amp;file_id=112949&amp;amp;aid=1088038&amp;quot; -o bitmap.patch''&lt;br /&gt;
## Apply the patches: ''cat ctable.patch bitmap.patch | patch -p0 -d wxWidgets''&lt;br /&gt;
&lt;br /&gt;
== Installing [[wxMac]] from sources ==&lt;br /&gt;
&lt;br /&gt;
# Enter the directory containing the [[wxMac]] sources: ''cd ~/wxmac/wxWidgets''&lt;br /&gt;
# Directory ''build'' should already be there. If not, create it with: ''mkdir build''&lt;br /&gt;
# Now enter ''build'' directory: ''cd build''&lt;br /&gt;
# Prepare the compilation: ''../configure''&lt;br /&gt;
# And compile: ''make''&lt;br /&gt;
# Now install [[wxMac]] compilation: ''sudo make install''&lt;br /&gt;
# Get back to your home directory, you're done: ''cd ~''&lt;br /&gt;
# '''Optional:''' If everything went ok, you can safely remove the [[wxMac]] sources (not recommended, since you might want to compile it again someday): ''rm -r ~/wxmac&lt;br /&gt;
&lt;br /&gt;
== Compiling and installing [[aMule]] ==&lt;br /&gt;
&lt;br /&gt;
# Enter the ''amule'' directory: ''cd ~/amule''&lt;br /&gt;
# Get [[aMule]]'s latest source code (aMule 2.0.0-rc8 sourcecode: [http://download.berlios.de/amule/aMule-2.0.0rc8.tar.bz2 http://download.berlios.de/amule/aMule-2.0.0rc8.tar.bz2]) and place it in your ''~/amule'' directory: ''curl -O http://download.berlios.de/amule/aMule-2.0.0rc8.tar.bz2''&lt;br /&gt;
# Extract it: ''tar -xjf aMule-2.0.0rc8.tar.bz2''&lt;br /&gt;
# Enter [[aMule]]'s sources directory: ''cd aMule-2.0.0rc8''&lt;br /&gt;
# Prepare the compilation (thanks to '''one_2_one''' and '''Babboia''' for his test&amp;amp;fix): ''./configure --disable-systray --disable-gtk --with-wx-config=/usr/local/bin/wx-config''&lt;br /&gt;
# And compile it: ''make''&lt;br /&gt;
# '''Optional:''' You can reduce the size of [[aMule]] from 44MB to 3MB by doing the following (anyway, this will make the [[aMule]] binary lose debug info, so you'll be unable to report problems to the [[aMule devs|aMule Team]] to make [[aMule]] a better program; so, it is not recommended): ''strip src/amule''&lt;br /&gt;
# Copy the ''amule'' binary to the app-Container directory: ''cp src/amule amule.app/Contents/MacOS/'' ('''NOTE:''' If the ''MacOS'' directory is missing in ''amule.app'', create it by typing ''mkdir amule.app/Contents/MacOS'' before executing the previous command. Thanks to '''dan''' for the tip)&lt;br /&gt;
# And copy ''amule.app'' directory to your Applications folder: ''cp -R amule.app /Applications''&lt;br /&gt;
# Get back to your home directory, you're done: ''cd ~''&lt;br /&gt;
# If everything went OK, you can safely remove the downloaded packages:&lt;br /&gt;
## Remove [[aMule]]'s sources package: ''rm ~/amule/aMule-2.0.0rc8.tar.bz2''&lt;br /&gt;
## Optionally remove the extracted [[aMule]] sources (not recommended, since you might want to compile it again someday): ''rm -r ~/amule''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Problems and solutions ==&lt;br /&gt;
&lt;br /&gt;
*If [http://fink.sourceforge.net Fink] reports something like: ''After unpacking 11.2GB will be freed'', don't be afraid. [http://fink.sourceforge.net Fink] has evolved into a different way of managing packet's size and some old (&amp;quot;old&amp;quot;: at least some months old) packages' sizes aren't handled correctly on the output. If this is your case, devide the number by 1024. So, what the above example really means is: ''After unpacking 11.2MB will be freed''.&lt;br /&gt;
&lt;br /&gt;
*If you get an error like this: ''You cannot open the application &amp;quot;amule&amp;quot; because it may be damaged or incomplete'', right click on ''amule'', then click on ''Show Packages Contents'', go to &amp;quot;Contents&amp;quot;&amp;gt;&amp;quot;MacOS&amp;quot;&amp;gt; and double click on ''amule''. Next time you start from ''amule.app'' it will run fine. If you still get the same error, move ''amule.app'' to the desktop and run it from there.&lt;br /&gt;
&lt;br /&gt;
== Older releases ==&lt;br /&gt;
&lt;br /&gt;
In older releases ([[aMule]] 2.0.0-rc7 and earlier), the app container wasn't included with the sources. If you are compiling any of this older releases and do not whish to upgrade (remember it is '''strongly''' recommended to upgrade to the latest release), you can:&lt;br /&gt;
&lt;br /&gt;
*Download the latest [[aMule]] sources and get the app container from there (recommended option).&lt;br /&gt;
*Download [http://download.berlios.de/amule/aMule-App-Container.tar.bz2 aMule's app-Container]: ''curl -O http://download.berlios.de/amule/aMule-App-Container.tar.bz2''&lt;br /&gt;
&lt;br /&gt;
You must extract the app container in your ''amule'' directory: possible ''~/amule''&lt;br /&gt;
To extract it: ''tar -xjf aMule-App-Container.tar.bz2''&lt;br /&gt;
&lt;br /&gt;
'''NOTE:''' If the app-Container failed to extract try running this command instead of the app-Container extraction step: ''mkdir -p amule.app/Contents/MacOS''&lt;br /&gt;
&lt;br /&gt;
Once the installation is finished, you can safely remove the app-Container package: ''rm aMule-App-Container.tar.bz2''&lt;/div&gt;</summary>
		<author><name>Ken</name></author>	</entry>

	</feed>