Closed tobbi closed 3 years ago
That’s rather annoying it should have used the i386 slice on Mojave and only used the x86_64 slice on Catalina and later.
If you’ve installed via my brew tap it won’t affect the installed symlinks only the actual app bundle.
@tobbi I see the problem you attempted to directly launch /Applications/Wine Devel.app/Contents/MacOS/wine
via terminal that does indeed throw an error.
Was there a reason for directly launching the wine
binary wrapper?, as the actual wine binaries are located in '/Applications/Wine Devel.app/Contents/Resources/wine/bin'
Testing directly launching the app bundle and launched Terminal session correctly when provided the requested permission, also tested "open with" this also functioned correctly.
Okay, I tried that, but a) it takes a while to run and b) the terminal window that gets opened shows this:
################################################################################
# Wine Is Not an Emulator #
################################################################################
/Applications/Wine Devel.app/Contents/Resources/start/bin/winehelp: line 41: wine: command not found
Welcome to .
In order to start a program:
.exe: wine program.exe
.msi: wine msiexec /i program.msi
If you want to configure wine:
wine winecfg
To get information about app compatibility:
appdb Program Name
Entering wine
into the console window tells me that wine wasn't found.
Trash the app and download it again preferably with my brew tap so wine
gets installed into your user $PATH
Look like you download it before I’d re-uploaded.
You're right. It's working now. Thanks!
When I start 6.11 on 10.14.6, I get the following error.