aMule Forum
English => Multiplatform => Mac OSX => Topic started by: PepitoGrilloOSX on July 28, 2020, 12:15:10 AM
-
Snow Leopard:
aMule: https://www.dropbox.com/s/y6q66mrskx97trl/aMule-2.3.2-Snow_Leopard-wxWidgets-3.0.2-TabsPatch.zip?dl=0 (https://www.dropbox.com/s/y6q66mrskx97trl/aMule-2.3.2-Snow_Leopard-wxWidgets-3.0.2-TabsPatch.zip?dl=0)
macOS 10.13 (High Sierra):
aMule: https://www.dropbox.com/s/en0g3nv595qjk1z/aMule-2.3.2-macOS_10.13-wxWidgets-3.0.4.zip?dl=0 (https://www.dropbox.com/s/en0g3nv595qjk1z/aMule-2.3.2-macOS_10.13-wxWidgets-3.0.4.zip?dl=0)
aMule GUI / amuled: https://www.dropbox.com/s/z478lidzpadlujx/aMuleGUI-amuled-2.3.2-macOS_10.13-wxWidgets-3.0.4.zip?dl=0 (https://www.dropbox.com/s/z478lidzpadlujx/aMuleGUI-amuled-2.3.2-macOS_10.13-wxWidgets-3.0.4.zip?dl=0)
macOS 10.14 (Mojave):
aMule: https://www.dropbox.com/s/z7im8z4ns0ovnr1/aMule-2.3.2-macOS_10.14-wxWidgets-3.0.4.zip?dl=0 (https://www.dropbox.com/s/z7im8z4ns0ovnr1/aMule-2.3.2-macOS_10.14-wxWidgets-3.0.4.zip?dl=0)
aMule GUI / amuled: https://www.dropbox.com/s/2u6e78oadw7ooi1/aMuleGUI-amuled-2.3.2-macOS_10.14-wxWidgets-3.0.4.zip?dl=0 (https://www.dropbox.com/s/2u6e78oadw7ooi1/aMuleGUI-amuled-2.3.2-macOS_10.14-wxWidgets-3.0.4.zip?dl=0)
macOS 10.15 (Catalina):
aMule: https://www.dropbox.com/s/5brs48zfcvxn2db/aMule-2.3.2-macOS_10.15-wxWidgets-3.0.5.zip?dl=0 (https://www.dropbox.com/s/5brs48zfcvxn2db/aMule-2.3.2-macOS_10.15-wxWidgets-3.0.5.zip?dl=0)
aMule GUI / amuled: https://www.dropbox.com/s/ynnjjfyho9fjjii/aMuleGUI-amuled-2.3.2-macOS_10.15-wxWidgets-3.0.5.zip?dl=0 (https://www.dropbox.com/s/ynnjjfyho9fjjii/aMuleGUI-amuled-2.3.2-macOS_10.15-wxWidgets-3.0.5.zip?dl=0)
Force light mode in Catalina:
defaults write org.amule.aMule NSRequiresAquaSystemAppearance -bool yes
-
Thank you so much!
It works in the sense that it opens but I can't seem to be able to connect or even download the server list sadly.
Do you have any idea of what is happening?
-
macOS 10.15 (Catalina) -- wxWidgets 3.14, with support for Dark Mode!:
aMule GUI / amuled: https://www.dropbox.com/s/iw51wgunvqcnrk2/aMuleGUI-amuled-2.3.2-macOS_10.15-wxWidgets-3.1.4.zip?dl=0 (https://www.dropbox.com/s/iw51wgunvqcnrk2/aMuleGUI-amuled-2.3.2-macOS_10.15-wxWidgets-3.1.4.zip?dl=0)
-
macOS 10.15 (Catalina) -- wxWidgets 3.14, with support for Dark Mode!:
aMule GUI / amuled: https://www.dropbox.com/s/iw51wgunvqcnrk2/aMuleGUI-amuled-2.3.2-macOS_10.15-wxWidgets-3.1.4.zip?dl=0 (https://www.dropbox.com/s/iw51wgunvqcnrk2/aMuleGUI-amuled-2.3.2-macOS_10.15-wxWidgets-3.1.4.zip?dl=0)
Great! Thank you very much!
Do exists an aMule build with dark mode?
-
Many thanks PepitoGrilloOSX ;)
-
macOS 11 (Big Sur) -- wxWidgets 3.14, with support for Dark Mode, and native M1 (arm64) binary!:
aMule GUI / amuled:https://www.dropbox.com/s/19hob4rye8za0k6/aMuleGUI-amuled-2.3.2-macOS_11-arm64-wxWidgets-3.1.4.zip?dl=0 (https://www.dropbox.com/s/19hob4rye8za0k6/aMuleGUI-amuled-2.3.2-macOS_11-arm64-wxWidgets-3.1.4.zip?dl=0)
-
macOS 11 (Big Sur) -- wxWidgets 3.14, with support for Dark Mode, and native M1 (arm64) binary!:
aMule GUI / amuled:https://www.dropbox.com/s/19hob4rye8za0k6/aMuleGUI-amuled-2.3.2-macOS_11-arm64-wxWidgets-3.1.4.zip?dl=0 (https://www.dropbox.com/s/19hob4rye8za0k6/aMuleGUI-amuled-2.3.2-macOS_11-arm64-wxWidgets-3.1.4.zip?dl=0)
Hi there, PepitoGrilloX.
I've just downloaded this version and when I'm trying to open it, it says that the file is damaged. I've the new MacBook Air with M1 Processor. What's the main difference between aMule and aMule GUI / amused? I've always downloaded the first one which is just the file that I drag into the Aplications folder.
Hope you can help me since I'm looking forward to using it again!
Pepepinto
-
Thank you very much!
-
Thank you very much!
Did it work for you, The X?
I’m not able to make it run. It shows a message which says that the file is damaged.
Thanks.
-
macOS 11 (Big Sur) -- wxWidgets 3.14, with support for Dark Mode, and native M1 (arm64) binary!:
aMule GUI / amuled:https://www.dropbox.com/s/19hob4rye8za0k6/aMuleGUI-amuled-2.3.2-macOS_11-arm64-wxWidgets-3.1.4.zip?dl=0 (https://www.dropbox.com/s/19hob4rye8za0k6/aMuleGUI-amuled-2.3.2-macOS_11-arm64-wxWidgets-3.1.4.zip?dl=0)
Hi there, PepitoGrilloX.
I've just downloaded this version and when I'm trying to open it, it says that the file is damaged. I've the new MacBook Air with M1 Processor. What's the main difference between aMule and aMule GUI / amused? I've always downloaded the first one which is just the file that I drag into the Aplications folder.
Hope you can help me since I'm looking forward to using it again!
Pepepinto
Seems that Dropbox messed up the Zip file (8,4 MB in my system, 27 MB for Dropbox ..). I will re-download the zip.
aMule is the all-in-one app with the GUI and the "server" features coupled together. aMuleGUI is just the client side and it connect to a server that takes care of the background task (you can shutdown the client and the server continues, which is my use case).
-
I just got deeper into the problem, and it's not a Dropbox problem (it was an interpretation error).
However, I was right with my first impression: It is related to code sign re-inforcement done by Apple on the ARM64 architecture.
It is mandatory to code sign every app that runs on M1, so now I have to check if some kind of "ad-hoc" signature is valid for the binary sharing.
In the meantime, the Intel version through Rossetta2 can be used, because this tight rules imposed by Apple do not apply to x86_64 architecture (regardless if the machine runs Big Sur or not).
-
Updated binaries for Big Sur upgraded to the recent aMule 2.3.3 version just released!
These binaries have been code-signed, and notarized by Apple, and support Intel and M1 architectures natively. Take into consideration that to achieve that, the binaries have to follow also the tight sandboxing rules in place.
macOS 11 (Big Sur) -- wxWidgets 3.1.4, with support for Dark Mode! UNIVERSAL (x86_64 / ARM64):
aMuleGUI / amuled 2.3.3: https://www.dropbox.com/s/79wawwtui8hvka7/aMuleGUI-amuled-2.3.3-wxWidgets-3.1.4-macos11-universal.dmg?dl=0 (https://www.dropbox.com/s/79wawwtui8hvka7/aMuleGUI-amuled-2.3.3-wxWidgets-3.1.4-macos11-universal.dmg?dl=0)
-
Updated binaries for Big Sur upgraded to the recent aMule 2.3.3 version just released!
These binaries have been code-signed, and notarized by Apple, and support Intel and M1 architectures natively. Take into consideration that to achieve that, the binaries have to follow also the tight sandboxing rules in place.
macOS 11 (Big Sur) -- wxWidgets 3.1.4, with support for Dark Mode! UNIVERSAL (x86_64 / ARM64):
aMuleGUI / amuled 2.3.3: https://www.dropbox.com/s/79wawwtui8hvka7/aMuleGUI-amuled-2.3.3-wxWidgets-3.1.4-macos11-universal.dmg?dl=0 (https://www.dropbox.com/s/79wawwtui8hvka7/aMuleGUI-amuled-2.3.3-wxWidgets-3.1.4-macos11-universal.dmg?dl=0)
Thank you so much PepitoGrilloX! I try to open the new aMule app and there is a box like the one I attached in this message. I've always installed aMule, but it wasn't a GUI version (the icon is also different). What do I need to do to start using aMule? Isn't there a normal version?
Thanks for your help and work.
Francis
-
The binary is for aMuleGUI and it includes amuled (amule daemon).
/Applications/aMuleGUI.app/Contents/MacOS/amuled
I recommend to take a look on the documentation on regards amuled usage. You can start by:
https://www.systutorials.com/docs/linux/man/1-amuled/ (https://www.systutorials.com/docs/linux/man/1-amuled/)
Just take into consideration that the binaries are also "sandboxed", and by default, confined visibility to (search for Apple sandbox mechanism for details):
$HOME/Library/Containers/org.amule.aMuleGUI/Data
Sorry, but I just compiled the binaries. I am not the program developer.
-
However, the following binary works also on Big Sur, even with Rosetta2 translation on M1 architectures.
macOS 10.15 (Catalina):
aMule: https://www.dropbox.com/s/5brs48zfcvxn2db/aMule-2.3.2-macOS_10.15-wxWidgets-3.0.5.zip?dl=0 (http://aMule: https://www.dropbox.com/s/5brs48zfcvxn2db/aMule-2.3.2-macOS_10.15-wxWidgets-3.0.5.zip?dl=0)
Remember that the wxWidgets version used (3.0.5) do not support Dark mode, and, eventually (if you use Dark Mode, like myself), you will need to force "light" mode for this app:
defaults write org.amule.aMule NSRequiresAquaSystemAppearance -bool yes
-
The binary is for aMuleGUI and it includes amuled (amule daemon).
/Applications/aMuleGUI.app/Contents/MacOS/amuled
I recommend to take a look on the documentation on regards amuled usage. You can start by:
https://www.systutorials.com/docs/linux/man/1-amuled/ (https://www.systutorials.com/docs/linux/man/1-amuled/)
Just take into consideration that the binaries are also "sandboxed", and by default, confined visibility to (search for Apple sandbox mechanism for details):
$HOME/Library/Containers/org.amule.aMuleGUI/Data
Sorry, but I just compiled the binaries. I am not the program developer.
Thanks for your help, PepitoGrilloX. I took a look at the link you posted. To be honest, I know nothing about programming and I don’t understand what these commands do. I know how to use commands in terminal, but not these ones. The thing is that I thought this version you compiled had the normal version which is just as simple as opening it and start using it.
I know that I can use the one which isn’t adapted to M1 processors, but I’m trying to use just native apps. Don’t you have the version which isn’t the aMuleGUI version?
Thanks for your support and patience.
Pepepinto
-
Updated binaries for Big Sur upgraded to the recent aMule 2.3.3 version just released!
These binaries have been code-signed, and notarized by Apple, and support Intel and M1 architectures natively. Take into consideration that to achieve that, the binaries have to follow also the tight sandboxing rules in place.
macOS 11 (Big Sur) -- wxWidgets 3.1.4, with support for Dark Mode! UNIVERSAL (x86_64 / ARM64):
aMuleGUI / amuled 2.3.3: https://www.dropbox.com/s/79wawwtui8hvka7/aMuleGUI-amuled-2.3.3-wxWidgets-3.1.4-macos11-universal.dmg?dl=0 (https://www.dropbox.com/s/79wawwtui8hvka7/aMuleGUI-amuled-2.3.3-wxWidgets-3.1.4-macos11-universal.dmg?dl=0)
Thank you, maybe there is something wrong with my operation, the software can't be used?
I am from China and this text is generated by a translator. Hopefully that makes sense to you
macOS 11 + m1
-
Try to copy amuled outside de app container:
cp /Applications/aMuleGUI.app/Contents/MacOS/amuled <OTHER_PATH>
xattr -cr <OTHER_PATH>/amuled
codesign -fs - <OTHER_PATH>/amuled
You will need XCode for the commands (I guess), but, after that:
$ <OTHER_PATH>/amuled
2021-02-13 08:49:53: Initialising aMuleD 2.3.3 compiled with wxBase(OSX Cocoa) v3.1.4
!2021-02-13 08:49:53: WARNING: The check for other instances is currently disabled in amuled.
!2021-02-13 08:49:53: Please make sure that no other instance of aMule is running or your files might be corrupted.
!2021-02-13 08:49:53: Attempting to use default directory at location
!2021-02-13 08:49:53: '/Users/<USER>/Library/Application Support/aMule/Temp'.
!2021-02-13 08:49:53: Attempting to use default directory at location
!2021-02-13 08:49:53: '/Users/<USER>/Library/Application Support/aMule/Incoming'.
2021-02-13 08:49:53: ListenSocket: Ok.
2021-02-13 08:49:53: Loading temp files from /Users/<USER>/Library/Application Support/aMule/Temp.
2021-02-13 08:49:53: All PartFiles Loaded.
2021-02-13 08:50:03: amuled: OnInit - starting timer
!2021-02-13 08:50:03: ERROR: aMule daemon cannot be used when external connections are disabled. To enable External Connections, use either a normal aMule, start amuled with the option --ec-config or set the key "AcceptExternalConnections" to 1 in the file ~/.aMule/amule.conf
2021-02-13 08:50:04: Now, exiting main app...
2021-02-13 08:50:04: aMule OnExit: Terminating core.
2021-02-13 08:50:04: aMule shutdown completed.
And then, you will need to setup the aMule config files as required by amuled.
-
I just compiled, signed & notarized an aMule (regular) M1 version (ed2kHelpScript it has been removed to get GateKeeper to accept the binary, thanks Apple!)
macOS 11 (Big Sur) -- wxWidgets 3.0.5, M1 (ARM64):
aMule 2.3.3: https://www.dropbox.com/s/l0l3j35glwr8ytk/aMule-2.3.3-wxWidgets-3.0.5-macOS_11_arm64.dmg?dl=0 (https://www.dropbox.com/s/l0l3j35glwr8ytk/aMule-2.3.3-wxWidgets-3.0.5-macOS_11_arm64.dmg?dl=0)
-
I just compiled, signed & notarized an aMule (regular) M1 version (ed2kHelpScript it has been removed to get GateKeeper to accept the binary, thanks Apple!)
macOS 11 (Big Sur) -- wxWidgets 3.0.5, M1 (ARM64):
aMule 2.3.3: https://www.dropbox.com/s/l0l3j35glwr8ytk/aMule-2.3.3-wxWidgets-3.0.5-macOS_11_arm64.dmg?dl=0 (https://www.dropbox.com/s/l0l3j35glwr8ytk/aMule-2.3.3-wxWidgets-3.0.5-macOS_11_arm64.dmg?dl=0)
Thanks PepitoGrilloX for your help! It seems to work right now and there is a new interface which is really beautiful :)
The only problem that I have now is that I can't change Amule downloads directory, as it shows the error shown before. Do you know how can I fix this?
Thanks a lot for your hard work :)
-
As I said, to comply with Apple rules, the binaries needs to be "sandboxed", that means that they cannot freely access arbitrary paths on the system (unless specifically managed by the program).
As far as aMule do not have those restrictions in mind (Apple rules new rules requirements are not considered by the aMule program), it is recommended to use paths inside the sandbox (container) of the app:
$HOME/Library/Containers/org.amule.aMule/Data
Maybe soft "links" inside the container to the real folders can do the trick (but I never personally tested).
-
Btw, if you look at the error message, it is exactly what it is suggesting the aMule program (pay attention to the suggested default location) ... so pressing OK is safe ...
-
I see that inside the "sandbox" there are already links to the user common folders:
[/Users/<USER>/Library/Containers/org.amule.aMule/Data]
% ls -la
total 0
drwx------ 12 jgd staff 384 8 feb 12:36 .
drwx------@ 4 jgd staff 128 13 feb 09:14 ..
lrwxr-xr-x 1 jgd staff 31 8 feb 12:36 .CFUserTextEncoding -> ../../../../.CFUserTextEncoding
lrwxr-xr-x 1 jgd staff 19 8 feb 12:36 Desktop -> ../../../../Desktop
drwx------ 3 jgd staff 96 8 feb 12:36 Documents
lrwxr-xr-x 1 jgd staff 21 8 feb 12:36 Downloads -> ../../../../Downloads
drwx------ 30 jgd staff 960 8 feb 12:36 Library
lrwxr-xr-x 1 jgd staff 18 8 feb 12:36 Movies -> ../../../../Movies
lrwxr-xr-x 1 jgd staff 17 8 feb 12:36 Music -> ../../../../Music
lrwxr-xr-x 1 jgd staff 20 8 feb 12:36 Pictures -> ../../../../Pictures
drwx------ 2 jgd staff 64 8 feb 12:36 SystemData
drwx------ 2 jgd staff 64 8 feb 12:36 tmp
And so, I guess that using this folder for the downloads is the same, and it is not forbidden from the sandbox point of view:
/Users/<USER>/Library/Containers/org.amule.aMule/Data/Downloads
-
I see that inside the "sandbox" there are already links to the user common folders:
[/Users/<USER>/Library/Containers/org.amule.aMule/Data]
% ls -la
total 0
drwx------ 12 jgd staff 384 8 feb 12:36 .
drwx------@ 4 jgd staff 128 13 feb 09:14 ..
lrwxr-xr-x 1 jgd staff 31 8 feb 12:36 .CFUserTextEncoding -> ../../../../.CFUserTextEncoding
lrwxr-xr-x 1 jgd staff 19 8 feb 12:36 Desktop -> ../../../../Desktop
drwx------ 3 jgd staff 96 8 feb 12:36 Documents
lrwxr-xr-x 1 jgd staff 21 8 feb 12:36 Downloads -> ../../../../Downloads
drwx------ 30 jgd staff 960 8 feb 12:36 Library
lrwxr-xr-x 1 jgd staff 18 8 feb 12:36 Movies -> ../../../../Movies
lrwxr-xr-x 1 jgd staff 17 8 feb 12:36 Music -> ../../../../Music
lrwxr-xr-x 1 jgd staff 20 8 feb 12:36 Pictures -> ../../../../Pictures
drwx------ 2 jgd staff 64 8 feb 12:36 SystemData
drwx------ 2 jgd staff 64 8 feb 12:36 tmp
And so, I guess that using this folder for the downloads is the same, and it is not forbidden from the sandbox point of view:
/Users/<USER>/Library/Containers/org.amule.aMule/Data/Downloads
So what do you suggest then? As you said, downloads folder seems to be included.
Should I select other location like documents folder or something like that?
Thanks for all your support 😉
-
Another option is to do it on reverse, and create a link from your standard "Downloads" folder. This will work for sure (from the Terminal command line):
$ ln -s "/Users/<USER>/Library/Containers/org.amule.aMule/Data/Documents/aMule Downloads" "/Users/<USER>/Downloads/aMule"
As far as I see this is the default location when you start from scratch. You will see inside the standard "Downloads" folder a direct alias to the aMule downloads folder inside the sandbox (which is safer).
-
Another option is to do it on reverse, and create a link from your standard "Downloads" folder. This will work for sure (from the Terminal command line):
$ ln -s "/Users/<USER>/Library/Containers/org.amule.aMule/Data/Documents/aMule Downloads" "/Users/<USER>/Downloads/aMule"
As far as I see this is the default location when you start from scratch. You will see inside the standard "Downloads" folder a direct alias to the aMule downloads folder inside the sandbox (which is safer).
Done, PepitoGrilloX! I’ve just created an alias from “Incoming” folder on my downloads folder so I can access all my files easily. It’s such a great idea. By the way, it’s such a pity that aMule isn’t ready for the new Apple changes.
I have another more question: Are you Spanish? 😁
Thanks for your support and patience 😊
-
I'm glad that worked for you.
N.B: Yes, I am spanish ;)
-
I just compiled, signed & notarized an aMule (regular) M1 version (ed2kHelpScript it has been removed to get GateKeeper to accept the binary, thanks Apple!)
macOS 11 (Big Sur) -- wxWidgets 3.0.5, M1 (ARM64):
aMule 2.3.3: https://www.dropbox.com/s/l0l3j35glwr8ytk/aMule-2.3.3-wxWidgets-3.0.5-macOS_11_arm64.dmg?dl=0 (https://www.dropbox.com/s/l0l3j35glwr8ytk/aMule-2.3.3-wxWidgets-3.0.5-macOS_11_arm64.dmg?dl=0)
;D Thank you. The software is working now。But the UPNP button is gray
-
Yes, UPNP is disabled for security concerns.
-
I just compiled, signed & notarized an aMule (regular) M1 version (ed2kHelpScript it has been removed to get GateKeeper to accept the binary, thanks Apple!)
macOS 11 (Big Sur) -- wxWidgets 3.0.5, M1 (ARM64):
aMule 2.3.3: https://www.dropbox.com/s/l0l3j35glwr8ytk/aMule-2.3.3-wxWidgets-3.0.5-macOS_11_arm64.dmg?dl=0 (https://www.dropbox.com/s/l0l3j35glwr8ytk/aMule-2.3.3-wxWidgets-3.0.5-macOS_11_arm64.dmg?dl=0)
Thank you for releasing the binaries, but I'm on an Intel Mac so is there a universal or x86_64 version of the monolithic aMule app?
-
aMule (x86_64): https://www.dropbox.com/s/5brs48zfcvxn2db/aMule-2.3.2-macOS_10.15-wxWidgets-3.0.5.zip?dl=0 (https://www.dropbox.com/s/5brs48zfcvxn2db/aMule-2.3.2-macOS_10.15-wxWidgets-3.0.5.zip?dl=0)
Force light mode:
defaults write org.amule.aMule NSRequiresAquaSystemAppearance -bool yes
-
I just compiled, signed & notarized an aMule (regular) M1 version (ed2kHelpScript it has been removed to get GateKeeper to accept the binary, thanks Apple!)
macOS 11 (Big Sur) -- wxWidgets 3.0.5, M1 (ARM64):
aMule 2.3.3: https://www.dropbox.com/s/l0l3j35glwr8ytk/aMule-2.3.3-wxWidgets-3.0.5-macOS_11_arm64.dmg?dl=0 (https://www.dropbox.com/s/l0l3j35glwr8ytk/aMule-2.3.3-wxWidgets-3.0.5-macOS_11_arm64.dmg?dl=0)
Thank you for releasing the binaries, but I'm on an Intel Mac so is there a universal or x86_64 version of the monolithic aMule app?
I join the request for a working aMule 2.3.3 binary for Big Sur + Intel processors, since the 2.3.2 binary for MacOS Catalina (https://www.dropbox.com/s/5brs48zfcvxn2db/aMule-2.3.2-macOS_10.15-wxWidgets-3.0.5.zip?dl=0) is crashing on my MacOS 11.2.1. Thank you in advance for your work.
-
Hi PepitoGrilloOOSX, I'm on Mojave, and I downloaded the 2.3.2 version, it works perfectly, only some graphical problem (I use dark mode). Does the command "defaults write... " work also in Mojave?
Is there a 2.3.3 version for Mojave or last is 2.3.2?
Thanks
Edit: I searched on internet and found that command "defaults write org.amule.aMule NSRequiresAquaSystemAppearance 1" does the trick on Mojave (1 for forcing light mode and 0 for forcing dark mode), so this is ok now;
what about the second question? ;D
-
macOS 11 (Big Sur) -- wxWidgets 3.0.5, Intel (x86_64):
aMule 2.3.3: https://www.dropbox.com/s/vdhcxp6y7n50xpa/aMule-2.3.3-wxWidgets-3.0.5-macos11-x86_64.dmg?dl=0 (https://www.dropbox.com/s/vdhcxp6y7n50xpa/aMule-2.3.3-wxWidgets-3.0.5-macos11-x86_64.dmg?dl=0)
It is not signed, notarized or sandboxed because it is not mandatory in the Intel architecture.
I will think on an universal version (Intel + M1), combining both binaries (signed, notarized and sandboxed).
-
macOS 11 (Big Sur) -- wxWidgets 3.0.5, Intel (x86_64):
aMule 2.3.3: https://www.dropbox.com/s/vdhcxp6y7n50xpa/aMule-2.3.3-wxWidgets-3.0.5-macos11-x86_64.dmg?dl=0 (https://www.dropbox.com/s/vdhcxp6y7n50xpa/aMule-2.3.3-wxWidgets-3.0.5-macos11-x86_64.dmg?dl=0)
It is not signed, notarized or sandboxed because it is not mandatory in the Intel architecture.
I will think on an universal version (Intel + M1), combining both binaries (signed, notarized and sandboxed).
Thanks, but the bundle version in the plist is still 2.3.2. The app it self is indeed 2.3.3.
-
New web location for all the binaries:
https://sourceforge.net/projects/amule-macos-binaries/files/ (https://sourceforge.net/projects/amule-macos-binaries/files/)
-
Hi, from the listed files I assume there is not a 2.3.3 for Mojave, right?
-
Right
-
A new "universal" binary it is available for aMule 2.3.3 at the official aMule download site at SourceForge:
macOS 11 (Big Sur) -- wxWidgets 3.0.5, Universal (ARM64 / x86_64)
aMule 2.3.3: https://sourceforge.net/projects/amule/files/aMule/2.3.3/ (https://sourceforge.net/projects/amule/files/aMule/2.3.3/)
It is code signed, sandboxed and notarized as requested by Apple.
-
macOS 11 (Big Sur) -- wxWidgets 3.0.5, Intel (x86_64):
aMule 2.3.3: https://www.dropbox.com/s/vdhcxp6y7n50xpa/aMule-2.3.3-wxWidgets-3.0.5-macos11-x86_64.dmg?dl=0 (https://www.dropbox.com/s/vdhcxp6y7n50xpa/aMule-2.3.3-wxWidgets-3.0.5-macos11-x86_64.dmg?dl=0)
It is not signed, notarized or sandboxed because it is not mandatory in the Intel architecture.
I will think on an universal version (Intel + M1), combining both binaries (signed, notarized and sandboxed).
Thanks, but the bundle version in the plist is still 2.3.2. The app it self is indeed 2.3.3.
The new universal binary for macOS 11 Big Sur fixes also this issue.
-
Thank you.
They work great.
The only thing is that the contrast is not very good:
https://imgur.com/a/yG4KlpW(https://imgur.com/a/yG4KlpW)
-
Thank you.
They work great.
The only thing is that the contrast is not very good:
https://imgur.com/a/yG4KlpW(https://imgur.com/a/yG4KlpW)
wxWidgets 3.0.5 does not support macOS Dark Mode. You have to "force" light mode for aMule (as shown in previous posts):
defaults write org.amule.aMule NSRequiresAquaSystemAppearance -bool yes
-
A new "universal" binary it is available for aMule 2.3.3 at the official aMule download site at SourceForge:
macOS 11 (Big Sur) -- wxWidgets 3.0.5, Universal (ARM64 / x86_64)
aMule 2.3.3: https://sourceforge.net/projects/amule/files/aMule/2.3.3/ (https://sourceforge.net/projects/amule/files/aMule/2.3.3/)
It is code signed, sandboxed and notarized as requested by Apple.
This universal binary has become the official aMule compilation for macOS, and from now on, you can download it from the Download section at the aMule web site.
https://sourceforge.net/projects/amule/files/aMule/2.3.3/ (https://sourceforge.net/projects/amule/files/aMule/2.3.3/)
-
wxWidgets 3.0.5 does not support macOS Dark Mode. You have to "force" light mode for aMule (as shown in previous posts):
defaults write org.amule.aMule NSRequiresAquaSystemAppearance -bool yes
Thank you, it fixes it.
I'm now facing a problem with uPnP. The option is grayed out.
You said it is disabled for security reasons.
Why is that?
Could we manually enable it?
In amule.conf it is enabled, but still, grayed out in the app.
-
wxWidgets 3.0.5 does not support macOS Dark Mode. You have to "force" light mode for aMule (as shown in previous posts):
defaults write org.amule.aMule NSRequiresAquaSystemAppearance -bool yes
Thank you, it fixes it.
I'm now facing a problem with uPnP. The option is grayed out.
You said it is disabled for security reasons.
Why is that?
Could we manually enable it?
In amule.conf it is enabled, but still, grayed out in the app.
The library it is not linked in the binary, so there is nothing that can be manually done.
-
A new "universal" binary it is available for aMule 2.3.3 at the official aMule download site at SourceForge:
macOS 11 (Big Sur) -- wxWidgets 3.0.5, Universal (ARM64 / x86_64)
aMule 2.3.3: https://sourceforge.net/projects/amule/files/aMule/2.3.3/ (https://sourceforge.net/projects/amule/files/aMule/2.3.3/)
It is code signed, sandboxed and notarized as requested by Apple.
This universal binary has become the official aMule compilation for macOS, and from now on, you can download it from the Download section at the aMule web site.
https://sourceforge.net/projects/amule/files/aMule/2.3.3/ (https://sourceforge.net/projects/amule/files/aMule/2.3.3/)
Thank you, the Big Sur interface is very cool!
But what about aMuled and aMuleGUI? They are not included in this package and all the previous ones have been deleted
-
A new "universal" binary it is available for aMule 2.3.3 at the official aMule download site at SourceForge:
macOS 11 (Big Sur) -- wxWidgets 3.0.5, Universal (ARM64 / x86_64)
aMule 2.3.3: https://sourceforge.net/projects/amule/files/aMule/2.3.3/ (https://sourceforge.net/projects/amule/files/aMule/2.3.3/)
It is code signed, sandboxed and notarized as requested by Apple.
This universal binary has become the official aMule compilation for macOS, and from now on, you can download it from the Download section at the aMule web site.
https://sourceforge.net/projects/amule/files/aMule/2.3.3/ (https://sourceforge.net/projects/amule/files/aMule/2.3.3/)
Thank you, the Big Sur interface is very cool!
But what about aMuled and aMuleGUI? They are not included in this package and all the previous ones have been deleted
The full set of binaries can be found here (although is not the official aMule location):
https://sourceforge.net/projects/amule-macos-binaries/files/ (https://sourceforge.net/projects/amule-macos-binaries/files/)
-
A new "universal" binary it is available for aMule 2.3.3 at the official aMule download site at SourceForge:
macOS 11 (Big Sur) -- wxWidgets 3.0.5, Universal (ARM64 / x86_64)
aMule 2.3.3: https://sourceforge.net/projects/amule/files/aMule/2.3.3/ (https://sourceforge.net/projects/amule/files/aMule/2.3.3/)
It is code signed, sandboxed and notarized as requested by Apple.
This universal binary has become the official aMule compilation for macOS, and from now on, you can download it from the Download section at the aMule web site.
https://sourceforge.net/projects/amule/files/aMule/2.3.3/ (https://sourceforge.net/projects/amule/files/aMule/2.3.3/)
Thank you, the Big Sur interface is very cool!
But what about aMuled and aMuleGUI? They are not included in this package and all the previous ones have been deleted
The full set of binaries can be found here (although is not the official aMule location):
https://sourceforge.net/projects/amule-macos-binaries/files/ (https://sourceforge.net/projects/amule-macos-binaries/files/)
Thank you!
-
WOW arm64 build!
Many thanks PepitoGrilloOSX ;)
-
WOW arm64 build!
Many thanks PepitoGrilloOSX ;)
You're welcome.
There is also the universal build (x86_64 + arm64).
-
Any chances that 2.3.3 (or 2.4.0) will be ported to MacOS 10.x? Just asking. Many of us have perfectly good Macs from 2015 which can't run Big Sur :)
-
Thanks PepitoGrilloOSX for your work.
Seems the notarized version has problems changing the incoming and temp directories. The old non notarized version is working as expected.
(https://i.postimg.cc/cC4Nh53Y/temp.png)
(https://i.postimg.cc/XvfSb0cd/incoming.png)
-
Any chances that 2.3.3 (or 2.4.0) will be ported to MacOS 10.x? Just asking. Many of us have perfectly good Macs from 2015 which can't run Big Sur :)
Sorry, but I do not own myself all the Apple hardware needed to compile for different OS versions.
You can use previous compiled versions as a workaround.
-
Thanks PepitoGrilloOSX for your work.
Seems the notarized version has problems changing the incoming and temp directories. The old non notarized version is working as expected.
(https://i.postimg.cc/cC4Nh53Y/temp.png)
(https://i.postimg.cc/XvfSb0cd/incoming.png)
This is related to the "sandboxing" of the application, not with the notarization. Unfortunately, aMule base code is not Apple "sandbox" aware, which means that it does not ask for access permissions to user for the paths outside the sandbox, and so, macOS blocks the access.
Right now I am working in a new binary, trying to avoid the sandboxing limitations, and adding "dark mode" support to aMule 2.3.3.
Well see...
-
Right now I am working in a new binary, trying to avoid the sandboxing limitations, and adding "dark mode" support to aMule 2.3.3.
Well see...
Many thanks :)
-
OMG arm64 build!
thanks
-
Finally!!
I new Universal2 macOS binary is available (look in the official download area).
aMule-2.3.3-wxWidgets-3.1.5-macOS11-Universal2.dmg:
- wxWidgets 3.1.5 (dark mode support)
- Not sandboxed (no path access restrictions)
-
Copying the ed2kHelperScript form version 2.3.2 to the last one (aMule-2.3.3-wxWidgets-3.1.5-macOS11-Universal2) works flawlessly.
Cheers
-
I'm getting: "zsh: illegal hardware instruction" when executing the "amuled" from "aMuleGUI-amuled-2.3.3-wxWidgets-3.1.4-macos11-universal.dmg"
-
The most up-to-date binaries are available at:
https://sourceforge.net/projects/amule/files/aMule/2.3.3/ (https://sourceforge.net/projects/amule/files/aMule/2.3.3/)
(None of the binaries has that name, so I guess there is some "typo")
Anyway, DMGs are not meant to be "executed". They need to be "mounted" (double click the file), and then, the contents and the installer will be accesible.
-
Copying the ed2kHelperScript form version 2.3.2 to the last one (aMule-2.3.3-wxWidgets-3.1.5-macOS11-Universal2) works flawlessly.
Cheers
Thanks. The problem with that is that I am not sure if this will be 100% "universal" (x86_64 + arm64).
-
Thanks
The DNG is from the unofficial repository: https://sourceforge.net/projects/amule-macos-binaries/files/
The "amuled" is accessed using terminal directly from "/Applications/aMuleGUI.app/Contents/MacOS/amuled", not from the mounted DNG. Result is "zsh: illegal hardware instruction"
-
PepitoGrilloOSX please, would you share the configure command to compile amuleGUI? THANKS!
-
You can try this alternative one if you want:
https://sourceforge.net/projects/amule-macos-binaries/files/aMuleGUI-amuled-2.3.3-wxWidgets-3.1.5-macOS11-Universal2.dmg/download (https://sourceforge.net/projects/amule-macos-binaries/files/aMuleGUI-amuled-2.3.3-wxWidgets-3.1.5-macOS11-Universal2.dmg/download)
It is an Universal2 binary that works from macOS 11 (and in macOS 12):
% lipo -info /Applications/aMuleGUI.app/Contents/MacOS/amuled
Architectures in the fat file: /Applications/aMuleGUI.app/Contents/MacOS/amuled are: x86_64 arm64
% /Applications/aMuleGUI.app/Contents/MacOS/amuled
2021-12-15 22:04:44: Initialising aMuleD 2.3.3 compiled with wxBase(OSX Cocoa) v3.1.5
!2021-12-15 22:04:44: WARNING: The check for other instances is currently disabled in amuled.
!2021-12-15 22:04:44: Please make sure that no other instance of aMule is running or your files might be corrupted.
...
For compiling yourself, please, refer to the official instructions and make sure to use the "--enable-amule-gui" and "--enable-amule-daemon" options at the "configure" phase.
-
wxWidgets 3.0.5 does not support macOS Dark Mode. You have to "force" light mode for aMule (as shown in previous posts):
defaults write org.amule.aMule NSRequiresAquaSystemAppearance -bool yes
Thank you, it fixes it.
I'm now facing a problem with uPnP. The option is grayed out.
You said it is disabled for security reasons.
Why is that?
Could we manually enable it?
In amule.conf it is enabled, but still, grayed out in the app.
The library it is not linked in the binary, so there is nothing that can be manually done.
For those be troubled by low-id because of lack upnp feature, you may setup upnp by yourselves. Just open terminal window to run:
port install miniupnpc
upnpc -r 4321 UDP 8765 TCP # change port number or add more port-proto
If you don't have MacPorts, search and install it firstly.
-
wxWidgets 3.0.5 does not support macOS Dark Mode. You have to "force" light mode for aMule (as shown in previous posts):
defaults write org.amule.aMule NSRequiresAquaSystemAppearance -bool yes
Thank you, it fixes it.
I'm now facing a problem with uPnP. The option is grayed out.
You said it is disabled for security reasons.
Why is that?
Could we manually enable it?
In amule.conf it is enabled, but still, grayed out in the app.
The library it is not linked in the binary, so there is nothing that can be manually done.
For those be troubled by low-id because of lack upnp feature, you may setup upnp by yourselves. Just open terminal window to run:
port install miniupnpc
upnpc -r 4321 UDP 8765 TCP # change port number or add more port-proto
If you don't have MacPorts, search and install it firstly.
Nice one!