It's simple to include a library needed by amule in the bundle. Simply:
With Terminal move in to the aMule.app/Content/MacOS dir.
Execute the command "otool -L amule" to see wich library are used by the app. Some are the wx, and is already present in the framework dir, and present a path like "@executable_path/../Frameworks/libname", some other are system wide library, present in all mac, like the varius libstd and the libsystem.
For each library you have compiled yourself in order to have aMule run do this procedure, but first notice this thigs:
If you look, for example, for libz.1.dylib, wich is reported by otool, being in /usr/lib/libz.1.dylib, you will notice this is a simbolic link for a file in the same dir called libz.1.2.3.dylib. THIS is the real library.
1 - move the REAL library in the Framework dir, and rename it as the one reported by otool, so in example, otool report /usr/lib/libz.1.dylib, then you must move the /usr/lib/libz.1.2.3.dylib in Framework, and rename it to libz.1.dylib.
2 - execute install_name_tool -id @executable_path/../Frameworks/$LIBPATH Frameworks/$LIBPATH (of cource change $LIBPATH with the FULL lib path reported by otool)
3 - install_name_tool -change $LIBPATH @executable_path/../Frameworks/$LIBPATH amule
4 - Execute the otool on the library you have imported and fix the dependecies repeating all the stept.
So in exmple, soppose amule depend on libA.1.dylib, you have to locate the real libA, move to Framework dir in aMule.app, execute the step 2 and 3, execute otool -L libA.1.dylib and look for other libs you have compiled in order to build libA. In the 99,9999% of the case there is no dependencies at this level, but check will not hurt!
If i was't so much clear, please refer to the mac_packager script, this is a bash script doing the same things, but restricted to wx libs. If you understand bash script this is more clear than my words!