CrossOver - ArchWiki

# CrossOver

Related articles

- Wine

CrossOver is the paid, commercialized version of Wine which provides more comprehensive end-user support. It includes scripts, patches, a GUI, and third-party software which may never be accepted in the Wine Project. This combination makes running Windows programs considerably easier for those aren't so tech-savvy.

This article or section needs expansion.

Reason: Multi-user installs, other desktop environments, older versions (if applicable). (Discuss)

## Installing CrossOver Linux

The factual accuracy of this article or section is disputed.

Reason: There is crossover in the AUR. (Discuss)

Tested with trial `install-crossover-11.2.1.bin`

- Ensure `python-dbus-common`, `pygtk` and `python2-dbus` are installed.

- Run `# ln -sf /usr/bin/python2 /usr/bin/python`

- Finally `$ ./install-crossover-*.bin` for single user.

## Installing CrossOver Linux on Arch x86_64

The factual accuracy of this article or section is disputed.

Reason: crossover lists all dependencies (Discuss)

CrossOver is currently not available in 64-bit version. One way to still be able to install and run the 32 bit version of CrossOver on an Arch 64 bit system is to install the missing libraries via the lib32-* packages in the multilib repository. If you wish to do so, simply add the repository to your /etc/pacman.conf file:

    [multilib]
    Include = /etc/pacman.d/mirrorlist

To get a list of suggested and recommended libraries that might be missing, run the cxoffice utility:

    $ /opt/cxoffice/bin/cxdiag [--debug]

If you use the optional --debug switch, you will get far greater detail. A list will be generated:

    [MissingLibAsound]
    "Level"="Recommend"
    "Title"="Missing 32bit libasound.so.2 library"
    "Description"="This is the preferred way to provide audio support to Windows applications."
    [MissingLibCapi20]
    "Level"="Suggest"
    "Title"="Missing 32bit libcapi20.so.3 library"
    "Description"="Provides support for some ISDN cards. Very few applications need this."
    [MissingLibEsd]
    "Level"="Suggest"
    "Title"="Missing 32bit libesd.so.0 library"
    "Description"="This is only needed if you want the Windows applications to send sound to an ESounD sound server.
     ......
     ......
     ......

The 32 bit library requirements will depend on the Windows applications you wish to run in CrossOver. Most of the libraries appearing in the list generated by cxdiag are not absolutely necessary to run most Windows applications. Go through the list and install the libraries you require. You might want to use pkgfile in order to find out which lib32-* package contains a particular missing library:

    $ pkgfile <filename>

Warning: The file will likely belong to more than one package. Be sure to install the multilib/lib32-* package.

There is also a way to generate a logfile to assist you in tracking down errors that may be preventing you from running your desired Windows application(s). From the CrossOver menu, choose "Run a Windows Command". You will see "Debug Options". Click the "+" sign to expand the options. Click the "Create log file" checkbox. Enter the command you would use to run your Windows application in the "Command" text box. (You can use the Browse button if you aren't sure what to enter, to navigate to your Windows application). CrossOver will prompt you for a location to save the log file. Choose your location and press enter. Crossover will generate the logfile in the location you chose.

Although the libSM.so.6 library was not shown in the cxdiag list of missing libraries - it DID appear in the logfile. The library belongs to the lib32-libsm package. If you're having problems getting your application to run, you might want to try installing lib32-libsm.

## Using CrossOver

If installed by a user in single user mode, Crossover binaries will be located in `~/cxoffice`. Windows applications and configuration files will be placed in ~/.cxoffice.

If installed with root privileges in multi-user shared mode, Crossover binaries will be located in `/opt/cxoffice`. Each user's bottles will be placed in ~/.cxoffice.

Some desktop environments like KDE may have automatically placed menu entries as part of the installation process.

Installed programs should be located under a new menu entry called Window Applications.

Tip: If you get a registration failure, try: `# /opt/cxoffice/bin/cxregister`. Registration should then complete and be valid for all users on the system.
Categories:

- Wine
- Gaming