Mustard on MacOs

[valarmorghulis23]

Hello,

I downloaded the zip file but I'm clueless as to what to do next. When extracted, the zip file is loaded with about a hundred .dll files which are for windows. I don't know how to get the GUI to run to open the wallet itself. The link to the installation guide takes you to Wasabi wallet which has a .dmg guide. How do I get this to run?

[nopara73]

The file format is .dll on OSX and Linux, too, no worry about that. I'm not sure if the installation process is different from Wasabi's, but if it isn't, then here's something you can get started with: https://docs.wasabiwallet.io/using-wasabi/InstallPackage.html#macos

[valarmorghulis23]

The file format is .dll on OSX and Linux, too, no worry about that. I'm not sure if the installation process is different from Wasabi's, but if it isn't, then here's something you can get started with: https://docs.wasabiwallet.io/using-wasabi/InstallPackage.html#macos

Thank you for your reply and for clarification on the .dll files! The issue is that Mustard doesn't have a .dmg file like Wasabi does (I have wasabi running on my mac), Mustard only has a .zip file. I'm not sure how to install the program on mac with the files inside of the zip.

[nopara73]

I don't have a testing mac at hand, but I looked into it and I think the mustardwalletltc file will be the one that you can start. If it doesn't work, then I think you can try to launch WalletWasabi.Gui.dll.

In wasabi the wassabee launcher is pointing to the WalletWasabi.Gui.dll, so that's where I'm coming from. Anyhow, I hope something helped here.

[valarmorghulis23]

'mustardwalletltc' opens up a terminal window:

'WalletWasabi.Gui.dll' doesn't open at all because .dll is not recognized by Mac =\

[nopara73]

Alright, so did a quick test with Wasabi on OSX. Here's what I found.

1. I opened the folder where Wasabi was installed on Mac. I believe this is the same folder what Mustard is shipping, it just doesn't install like Wasabi.
2. I opened a terminal in that folder.
3. Then I tried ./wassabee which launched Wasabi. I believe mustardwalletltc is the equivalent to wassabee file, so you'd do ./mustardwalletltc here. In case it still doesn't work you may try sudo ./mustardwalletltc, which would open Mustard with administrator privileges, which isn't recommended, but there may be no other way to do this if the software isn't Apple signed (please smarter people correct me on this if I'm wrong.)
4. The next thing I tried is to do ./WalletWasabi.Gui.dll which just did not work, so I suppose I was dead wrong on that one.

I hope I was helpful.

[gabrielkrieger]

Thanks for testing this and chiming in , really appreciated !

Executing "mustardwalletltc" by doing "./mustardwalletltc" from Bash should indeed work, as it does with "./wassabee" of Wasabi .

I see that for you 'mustardwalletltc' opens up a Terminal that shows the contents of this file instead of executing it ...

Can you try executing that file somehow ? If you don't like doing it in bash / terminal then waybe right click and "run" or first "properties" and give it the "executable" permission and then click it ...

[valarmorghulis23]

Thank you both for the advice!

I tried running the file using the ./mustardwalletltc command (with sudo as well) in terminal and it did the same thing; opened a terminal window showing the contents of the file.

I then converted 'mustardwalletltc' to an executable in terminal and tried again. This time I received an error about file verification:

When I hit cancel, I received about 25 other similar messages referencing other .dylib and .dll files in the folder. I read the error report in terminal which recommended updating .NET. I updated it and tried again and got the exact same problem.

[gabrielkrieger]

Ah , I heard about this MacOS signature verification stuff . I guess it can be disabled on MacOS somehow but I know that's not a user friendly solution . The good solution will be to properly sign those files during the build .

Did you try with "sudo ./mustardwalletltc" as nopara suggested ? Maybe that gets rid of those warnings .

Another way to go is to run the GUI from source . It's pretty easy if you have .NET installed . Just download the source code from GitHub and do a "dotnet run" in the "WalletWasabi.Gui" folder . Full documentation on building from source is available on docs.wasabiwallet.io . Obviously this is not something we can expect all MacOS users to do , just a temporary solution for you ...

[valarmorghulis23]

Okay thanks, I'll try that. When do you think Mac users can expect a .dmg for Mustard? I think that would be most helpful and to streamline this entire process. I imagine I'm not the only Mac user who will run into this issue.

[gabrielkrieger]

Good question :D This is high on my priority list , merely because the users are asking for it pretty strongly ;)

Signing the dmg for MacOS is not trivial though . According to the docs , step 1 is "Get a macintosh machine." and I'm still working on that one right now . I want to try to do the signing in a VM on an older version of MacOS . Bad idea ?

Ideally I should get a fancy physical MacOS laptop so I can properly build - and test - the MacOS builds ... maybe I should prioritize a " wish list / bounties / donations " program already :D

Anyway , I'm hoping to be able to start delivering dmg builds in a matter of weeks , maybe days !

[gabrielkrieger]

Still working on it ...

[xanoni]

building it was straight forward ... dotnet build and and then just dotnet run ...