Installing Enterprise Architect inside Wine or CrossOver

This page describes how to install and upgrade Enterprise Architect on Linux or macOS environments using either Wine or CodeWeavers CrossOver. Instructions are also provided for installing and configuring Add-Ins, and configuring version control, Enterprise Architect's Visual Execution Analyzer and Cloud Service for use in non-Windows environments.

Installing Enterprise Architect using Wine

The example commands used here relate to Debian-based Linux systems, such as Ubuntu and Linux Mint, although you can follow the same basic procedures for other Linux distributions or macOS environments.

  1. Install Wine and Winetricks by running these commands. If apt-get complains about missing dependencies, install them, then repeat the update and install commands.

    Note: The first command is only required for 64-bit systems, which is true of most modern computers.
    sudo dpkg --add-architecture i386
    sudo add-apt-repository ppa:wine/wine-builds
    sudo apt-get update
    sudo apt-get install --install-recommends winehq-devel
    sudo apt-get install winetricks

    As an alternative to these commands, you can install Wine and Winetricks via your distribution's package manager, although this might result in older versions of the software being installed. For the latest versions of Wine for Linux or macOS, please refer to the Wine HQ website.

  2. We recommend installing the Carlito font, so that text in diagrams appears as it does in a native Windows installation. This also prevents the diagram from resizing unnecessarily. Issue this command to install the Carlito font:
    sudo apt-get install fonts-crosextra-carlito

  3. Install the MSXML and MDAC components by running these commands:
    winetricks msxml3
    winetricks msxml4
    winetricks mdac28

    If prompted to do so, download the msxml.msi file and place it in the directory: ~/.cache/winetricks/msxml3.

  4. Download the latest Enterprise Architect installer:

  5. Install Enterprise Architect by running one of these commands, which relate to the registered and trial installations respectively:

    • wine msiexec /i easetupfull.msi
    • wine msiexec /i easetup.msi

Enabling Jet 4 (Unicode enabled) model repositories and ODBC access

Install support for Jet4 under Wine, by running the command:
winetricks jet40

To install an ODBC driver, first download the relevant installer, then run a command such as:
wine msiexec /i mysql-connector-odbc-3.51.25-win32.msi

Once the ODBC driver is installed, you can configure the connection from the Enterprise Architect Ribbon, Tools | ODBC Data Sources.

This table lists ODBC drivers that have been tested against Enterprise Architect running under Wine. The compatibility of each driver with Enterprise Architect is indicated in the Status column.

RDBMS Product ODBC Driver Version Status Download From
MySQL 3.51.25 Working
MySQL 5.1.12 Working
MySQL 5.2.2 Working
MySQL 5.2.4 Not Working
MySQL 5.2.5 Working
Postgresql 8.04.0200 Working
Postgresql 9.00.0310 Working
Postgresql 9.05.0400 Working

Upgrading Enterprise Architect using Wine

  1. Download the latest Enterprise Architect installer.

  2. Run this command in a terminal:
    wine uninstaller

  3. Uninstall the existing version:

    1. Select Enterprise Architect from the Applications list.

    2. Click Remove.

    3. Follow the prompts to uninstall Enterprise Architect.

  4. Install the downloaded file from step 1, using this command for the registered edition of Enterprise Architect:
    wine msiexec /i easetupfull.msi

    Or this command for the Trial edition:
    wine msiexec /i easetup.msi

Installing Enterprise Architect using CrossOver

You can install Enterprise Architect in a Linux environment using CrossOver Linux, or in a macOS environment using CrossOver Mac.

  1. Download the latest Enterprise Architect installer:

  2. Download and install CrossOver version 15.2.0 or later. CrossOver Linux and CrossOver Mac are available from CodeWeavers' website.

  3. From the CrossOver menu, select Install Windows Software.

  4. Find the Enterprise Architect entry that matches your Enterprise Architect version, or the highest version if yours is not listed.

  5. Change the installer to the location of the Enterprise Architect setup file you downloaded.

  6. Click Install.

  7. To install Enterprise Architect Add-Ins:

    1. From the CrossOver menu, select Install Windows Software.

    2. Find the entry Unsupported Application | Option Application.

    3. Click Select an Installer, then select the Add-In's installation file.

    4. Click Select a bottle in which to install, then select the bottle in which Enterprise Architect is already installed.

    5. Click Proceed.

Upgrading Enterprise Architect using CrossOver

