The client terminal can be installed and run on computers with Mac OS using Wine. Wine is a free software that allows users of the Unix-based systems to run an application developed for the Microsoft Windows systems. Among all the Wine versions there is one for Mac OS.
Note that Wine is not a fully stable application. Thus, some functions in the applications you start under it may work improperly or not work at all. |
- 'The Mono version installed on Mac may not be compatible with this version of Visual Studio. Would you like us to install Mono '6.6.0.155' for you? This will overwrite any existing Mono installation on your Mac.' The stack on both workstations is completely up to date: OSX: Catalina 10.15.2 Visual Studio Mac: 8.3.11 (build 1) XCode: 11.3 (11C29).
- Navigate to the Download or Application you just installed to your Mac Instead of Double-Clicking on the Icon to open, Right Click on it and choose 'Open' A Pop-Up Window will appear telling you that the Software is from an Unidentified Developer, but it will give you the option to Open it anyway.
- The client terminal can be installed and run on computers with Mac OS using Wine. Wine is a free software that allows users of the Unix-based systems to run an application developed for the Microsoft Windows systems. Among all the Wine versions there is one for Mac OS. Note that Wine is not a fully stable application.
For the installation on Mac OS we recommend to use the free application PlayOnMac. PlayOnMac is a Wine-based software for easy installation of Windows applications on Mac OS.
You will still have to manually run the msi files to install wine-mono and wine-gecko to existing wineprefixes, but they will automatically be installed to any new wineprefixes. Installing wine-mono doesn't seem to install mono in wine. From prodding around a bit it looks like the package is downloading the installer, but mono itself is never installed in wine. The package puts the installer at: /usr/share/wine/mono/wine-mono-4.7.5.msi.
PlayOnMac Installation
To install PlayOnMac, open the product's official web site, move to Downloads section and click the link for downloading the latest version.
After downloading the DMG package, launch it from Downloads section of your system:
PlayOnMac first launch window will appear. After clicking 'Next', the installer will start checking and installing the various components necessary for work.
The first necessary component is XQuartz. This is a software for using X Window System on Mac OS. X Window System provides standard tools and protocols for building the graphical user interface in Unix-like OS.
If you have already installed XQuartz or want to install it later, select 'Don't install XQuartz for the moment' or 'I've downloaded file by myself', respectively.
XQuartz installation is performed in several stages. First of all, you should read the important information (Read Me) and accept the license conditions.
Before the installation, Mac OS security system will ask you to enter your account's password:
Wait for the installation to complete. For changes to take effect, you should restart your PC.
After restarting the system, launch PlayOnMac again from the setup file in Downloads folder. The first launch window will appear again. This time, the installer will offer to install MS Windows fonts necessary for correct operation.
Accept the license agreement conditions and wait till the installation is complete. After that, PlayOnMac is ready for use. Its main window will appear:
Updating Wine
Wine v. 1.4 is installed together with PlayOnMac. Wine 1.4.1 is the latest stable version at the moment. Wine 1.5.21 beta release containing many improvements is also available for download. However, it may be less stable. It is recommended to install the latest version of Wine.
To upgrade Wine to the latest version, open PlayOnMac upper menu and select Manage Wine Versions:
The window with Wine versions available for installation will open. Select the latest version (1.5.21 at the moment).
Move the latest Wine version to the right side of the window. The installation will start.
After the installation is complete, the new version of Wine will appear in the left part of PlayOnMac Wine versions manager window. You can then close the window and install the trading terminal.
Terminal Installation
To install the terminal, download the installer 'mt4setup.exe'. After the download is complete, launch the setup file. PlayOnMac will be used automatically to open it.
The standard terminal installation process with all its stages will start:
When the installation is complete, PlayOnMac will offer you to create the shortcuts for the terminal components - the client terminal itself and MetaEditor:
After creating the necessary shortcuts, you can start using the client terminal. Double click on it in PlayOnMac window to launch the terminal.
Known Issues
As was already mentioned above, Wine is not a completely stable software. Thus, some functions of the terminal may work improperly. Currently the following issues are discovered:
- Market is unavailable
Except for the above problem, you can enjoy all the features of the client terminal on Mac OS.
Terminal Data Directory
PlayOnMac creates a separate virtual logical drive with necessary environment for each installed program. The default path of the installed terminal's data folder is as follows:
LibraryPlayOnMacWinePrefixClient_Terminal_DriveCProgramFilesClient Terminal |
Wine implements its own version of Internet Explorer. The implementation is based on a custom version of Mozilla's Gecko Layout Engine.
- 3Building Wine Gecko
- 3.1Mingw-w64
- 3.2Troubleshooting
Installing
When your application tries to display a site, Wine loads and uses its custom implementation of Gecko. Wine tries to find Gecko installation in following order:
- If Wine Gecko is already installed in the prefix, that installation will be used.
- Wine 5.0-rc1 and newer will try to load Gecko from UNIX-style installation without installing it into the prefix. It will look for wine-gecko-$(VERSION)-$(ARC) subdirectory of standard local lookup (see bellow).
- Wine will try to find Wine Gecko MSI installer on local machine (see bellow). If it can find it, it will install it into the prefix and use it.
- If the file can't be found on your computer, Wine will download it for you. The downloaded .msi is saved to ~/.cache/wine. If the download fails, you can download the appropriate version (see table below) yourself from http://dl.winehq.org/wine/wine-gecko/.
Whenever Wine tries to find local installation, it will look in following directories:
- In most cases, the file(s) should be placed in /usr/share/wine/gecko.
- If you installed Wine in some $prefix rather than /usr, $prefix/share/wine/gecko/ before /usr/share/wine/gecko. (e.g. if you installed it from source, then place the files in /usr/local/share/wine/gecko).
- If you're running Wine from build tree, Wine will try to find files in $build_dir/../gecko directory.
- Local cache, usually ~/.cache/wine.
For 64 bit (WoW64) Wine, both the x86 and x86_64 packages are required.
Wine will currently not be able to use such Gecko installation if it can't map it to DOS drive (for example if z: drive is removed).
| Wine | Gecko (32 bit) | Gecko (64 bit) |
|---|---|---|
| wine-0.9.47 - wine-1.1.11 | wine_gecko-0.1.0.cab | |
| wine-1.1.12 - wine-1.1.14 | wine_gecko-0.9.0.cab | |
| wine-1.1.15 - wine-1.1.26 | wine_gecko-0.9.1.cab | |
| wine-1.1.27 - wine-1.3.1 | wine_gecko-1.0.0-x86.cab | |
| wine-1.3.2 - wine-1.3.15 | wine_gecko-1.1.0-x86.cab | wine_gecko-1.1.0-x86_64.cab |
| wine-1.3.16 - wine-1.3.26 | wine_gecko-1.2.0-x86.msi | wine_gecko-1.2.0-x86_64.msi |
| wine-1.3.27 - wine-1.3.32 | wine_gecko-1.3-x86.msi | wine_gecko-1.3-x86_64.msi |
| wine-1.3.33 - wine-1.4 | wine_gecko-1.4-x86.msi | wine_gecko-1.4-x86_64.msi |
| wine-1.5.0 - wine-1.5.6 | wine_gecko-1.5-x86.msi | wine_gecko-1.5-x86_64.msi |
| wine-1.5.7 - wine-1.5.9 | wine_gecko-1.6-x86.msi | wine_gecko-1.6-x86_64.msi |
| wine-1.5.10 - wine-1.5.14 | wine_gecko-1.7-x86.msi | wine_gecko-1.7-x86_64.msi |
| wine-1.5.15 - wine-1.5.21 | wine_gecko-1.8-x86.msi | wine_gecko-1.8-x86_64.msi |
| wine-1.5.22 - wine-1.5.30 | wine_gecko-1.9-x86.msi | wine_gecko-1.9-x86_64.msi |
| wine-1.5.31 - wine-1.7.2 | wine_gecko-2.21-x86.msi | wine_gecko-2.21-x86_64.msi |
| wine-1.7.3 - wine-1.7.30 | wine_gecko-2.24-x86.msi | wine_gecko-2.24-x86_64.msi |
| wine-1.7.31 - wine-1.7.37 | wine_gecko-2.34-x86.msi | wine_gecko-2.34-x86_64.msi |
| wine-1.7.38 - wine-1.7.49 | wine_gecko-2.36-x86.msi | wine_gecko-2.36-x86_64.msi |
| wine-1.7.50 - wine-1.9.2 | wine_gecko-2.40-x86.msi | wine_gecko-2.40-x86_64.msi |
| wine-1.9.3 - wine-1.9.12 | wine_gecko-2.44-x86.msi | wine_gecko-2.44-x86_64.msi |
| wine-1.9.13 - wine-3.21 | wine_gecko-2.47-x86.msi | wine_gecko-2.47-x86_64.msi |
| wine-5.0-rc1 - current |
Debug info
If Gecko is crashing on you, you can download a debug build from http://dl.winehq.org/wine/wine-gecko/ to get more verbose logs. Download the -unstripped.tar.bz2 file for the version you are using (on a 64 bit system, download both the x86 and x86_64 tarballs), unpack the files, and replace the files in $WINEPREFIX/drive_c/windows/system32/gecko/version and (on 64 bit) $WINEPREFIX/drive_c/windows/sysWoW64/gecko/version with the extracted files.
Building Wine Gecko
The following describe how the Wine Gecko package is built.
NOTE: If you're unsure if you want to build it yourself, the answer is no. There is no reason to build it yourself unless you're going to work on Mozilla code. If you need Gecko to run an app in Wine, follow the instructions above. Wine Gecko source is hosted in Git on Sourceforge.
Wine Gecko is maintained by Jacek Caban. If you need help, feel free to contact him.
Mingw-w64
It is encouraged to use mingw-w64 for cross-compiling. A fairly recent version of mingw-w64 should be enough.
Building
Wine Mono Is Not Installed Machines
The exact instruction about building the package are hosted in wine/README in Wine Gecko source directory.
Binary Packages
Wine Mono Is Not Installed Mac Os
Some Distro are maintaining mingw-w64 in their repo, like Fedora. You can install the dependencies with commands like
Troubleshooting
'pthread_t' does not name a type
Try to remove media/libstagefright/ports/win32/include/pthread.h. This should be fixed in version 2.47.1.
mingw-w64 too old
For example:
- 'ILocation' was not declared.
The mingw-w64 package on your distro may be too old to include this patch.(for example, it will take some time to backport these patch to stable branches like v4.x)If you faced this trouble, please consider compile mingw-w64 by yourself(as README said)