Difference between revisions of "HowTo compile on Mac"

From AMule Project FAQ
Jump to: navigation, search
(changed "bash: ../configure --disable-shared --enable-unicode --enable-debug --enable-debug_gdb" to "bash: ./configure --disable-shared --enable-unicode --enable-debug --enable-debug_gdb")
(Binary releases: pipe correct typography)
 
(44 intermediate revisions by 11 users not shown)
Line 1: Line 1:
<center>'''English''' | [[HowTo_compile_on_Mac-de|Deutsch]] | [[HowTo_compile_on_Mac-es|Español]] | [[HowTo_compile_on_Mac-fr | Français]] </center>
+
<center>
 +
'''English''' |  
 +
[[HowTo_compile_on_Mac-de|Deutsch]] |  
 +
[[HowTo_compile_on_Mac-es|Espa&ntilde;ol]] |  
 +
[[HowTo_compile_on_Mac-fr|Fran&ccedil;ais]] |
 +
[[HowTo_compile_on_Mac-it|Italiano]]
 +
</center>
  
 
How to get and install [[aMule]] on [http://www.apple.com/macosx/ Apple Mac OS X].
 
How to get and install [[aMule]] on [http://www.apple.com/macosx/ Apple Mac OS X].
  
# You can simply download the finished application ('binary release') or
+
# You can simply download the finished application ('binary release');
# You compile it from a [[aMule SVN|SVN source snapshot]].
+
# You compile it from a [[aMule SVN|SVN source snapshot]] or [http://www.amule.org/files/files.php?cat=42 stable release source].
  
 
== Binary releases ==
 
== Binary releases ==
 
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.  
 
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.  
  
# Latest official binary release: [http://www.amule.org/files/files.php?cat=30 aMule-2.1.3-Mac]
+
Check the Mac forum for the most recent user posted binary: [http://forum.amule.org/index.php?board=49.0 aMule forum]
# Check the Mac forum for a more recent user posted binary: [http://forum.amule.org/index.php?board=49.0 aMule forum]
+
  
 
Now, to install the downloaded binary, just drag the aMule application to a folder of your choice (e.g., ''/Applications'').
 
Now, to install the downloaded binary, just drag the aMule application to a folder of your choice (e.g., ''/Applications'').
Line 16: Line 21:
 
To start aMule, double-click the application icon.
 
To start aMule, double-click the application icon.
  
'''Note:''' You might want to take a look at the [[Mac specific usage]] article.
+
'''Note:''' You might want to take a look at the [[Mac specific usage|Mac-specific usage]] article.
  
 
== Compiling from source ==
 
== Compiling from source ==
Compiling from source allows most current bug reports, because you can compile and test the [[aMule CVS|CVS snapshot]] of the very day.
+
Compiling from source allows most current bug reports, because you can compile and test the [[aMule SVN|SVN snapshot]] of the very day.
  
To compile [[aMule]] from source you need some development tools, the [[wxWidgets]] library and the [http://dl.amule.org aMule source].
+
To compile [[aMule]] from source you need some development tools, the [[wxWidgets]] library and the [http://www.amule.org/files/files.php?cat=42 aMule source].
  
 
=== Get the sources and development tools ===
 
=== Get the sources and development tools ===
==== [http://developer.apple.com/tools/xcode Xcode] ====
+
==== Step 1: Download and install [http://developer.apple.com/tools/xcode Xcode] ====
 
[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.  
 
[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 will need at least version 2.1 of Xcode, a more recent version is preferable though. [http://developer.apple.com/tools/xcode Xcode] is included on the OS X 10.4 DVD, but early versions of 10.4 were shipped with Xcode 2.0, so you will need to check that the version on your DVD is at least 2.1.
+
You will need at least version 2.1 of Xcode, a more recent version is preferable though. You can download the most recent version of Xcode from Apple, but you will need to sign up for a free-of-charge developer account first or log-in using your iTunes Store account.
 
+
Alternatively, you can download the most recent version of Xcode from Apple, but you will need to sign up for a free-of-charge developer account first.
+
  
 
# Get Xcode from http://developer.apple.com/tools/download
 
# Get Xcode from http://developer.apple.com/tools/download
 
# "Member Site"->"Log In"->"Download Software"->"Developer Tools"->"Download Xcode Tools last release">"Install"
 
# "Member Site"->"Log In"->"Download Software"->"Developer Tools"->"Download Xcode Tools last release">"Install"
  
==== [http://www.macports.org MacPorts]====
+
==== Step 2: Install [http://www.macports.org MacPorts]====
[http://www.macports.org MacPorts] is an open source installer for lots of open source tools ported to [http://macos.apple.com Mac OS X]. aMule needs a few of these tools to compile properly. Alternatively, you can also use [http://www.finkproject.org/ Fink] to install these tools or you can install them manually.
+
[http://www.macports.org MacPorts] is an open source installer for lots of open source tools ported to [http://macos.apple.com Mac OS X]. aMule needs a few of these tools to compile properly. Alternatively, <del>you can also use [http://www.finkproject.org/ Fink] to install these tools or</del> (Fink currently lacks many of the needed tools) you can install them manually .
  
 
# Download the most recent version of [http://www.macports.org MacPorts]
 
# Download the most recent version of [http://www.macports.org MacPorts]
# Read [http://trac.macosforge.org/projects/macports/wiki MacPorts' documentation] to learn how to install applications through [http://www.macports.org MacPorts].
+
# Read [http://guide.macports.org/ MacPorts' documentation] to learn how to install applications through [http://www.macports.org MacPorts].
 +
 
 +
===== Syntax of most important commands =====
 +
Packages list can be downloaded/updated through
 +
 
 +
  $ sudo port selfupdate
 +
 
 +
You can upgrade all the packages installed with
 +
 
 +
  $ sudo port upgrade installed
 +
 
 +
Packages can be installed through
 +
 
 +
  $ sudo port install ''package_name''
 +
 
 +
and removed with
 +
 
 +
  $ sudo port uninstall ''package_name''
 +
 
 +
Port variants can be invoked with the plus sign:
 +
 
 +
  $ sudo port install ''package_name'' +universal
 +
 
 +
You can list all available variants with:
 +
 
 +
  $ sudo port variants ''package_name''
 +
 
 +
===== Notes about Universal variant =====
 +
 
 +
As stated [http://guide.macports.org/chunked/internals.configuration-files.html here], MacPorts has different build_arch settings for ''universal'' variant. You can use this variant on Leopard to switch both ppc and i386 version on. Since Snow Leopard doesn't support ppc architecture anymore, the universal variant can be used to switch both i386 and x86_64 version on. Please note that default architecture on Snow Leopard is x86_64 if the CPU supports it, i386 otherwise.
 +
 
 +
'''WARNING''': ''binutils'' [https://svn.macports.org/ticket/21588 fails] building universal. So you should set ''build_arch'' to ''i386'' (about line 59) into ''/opt/local/etc/macports/macports.conf'' to be sure to build every port against i386 architecture (x86_64 is useless since 64-bit Carbon libraries does not exists and wxCocoa is not ready yet).
 +
 
 +
==== Step 3: Install libraries and tools ====
 +
 
 +
These are the package that provides (with dependancies) all needed libraries and tools to build [[wxWidgets]] and [[aMule]] with most of feature:
  
The tools that you will need to install are:
 
 
# automake
 
# automake
 +
# binutils
 
# flex
 
# flex
# gettext (only required if you want to use a language other than English in aMule)
+
# gettext
 
# libpng
 
# libpng
 
# libcryptopp
 
# libcryptopp
Line 50: Line 88:
 
# jpeg
 
# jpeg
 
# libgeoip
 
# libgeoip
 +
# libupnp
 +
# pkgconfig
  
====[http://www.cryptopp.com/ Crypto++]====
+
This should be enough:
'With the recent SVN builds, you will need the crypto++ library to compile with encryption. If not, you will get an error similar to the following,
+
<pre>
+
checking for crypto++ version >= 5.1... configure: error:
+
        Could not find cryptopp header file "cryptlib.h".
+
        Please check if the path "/usr" is valid.
+
</pre>
+
  
The MacPort is currently broken and very outdated (v5.1 while 5.5.2 is the current). So it is best to build it yourself.
+
  $ sudo port install automake binutils flex libpng libcryptopp gd2 libgeoip libupnp
  
# Get the source from: http://www.cryptopp.com/#download
+
==== Step 4: Compile [[wxWidgets|wxMac]] ====
# Extract the archive (just double-click it)
+
 
+
==== [[wxWidgets|wxMac]] ====
+
 
[[wxWidgets|wxMac]] is the port of the [[wxWidgets]] library for [http://www.apple.com/macosx Mac OS X]. This library is used to make [[aMule]] 'multi-platform'.
 
[[wxWidgets|wxMac]] is the port of the [[wxWidgets]] library for [http://www.apple.com/macosx Mac OS X]. This library is used to make [[aMule]] 'multi-platform'.
  
# Get the source from: http://www.wxwidgets.org/downloads/ (Source Archives: wxMac)
+
Get the source from: http://www.wxwidgets.org/downloads/ (Source Archives: wxMac) and extract the archive on your desktop.<br>
# Extract the archive (just double-click it)
+
Last stable version is 2.8.11 at now.
 +
Type
 +
 
 +
$ cd
  
==== [http://www.amule.org aMule itself] ====
+
leave a space after the command, than drag and drop the wxMac uncompressed folder into the Terminal window: the complete path of the folder will be printed on screen. For example:
# Get latest daily [[aMule CVS|CVS source snapshot]]: [http://www.hirnriss.net/?area=cvs aMule CVS]
+
# Extract the archive (just double-click it)
+
  
=== Compile the sources ===
+
$ cd ~/Desktop/wxMac-2.8.11/
Put the ''amule'' folder, the ''wxMac'' folder and the "crypto552" 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 [[WxWidgets|wxMac]]).
+
  
==== Compile gdlib ====
+
Press enter.
This step is only needed once, even if you later download and compile a newer version of the [[aMule CVS]] source. Assuming you have unzipped it on your desktop, do the following:
+
The basic command to configure and compile the package is the following:
  
  bash: cd ~/Desktop/gd-2.0.35/
+
  $ ./configure --disable-shared --enable-unicode --disable-debug --disable-debug_gdb --with-libiconv-prefix=/opt/local && make -j8
bash: ./configure
+
bash: sudo make install
+
  
Libraries have been installed in: /usr/local/lib
+
'''Note:''' The above command doesn't enable debug information. Debug informations allows you to submit a helpful stacktrace if [[aMule]] crashes or a sample if it hangs to the [[aMule devs|aMule developers]]. If you want to compile a debug version then you can use "--enable-debug --enable-debug_gdb" instead.
  
==== Compile Crypto++ ====
+
===== Snow Leopard =====
This step is only needed once, even if you later download and compile a newer version of the [[aMule CVS]] source. Assuming you have unzipped it on your desktop, do the following:
+
  
bash: cd ~/Desktop/cryptopp552/
+
Building on Snow Leopard is tricky. You must focus on architecture, compiler version, compatibility. This should be enough to have compatibility with i386 Leopard and above:
bash: make
+
bash: sudo make install PREFIX=/usr/local/cryptopp
+
  
==== Compile [[WxWidgets|wxMac]] ====
+
  CC="gcc-4.2 -arch i386" CXX="g++-4.2 -arch i386" \
This step is only needed once, even if you later download and compile a newer version of the [[aMule CVS]] source.
+
  ./configure CFLAGS="-arch i386 -isysroot /Developer/SDKs/MacOSX10.5.sdk -mmacosx-version-min=10.5" \
 +
  CXXFLAGS="-arch i386 -isysroot /Developer/SDKs/MacOSX10.5.sdk -mmacosx-version-min=10.5" \
 +
  CPPFLAGS="-arch i386" LDFLAGS="-arch i386" OBJCFLAGS="-arch i386" OBJCXXFLAGS="-arch i386" \
 +
  --disable-shared --enable-unicode --disable-debug --disable-debug_gdb --with-libiconv-prefix=/opt/local
  
The following assumes that you have placed the above packages on your Desktop.<br>
+
followed by:
''cd'' into the ''wxMac'' folder, ''configure'' and ''make'':
+
  
bash: cd ~/Desktop/wxMac-2.8.7/build
+
  make -j8
bash: ./configure --disable-shared --enable-unicode --enable-debug --enable-debug_gdb
+
bash: make
+
  
'''Note:''' The second command above makes sure that wxMac is compiled with debug information. This information allows you to submit a helpful stacktrace if [[aMule]] crashes or a sample if it hangs to the [[aMule devs|aMule developers]]. If you do not want to compile a debug version then you can use "--disable-debug --disable-debug_gdb" instead.
+
==== Step 5: Compile [[aMule]] ====
 +
Download [http://www.amule.org/files/files.php?cat=42 aMule source] and extract archive into the same place of wxMac (i.e. your desktop if you are following out suggestion).
 +
Open a Terminal and type:
  
'''Note:''' If you want to compile a [http://en.wikipedia.org/wiki/Universal_binary Universal Binary] of aMule (i.e., a version of aMule that runs on both PowerPC based and Intel based Macs) then you can add the "--enable-universal_binary" parameter at the end of the second command. If you don't include this parameter wxMac and aMule will be compiled for your native architecture only.
+
  $ cd
  
'''Note:''' The above make command may take up to 50 minutes on a 1.33 GHz G4 processor, depending on the parameters you chose. A faster CPU will take shorter time.
+
then leave a space and drag and drop aMule uncompressed folder whose path will be printed on screen, for example:
  
'''Note:''' The above make command if given with the option -j 8 (make -j 8) will take 5 minutes on an 2,4Ghz Intel iMac
+
  $ cd ~/Desktop/aMule-2.2.
  
==== Compile [[aMule]] ====
+
Press Enter. Now it's possible to configure the sources: there are several options that can be used to activate or deactivate feature during compiling. This is only an example, that provide a full feature aMule build:
Now ''cd'' into the ''amule'' folder, ''configure'' and ''make'':
+
  
'''Note:''' You can copy and paste the 4 lines for ''./configure'' in one go.
+
  $ ./configure --with-wx-config=../wxMac-2.8.10/wx-config  --enable-optimize --with-crypto-prefix=/opt/local \
 +
  --with-gdlib-config=/opt/local/bin/gdlib-config  --with-libiconv-prefix=/opt/local --enable-cas --enable-webserver \
 +
  --enable-amulecmd --enable-amule-gui --enable-wxcas --enable-alc --enable-alcc --enable-amule-daemon --enable-geoip \
 +
  --with-geoip-lib=/opt/local/lib --with-geoip-headers=/opt/local/include --enable-geoip-static --enable-debug
  
'''Note:''' This takes about 30 minutes on a 1.33 GHz G4.
+
Take a look to the [[configure]] page for a complete list of options.
 +
You should pay attention to these elements:
  
bash: cd ~/Desktop/amule-cvs
+
# The given example enables debug informations. To disable them exchange the option ''--enable-debug'' with ''--disable-debug --enable-optimize''.
bash: ./configure --disable-systray --disable-gtk --enable-embedded_crypto    \
+
# The option ''--with-wx-config'' must point to the correct relative path of the compiled wxMac. The example assumes that aMule and wxMac folders are in the same directory (i.e. your desktop). You should also correct the wxMac folder's name according to its version (in the example is 2.8.10).
            --with-wx-config=../wxMac-2.8.7/build/wx-config    \
+
# The option ''--with-crypto-prefix'' should point to /usr/local/cryptopp if you compiled Crypto++ starting from its source, out of MacPorts.
            --enable-cas --enable-webserver --enable-amulecmd    \
+
# '''IMPORTANT!''' It seems that Mac OS version of ''ld'' tool is not able to make static library. So if you plan to run/install your compiled aMule on other Mac which doesn't have MacPorts installed you MUST remove the ''--enable-geoip-static'' option to avoid a crash when the program starts.
            --enable-debug --disable-optimize --with-crypto-prefix=/usr/local/cryptopp
+
  
bash: make
+
Now it's time to make you packages with:
bash: ./src/utils/scripts/mac_packager
+
  
'''Note:''' If you don't want to compile aMule with debug information (see above) you can use "--disable-debug --enable-optimize" in the configure statement.
+
  $ make -j8
  
'''Note:''' In order to compile aMule as a Universal Binary (see above) you will need to add the following parameters to the configure statement:
+
and
            --disable-dependency-tracking \
+
            CFLAGS="-arch ppc -arch i386 -isysroot /Developer/SDKs/MacOSX10.4u.sdk" \
+
            CXXFLAGS="-arch ppc -arch i386 -isysroot /Developer/SDKs/MacOSX10.4u.sdk"
+
  
'''Note:''' Under Mac OS X 10.5 (Leopard) or higher version, you should change the parameters like this:
+
  ./src/utils/scripts/mac_packager
            --disable-dependency-tracking \
+
            CFLAGS="-arch ppc -arch i386 -isysroot /Developer/SDKs/MacOSX10.5.sdk" \
+
            CXXFLAGS="-arch ppc -arch i386 -isysroot /Developer/SDKs/MacOSX10.5.sdk"
+
  
==== Running [[aMule]] ====
+
You should find the aMule package in the same source folder.
Once the mac_packager script has finished, you can move the aMule application from the amule-cvs folder to anywhere on your hard drive.
+

Latest revision as of 06:09, 14 January 2012

English | Deutsch | Español | Français | Italiano

How to get and install aMule on Apple Mac OS X.

  1. You can simply download the finished application ('binary release');
  2. You compile it from a SVN source snapshot or stable release source.

Binary releases

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.

Check the Mac forum for the most recent user posted binary: aMule forum

Now, to install the downloaded binary, just drag the aMule application to a folder of your choice (e.g., /Applications).

To start aMule, double-click the application icon.

Note: You might want to take a look at the Mac-specific usage article.

Compiling from source

Compiling from source allows most current bug reports, because you can compile and test the SVN snapshot of the very day.

To compile aMule from source you need some development tools, the wxWidgets library and the aMule source.

Get the sources and development tools

Step 1: Download and install Xcode

Xcode is Apple's development environment. We need it for the GCC compiler.

You will need at least version 2.1 of Xcode, a more recent version is preferable though. You can download the most recent version of Xcode from Apple, but you will need to sign up for a free-of-charge developer account first or log-in using your iTunes Store account.

  1. Get Xcode from http://developer.apple.com/tools/download
  2. "Member Site"->"Log In"->"Download Software"->"Developer Tools"->"Download Xcode Tools last release">"Install"

Step 2: Install MacPorts

MacPorts is an open source installer for lots of open source tools ported to Mac OS X. aMule needs a few of these tools to compile properly. Alternatively, you can also use Fink to install these tools or (Fink currently lacks many of the needed tools) you can install them manually .

  1. Download the most recent version of MacPorts
  2. Read MacPorts' documentation to learn how to install applications through MacPorts.
Syntax of most important commands

Packages list can be downloaded/updated through

 $ sudo port selfupdate

You can upgrade all the packages installed with

 $ sudo port upgrade installed

Packages can be installed through

 $ sudo port install package_name

and removed with

 $ sudo port uninstall package_name

Port variants can be invoked with the plus sign:

 $ sudo port install package_name +universal

You can list all available variants with:

 $ sudo port variants package_name
Notes about Universal variant

As stated here, MacPorts has different build_arch settings for universal variant. You can use this variant on Leopard to switch both ppc and i386 version on. Since Snow Leopard doesn't support ppc architecture anymore, the universal variant can be used to switch both i386 and x86_64 version on. Please note that default architecture on Snow Leopard is x86_64 if the CPU supports it, i386 otherwise.

WARNING: binutils fails building universal. So you should set build_arch to i386 (about line 59) into /opt/local/etc/macports/macports.conf to be sure to build every port against i386 architecture (x86_64 is useless since 64-bit Carbon libraries does not exists and wxCocoa is not ready yet).

Step 3: Install libraries and tools

These are the package that provides (with dependancies) all needed libraries and tools to build wxWidgets and aMule with most of feature:

  1. automake
  2. binutils
  3. flex
  4. gettext
  5. libpng
  6. libcryptopp
  7. libiconv
  8. gd2
  9. jpeg
  10. libgeoip
  11. libupnp
  12. pkgconfig

This should be enough:

 $ sudo port install automake binutils flex libpng libcryptopp gd2 libgeoip libupnp

Step 4: Compile wxMac

wxMac is the port of the wxWidgets library for Mac OS X. This library is used to make aMule 'multi-platform'.

Get the source from: http://www.wxwidgets.org/downloads/ (Source Archives: wxMac) and extract the archive on your desktop.
Last stable version is 2.8.11 at now. Type

$ cd

leave a space after the command, than drag and drop the wxMac uncompressed folder into the Terminal window: the complete path of the folder will be printed on screen. For example:

$ cd ~/Desktop/wxMac-2.8.11/

Press enter. The basic command to configure and compile the package is the following:

$ ./configure --disable-shared --enable-unicode --disable-debug --disable-debug_gdb --with-libiconv-prefix=/opt/local && make -j8

Note: The above command doesn't enable debug information. Debug informations allows you to submit a helpful stacktrace if aMule crashes or a sample if it hangs to the aMule developers. If you want to compile a debug version then you can use "--enable-debug --enable-debug_gdb" instead.

Snow Leopard

Building on Snow Leopard is tricky. You must focus on architecture, compiler version, compatibility. This should be enough to have compatibility with i386 Leopard and above:

 CC="gcc-4.2 -arch i386" CXX="g++-4.2 -arch i386" \
 ./configure CFLAGS="-arch i386 -isysroot /Developer/SDKs/MacOSX10.5.sdk -mmacosx-version-min=10.5" \
 CXXFLAGS="-arch i386 -isysroot /Developer/SDKs/MacOSX10.5.sdk -mmacosx-version-min=10.5" \
 CPPFLAGS="-arch i386" LDFLAGS="-arch i386" OBJCFLAGS="-arch i386" OBJCXXFLAGS="-arch i386" \
 --disable-shared --enable-unicode --disable-debug --disable-debug_gdb --with-libiconv-prefix=/opt/local

followed by:

 make -j8

Step 5: Compile aMule

Download aMule source and extract archive into the same place of wxMac (i.e. your desktop if you are following out suggestion). Open a Terminal and type:

 $ cd

then leave a space and drag and drop aMule uncompressed folder whose path will be printed on screen, for example:

 $ cd ~/Desktop/aMule-2.2.

Press Enter. Now it's possible to configure the sources: there are several options that can be used to activate or deactivate feature during compiling. This is only an example, that provide a full feature aMule build:

 $ ./configure --with-wx-config=../wxMac-2.8.10/wx-config  --enable-optimize --with-crypto-prefix=/opt/local \
 --with-gdlib-config=/opt/local/bin/gdlib-config  --with-libiconv-prefix=/opt/local --enable-cas --enable-webserver \
 --enable-amulecmd --enable-amule-gui --enable-wxcas --enable-alc --enable-alcc --enable-amule-daemon --enable-geoip \
 --with-geoip-lib=/opt/local/lib --with-geoip-headers=/opt/local/include --enable-geoip-static --enable-debug

Take a look to the configure page for a complete list of options. You should pay attention to these elements:

  1. The given example enables debug informations. To disable them exchange the option --enable-debug with --disable-debug --enable-optimize.
  2. The option --with-wx-config must point to the correct relative path of the compiled wxMac. The example assumes that aMule and wxMac folders are in the same directory (i.e. your desktop). You should also correct the wxMac folder's name according to its version (in the example is 2.8.10).
  3. The option --with-crypto-prefix should point to /usr/local/cryptopp if you compiled Crypto++ starting from its source, out of MacPorts.
  4. IMPORTANT! It seems that Mac OS version of ld tool is not able to make static library. So if you plan to run/install your compiled aMule on other Mac which doesn't have MacPorts installed you MUST remove the --enable-geoip-static option to avoid a crash when the program starts.

Now it's time to make you packages with:

 $ make -j8

and

 ./src/utils/scripts/mac_packager

You should find the aMule package in the same source folder.