To install a newer version of Enterprise Architect using CrossOver:

  1. Select Tools | Manage Bottles.

  2. Select the bottle you want to update.

  3. Select the Applications tab.

  4. Click Install Software...

  5. Find the Unsupported Application section and select Other Application.

  6. Click Proceed.

  7. Click Choose Installer File....

  8. Select the new Enterprise Architect installer file.

  9. Click Install.

  10. You will be prompted to uninstall the old version of Enterprise Architect before the upgrade occurs.

Installing Enterprise Architect Add-Ins using Wine

To install Enterprise Architect Add-Ins under the Wine environment:

  1. Download the Add-In of interest. Add-Ins are usually distributed as executable installers. A list of Enterprise Architect addins developed by Sparx Systems can be found at:

  2. If your Add-In depends on .NET, you need to install .NET first. Although .NET-based Add-Ins for Enterprise Architect have not been tested under Wine, you can run one of these commands to install the .NET runtime:

    • winetricks dotnet20
    • winetricks dotnet30
    • winetricks dotnet35
    • winetricks dotnet40

    NOTE: Installing a higher .NET runtime will install the previous versions as well.

  3. Run this command, replacing the name of the installer file with the one you downloaded.
    wine EAZachman.exe

  4. Follow the installer's prompts to complete installation.

Configuring the MDG Link for Eclipse Add-In using Wine

