Главная » Linux

Wine 32 bit mac os

Содержание
  1. Wine 32 bit mac os
  2. Как запускать 32-битные приложения в macOS Catalina
  3. Какие 32-битные приложения вообще могут понадобиться
  4. Что же теперь делать
  5. Как установить macOS Mojave на виртуальную машину
  6. Wine 32 bit mac os

Wine 32 bit mac os

Copy raw contents

How to install/about wine on mac

As this question keeps appearing more recently I’m making this basic guide.

  • Install XQuartz 2.7.7 or above
  • Gatekeeper must allow block unsigned packages
  • Running OS X 10.8 to macOS 10.14* (macOS Catalina & later)

Recommended way to install Winehq packages;

Installing wine using homebrew Once homebrew is installed you the following command to install your selected wine package

The above command will install XQuartz and the most recent wine-staging pkg available on winehq but it will also add wine for use in Terminal meaning you no longer need to launch the installed Wine Staging app each time you want to access wine.

Please Note;
Only a single wine package can be installed using brew
The —no-quarantine command is required as homebrew by default adds the quarantine flag to downloaded casks, this causes Gatekeeper to treat the bundle as damaged.

Winehq is currently not providing recent packages for macOS so I decided to upload my own builds.

This command will add my brew tap and the second command will install my custom cask of Wine Staging

The tap contains the following

  • gcenx-wine-stable
  • gcenx-wine-devel
  • gcenx-wine-staging
  • wine-crossover

How to manually install wine on mac using Winehq releases;

Grab a wine package usually using the latest wine-devel is recommended, but most agree it’s best to use the latest wine-staging due to additional patches.
If your intention is to have a more stable environment use wine-stable

The above is the Winehq way to install wine on mac but that makes it cumbersome to use considering you must launch the Wine Stable , Wine Devel or Wine Staging app each time to get access to wine within Terminal

The default WINEPREFIX will be

/.wine so anything you install will be placed into the hidden

/.wine folder. You can override this by using the WINEPREFIX command

The default architecture of a WINEPREFIX will be 64Bit meaning 32Bit and 64Bit applications & games are supported but that’s not always ideal for several reasons. A new WINEPREFIX can be created and also setting WINEARCH

Here is an example of using both commands to create a 32Bit only WINEPREFIX

The above command will create a new WINEPREFIX thats also 32Bit only and launch winecfg