The MDG Link for Eclipse Add-In is now distributed and installed automatically with the Enterprise Architect installer (as of Enterprise Architect version 12). When running under Wine, MDG Link for Eclipse allows you to link to an instance of Eclipse running natively on the Linux host. These instructions assume that Eclipse has been set up within the native Linux environment.

  1. To run MDG Link for Eclipse in the native Linux version of Eclipse, Enterprise Architect's plugin jar files must be copied to the plugins directory of the Eclipse installation. Copy the necessary jar files from your Enterprise Architect installation under Wine to your Eclipse installation. Two sample copy commands are shown here, with the jar file paths corresponding to 64-bit and 32-bit Wine installations respectively. You can copy one of these samples and replace the 'PATH_TO_ECLIPSE_DIR' text with your Eclipse installation path.

    • cp ~/.wine/drive_c/Program\ Files/Sparx\ Systems/EA/*.jar PATH_TO_ECLIPSE_DIR/plugins
    • cp ~/.wine/drive_c/Program\ Files\ \(x86\)/Sparx\ Systems/EA/*.jar PATH_TO_ECLIPSE_DIR/plugins
  2. Start Eclipse and load the project to link to Enterprise Architect. Note: We recommend running Eclipse natively due to potential compatibility issues between Java and Wine that can manifest when running Eclipse via Wine.

  3. Start Enterprise Architect (via Wine) and open a project.

  4. Configure the MDG Link for Eclipse connection options by invoking Enterprise Architect's Eclipse Options dialog - click the Code ribbon in Enterprise Architect (version 13 or later), then click the Eclipse button, then Options.

  5. Since Windows and Linux paths are different, you need to specify how file paths are handled in the Options dialog, as illustrated.

    Replace 'Y:' with the path you use in Wine.
  6. Connect to an Eclipse project by right-clicking a package in Enterprise Architect's Project Browser, then select Extensions | Eclipse | Connect External Project.

    Select the project you opened in Eclipse using the Connections dialog.

Configuring Subversion for Enterprise Architect and Wine

To install and configure Subversion for use with Enterprise Architect in a Wine environment:

  1. Ensure that you have a working Wine environment that supports Enterprise Architect, as explained in the opening sections of this article.

  2. Ensure that you have the program 'ntlm_auth' installed as part of your Linux distribution. This is usually part of the winbind (samba) package.

  3. Install a native subversion client into the same environment as Enterprise Architect, using a command of the form:

    This table lists native Subversion clients that have been tested against Enterprise Architect running under Wine. The compatibility of each client with Enterprise Architect is indicated in the Status column.

    Subversion Client Client Version Status
    SlikSVN 1.6.9 Working
    SlikSVN 1.6.16 Working
    CollabNet Subversion Client 1.6.12 Not Working
  4. Enterprise Architect requires that the subversion credentials be cached before making a connection. The initial SVN checkout will create the cache Enterprise Architect needs.

    Perform the initial checkout using a command of this form:
    wine <PATH_TO_SVN> co <PATH_TO_REPOSITORY> <OUTPUT_PATH> --username <USERNAME> --password <PASSWORD>

    Don't checkout the repository using the native Linux/Mac client, since the SVN credentials will not be cached correctly.

  5. Configure version control in Enterprise Architect as illustrated.

    When prompted 'Are you using a Unix based Subversion client', click No.

  6. Connect a package in your Enterprise Architect project to version control as illustrated.

Configuring Enterprise Architect's Cloud Server using Wine

Enterprise Architect's Cloud Server can be installed and run on Linux using Wine. To configure the Cloud Server using Wine, you need to consider the guidelines in the Help topic Cloud Server Configuration and pay particular attention to the points regarding privileged ports on Linux and the commands for running the Cloud Server in standalone mode.

Using Enterprise Architect's Visual Execution Analyzer (VEA) with Wine

Note these points before attempting to analyze your application with Enterprise Architect running under Wine:

  • These instructions assume your application is installed successfully into the Wine environment, and all dependencies are met. For example, you have installed msxml6 if your application requires it and it is not deployed as part of your installer.

  • The VEA feature only applies to Native code (C/C++), when running under Wine.

  • These instructions assume you have built your program in Visual Studio as Debug or Release with PDB support.

  • If you are using a Debug executable file, you might have to copy the MFC/ATL Debug SXS from your Windows machine to your Wine environment. So the folder C:\windows\WinSxS would map to ~/.wine/drive_c/windows/winsxs.

  • For every EXE/DLL that you want to debug or profile using the VEA, you must have the PDB for that file.

Deploy your application and analyze it using Enterprise Architect's VEA using these steps:

  1. Copy all of your source files from your development machine to the Wine environment. The path must match exactly. For example, if your source code was compiled in C:\source\yourApp, then you must copy the source code files to ~/.wine/drive_c/source/yourApp. This means you might first have to create a drive in winecfg if you use a separate build machine in order to get the correct path.

  2. Run your application manually via the command line using a command of the form:

  3. If the application runs, proceed to the next step. Otherwise, check the console for Wine output and install any DLLs to resolve missing dependencies. Once you are certain that there are no missing dependencies and that the crash is due to something else, proceed to the next step.

    Tip: If a huge amount of output is generated by WINE, pipe the output to a file using a command of the form:
    wine PATH_TO_APPLICATION >& output.txt

  4. Import your source code. This is optional - you don't have to import your code into Enterprise Architect, but it does help when you want to set breakpoints within your code.

  5. Set up Enterprise Architect Build Scripts using these steps:

    1. Add a build script to a package. For details, see the Help topic: Analyzer Script Editor.

    2. Configure the Run command.

    3. Configure the Debug command.

    4. Set the Debugger value to Microsoft Native.

  6. Open the Debugger window or use the Execution Analysis - Debug workspace (preferred).

  7. Select the Build Script you created in the previous step.

  8. Click the Play button.


  • Check that the breakpoint is bound. If it is bound, it will stay red. If it has a question mark, it is not bound.

  • If your breakpoint didn't bind, then check carefully that the source path matches exactly.

  • Ensure that the PDB file(s) is in the same directory as your EXE file(s).

  • Ensure that EXE and PDB files match; that is, that they are from the same compilation.

Known Issues and Workarounds

When attempting to debug or profile an application, the Debugger or Profiler crashes.

Ensure that SSampler and SSProfiler75 have WinXP as their Windows version.

When attempting to debug or profile an application, no data is returned.

Ensure that SSampler and SSProfiler75 have 'dbghelp' overridden.

Ensure that the source path matches exactly to where it was originally compiled.

Unable to connect to a database after a Wine update.

Reinstall mdac28 by running the command:
winetricks --force mdac28

Enterprise Architect shortcuts don't appear to work.

Press the Ctrl, Alt and Shift keys one at a time. (Wine is reporting that one of these keys is being pressed).

Diagram elements don't draw their borders.

You can change the diagram rendering mode that Enterprise Architect uses. From the Start ribbon, choose Options | Diagram | Appearance, and set the Renderer value to Enhanced -1.

When profiling an application for a long period of time, the machine locks up.

Profile in smaller time periods. There is currently no other known workaround.

The Project Browser context menu is missing or not working using CrossOver Mac.

Toggle the Use legacy X Window System value:

  1. Use the CrossOver menu Configure | Manage Bottles.

  2. Click the Advanced tab.

  3. Toggle the option Use legacy X Window System.

  4. Reboot the Bottle when prompted.

Formatted Notes do not always display as expected under Wine

This can occur, for example, in the Info View facility. There is currently no known workaround.