Basic wine tools

  • wine (32Bit loader)
  • wine64 (64Bit loader)
  • msiexec (execute msi files
  • notepad
  • regedit (Wines Registry editor)
  • regsvr32 (Provides DLL registration services)
  • wineboot
  • winecfg (wine configuration utility)
  • wineconsole (windows like shell aka cmd)
  • winedbg (wine debug utility)
  • winefile (wine file manager)
  • winemine (wines version of the game mine)
  • winepath

What’s this winetricks everyone keeps saying to use?

Winetricks is an easy way to work around problems in Wine.

While winetricks can be installed directly from GitHub you will be missing packages winetricks requires, instead install again using homebrew

Now you will also have access to winetricks command within Terminal

Why doesn’t Virtual Desktop work?

By default wine on mac uses what’s known as macDriver using winetricks run the following command

This will swap from macDriver to x11 now wine will make use of XQuartz

Why doesn’t my game work on mac but Winehq says it does?

This usually happens when the game uses DirectX10 or above, the version of OpenGL included on macOS hasn’t been updated in years so it’s missing some needed extensions.

Читайте также:  Настройка ftp linux red hat

Can I use DXVK on mac?

No not currently.
MoltenVK is Vulkan 1.1 compliant, but still missing additional extensions needed by DXVK.
MoltenVK uses Metal meaning only wine64 has Vulkan support (currently wine32on64 doesn’t support MoltenVK).

Please Note;
CrossOver-20 does include DXVK support, this provides DirectX10 and DirectX11 support. CodeWeavers patched MoltenVK to fake unsupported extensions and a custom version of DXVK that’s modified specifically for macOS.

macOS Catalina and later

Currently only CrossOver-19 and later will run

Here are some free alternatives;

  • Unofficial Wineskin Use a WS11 Engine
  • PortingKit Should automatically select a working Engine
  • My brew tap

Gatekeeper will give a warning for each Windows binary that is ran as these won’t be code-signed in a way Apple expects, to avoid this you could disabled Gatekeeper using the following command

Please Note;
macOS Catalina 10.15.0 to 10.15.3, SIP needs to be disabled this will allow wine32on64 to change the state of i386_set_ldt

My current wine-crossover package can be downloaded directly WineCX19.02
Phoenicis has a build of WineCX19.0.0

Also;
wine32on64 currently does not support 16Bit executable so some things just won’t work

Apple Silicon support?

Only CrossOver-20.0.2 includes support for Apple Silicon at this time, this requires macOS Big Sur 11.1 and install Rosetta2.
I will be adding support for Apple Silicon into Wineskin once I’m able to obtain an M1 Mac mini, currently checking where would be the best place to purchase from.

Using wine in a macOS Virtual Machine

From Wine-4.15 to Wine-5.16 macDriver (the default display driver) won’t function within a Virtual Machine, however the X11 display driver works.
You can edit the wine registry manually or use winetricks

Please Note; The macDriver regression was resolved from Wine-5.17

Wine-5.9 to Wine-5.18 file limit regression;

The upstream patch was applied to my recently uploaded Wine-5.17 packages
The most commonly noticed issues was wine-gecko was always crashing.

Источник

Как запускать 32-битные приложения в macOS Catalina

Перед выходом macOS Catalina мы рассказывали о важном изменении этой операционной системы.

Купертиновцы прекратили поддержку 32-битных программ. Все приложения без соответствующего апдейта просто не заработают в macOS 10.15 и более поздних версиях операционной системы от Apple.

Чтобы продолжить их использовать, самый лучший метод — просто поставить предыдущую версию macOS на виртуальную машину. Сейчас объясню, как это сделать.

? Спасибо re:Store за полезную информацию. ?

Какие 32-битные приложения вообще могут понадобиться

У каждого пользователя список свой. Мне, например, не хватает четырёх программ, которыми я часто пользовался вплоть до macOS Mojave.

Больше не поддерживаются: удобный переключатель языка ввода по клавише CapsLock – Capster, стриминговый плеер SopCast, приложение для цифрового микроскопа Digital Viewer и программа для работы с трехмерными моделями конструктора Lego Digital Designer.

От первых двух пришлось отказаться полностью, а второй паре нашел 64-битные аналоги: Plugable Digital Viewer и Studio 2.0.

На несколько месяцев я забыл о проблеме с 32-битными приложениями, пока во время новогодних каникул не решил поиграть во что-то на своем Mac.

Да, компьютеры Apple не позиционируются как геймерские. Но есть множество приложений и игр 5-7 летней давности, которые отлично работают даже на Mac mini и MacBook Air без дискретной графики.

Купленные давным-давно DiRT 3, Borderlands и Mafia II пропали с виртуальных полок Mac App Store. Нет там и старых любимых платформеров, вроде Trine.

Не порадовал визит в раздел с играми для Mac на сайте Steam.

На странице большинства купленных ранее игр красовался баннер об отсутствии поддержки Catalina.

Что же теперь делать

Если вам необходимо запустить 32-битные приложения, а компьютер уже обновлен до macOS Catalina, есть такие варианты выхода из ситуации:

Читайте также:  Artmoney для windows 10 крякнутый

▸ установить macOS Mojave в качестве второй системы на Mac;

▸ установить Windows через BootCamp и использовать программы или игры для этой ОС;

▸ дождаться обновления контейнера Wine для запуска 32-битных приложений. Работа ведется, но есть определенные трудности и четкие сроки выхода такой версии разработчики пока не называют.

▸ использовать виртуальную машину с установленной системой macOS Mojave и ниже.

Последний способ самый предпочтительный, так не придется перезагружать компьютер и запускать другую операционную систему, чтобы запустить нужное приложение.

Как установить macOS Mojave на виртуальную машину

1. Для начала определимся с используемым приложением. Можете выбрать любое популярное решение: VMWare, VirtualBox или Parallels.

В данном примере будем использовать утилиту Parallels Desktop, в других программах процесс установки будет схожим.

2. Теперь нужно скачать подходящую версию macOS. Купертиновцы любезно скрыли старые версии macOS и их нельзя найти через поиск в Mac App Store.

К счастью, можно воспользоваться прямыми ссылками: скачать macOS 10.14 Mojave или macOS 10.13 High Sierra.

3. Запускаем приложение для создания виртуальной машины и через меню Файл – Новый создаем новую систему.

4. Выбираем пункт Установить Windows или другую ОС с DVD или из образа.

5. Подтверждаем установку из загруженного образа macOS или вручную указываем путь к инсталлятору.

6. Подтверждаем выделение необходимого места на диске под образ системы.

7. Производим привычную установку и настройку macOS в окне виртуальной машины.

8. После установки в настройках виртуальной машины не забываем предоставить доступ к сети и оборудованию компьютера. При необходимости следует изменить предоставляемые виртуальной машине ресурсы (оперативную и видеопамять).

И в самом конце предоставляем доступ ко всем дискам или выделенным папкам на Mac, чтобы быстро копировать данные между основной системой и виртуальной.

9. Перезапускаем виртуальную машину для вступления изменений в силу.

Все! Теперь можно устанавливать и использовать старые 32-битные приложения.

На данный момент это самый удобный способ использовать нужные программы и игры, поддержка которых пропала в macOS Catalina.

Источник

Wine 32 bit mac os

How to install/about wine on mac

As this question keeps appearing more recently I’m making this basic guide.

  • Install XQuartz 2.7.7 or above
  • Gatekeeper must allow block unsigned packages
  • Running OS X 10.8 to macOS 10.14* (macOS Catalina & later)

Recommended way to install Winehq packages;

Installing wine using homebrew Once homebrew is installed you the following command to install your selected wine package

The above command will install XQuartz and the most recent wine-staging pkg available on winehq but it will also add wine for use in Terminal meaning you no longer need to launch the installed Wine Staging app each time you want to access wine.

Please Note;
Only a single wine package can be installed using brew
The —no-quarantine command is required as homebrew by default adds the quarantine flag to downloaded casks, this causes Gatekeeper to treat the bundle as damaged.

Winehq is currently not providing recent packages for macOS so I decided to upload my own builds.

This command will add my brew tap and the second command will install my custom cask of Wine Staging

The tap contains the following

  • gcenx-wine-stable
  • gcenx-wine-devel
  • gcenx-wine-staging
  • wine-crossover

How to manually install wine on mac using Winehq releases;

Grab a wine package usually using the latest wine-devel is recommended, but most agree it’s best to use the latest wine-staging due to additional patches.
If your intention is to have a more stable environment use wine-stable

The above is the Winehq way to install wine on mac but that makes it cumbersome to use considering you must launch the Wine Stable , Wine Devel or Wine Staging app each time to get access to wine within Terminal

Читайте также:  Foison c48 драйвер для windows

The default WINEPREFIX will be

/.wine so anything you install will be placed into the hidden

/.wine folder. You can override this by using the WINEPREFIX command

The default architecture of a WINEPREFIX will be 64Bit meaning 32Bit and 64Bit applications & games are supported but that’s not always ideal for several reasons. A new WINEPREFIX can be created and also setting WINEARCH

Here is an example of using both commands to create a 32Bit only WINEPREFIX

The above command will create a new WINEPREFIX thats also 32Bit only and launch winecfg

Basic wine tools

  • wine (32Bit loader)
  • wine64 (64Bit loader)
  • msiexec (execute msi files
  • notepad
  • regedit (Wines Registry editor)
  • regsvr32 (Provides DLL registration services)
  • wineboot
  • winecfg (wine configuration utility)
  • wineconsole (windows like shell aka cmd)
  • winedbg (wine debug utility)
  • winefile (wine file manager)
  • winemine (wines version of the game mine)
  • winepath

What’s this winetricks everyone keeps saying to use?

Winetricks is an easy way to work around problems in Wine.

While winetricks can be installed directly from GitHub you will be missing packages winetricks requires, instead install again using homebrew

Now you will also have access to winetricks command within Terminal

Why doesn’t Virtual Desktop work?

By default wine on mac uses what’s known as macDriver using winetricks run the following command

This will swap from macDriver to x11 now wine will make use of XQuartz

Why doesn’t my game work on mac but Winehq says it does?

This usually happens when the game uses DirectX10 or above, the version of OpenGL included on macOS hasn’t been updated in years so it’s missing some needed extensions.

Can I use DXVK on mac?

No not currently.
MoltenVK is Vulkan 1.1 compliant, but still missing additional extensions needed by DXVK.
MoltenVK uses Metal meaning only wine64 has Vulkan support (currently wine32on64 doesn’t support MoltenVK).

Please Note;
CrossOver-20 does include DXVK support, this provides DirectX10 and DirectX11 support. CodeWeavers patched MoltenVK to fake unsupported extensions and a custom version of DXVK that’s modified specifically for macOS.

macOS Catalina and later

Currently only CrossOver-19 and later will run

Here are some free alternatives;

  • Unofficial Wineskin Use a WS11 Engine
  • PortingKit Should automatically select a working Engine
  • My brew tap

Gatekeeper will give a warning for each Windows binary that is ran as these won’t be code-signed in a way Apple expects, to avoid this you could disabled Gatekeeper using the following command

Please Note;
macOS Catalina 10.15.0 to 10.15.3, SIP needs to be disabled this will allow wine32on64 to change the state of i386_set_ldt

My current wine-crossover package can be downloaded directly WineCX19.02
Phoenicis has a build of WineCX19.0.0

Also;
wine32on64 currently does not support 16Bit executable so some things just won’t work

Apple Silicon support?

Only CrossOver-20.0.2 includes support for Apple Silicon at this time, this requires macOS Big Sur 11.1 and install Rosetta2.
I will be adding support for Apple Silicon into Wineskin once I’m able to obtain an M1 Mac mini, currently checking where would be the best place to purchase from.

Using wine in a macOS Virtual Machine

From Wine-4.15 to Wine-5.16 macDriver (the default display driver) won’t function within a Virtual Machine, however the X11 display driver works.
You can edit the wine registry manually or use winetricks

Please Note; The macDriver regression was resolved from Wine-5.17

Wine-5.9 to Wine-5.18 file limit regression;

The upstream patch was applied to my recently uploaded Wine-5.17 packages
The most commonly noticed issues was wine-gecko was always crashing.

Источник

Оцените статью
© 2024 Советы по настройке компьютера