Difference between revisions of "CrossOver"

From ArchWiki
Jump to: navigation, search
(Add a link.)
m (Troubleshooting: correct package name it meant to be)
 
(24 intermediate revisions by 8 users not shown)
Line 1: Line 1:
 
[[Category:Wine]]
 
[[Category:Wine]]
 
[[Category:Gaming]]
 
[[Category:Gaming]]
{{Article summary start}}
+
[[ja:CrossOver]]
{{Article summary text|Configuring and installing CrossOver on Archlinux.}}
+
{{Related articles start}}
{{Article summary heading|Related}}
+
{{Related|Wine}}
{{Article summary wiki|Wine}}
+
{{Related articles end}}
{{Article summary end}}
 
[http://www.codeweavers.com/ CrossOver] is the paid, commercialized version of Wine which provides more comprehensive end-user support. It includes scripts, patches, a [[wikipedia:Graphical user interface|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.
 
{{Expansion| Multi-user installs, other desktop environments, older versions (if applicable).}}
 
  
==Installing Crossover Linux==
+
[http://www.codeweavers.com/ CrossOver] is the paid, commercialized version of Wine which provides more comprehensive end-user support. It includes scripts, patches, a [[wikipedia:Graphical user interface|GUI]], and third-party software which may never be accepted in the Wine Project. This combination makes running Windows programs considerably easier for those less tech-savvy.
Tested with trial {{ic|install-crossover-11.2.1.bin}}
 
  
*Ensure {{ic|python-dbus-common}}, {{ic|pygtk}} and {{ic|python2-dbus}} are installed.
+
== Installation ==
  
*Run {{ic|# ln -sf /usr/bin/python2 /usr/bin/python}}
+
In this article it is suggested that you install the trial version of crossover.
 +
[[Install]] {{AUR|crossover}} package.
  
*Finally {{ic|$ ./install-crossover-*.bin}} for single user.
+
== Usage ==
  
==Using CrossOver==
+
If installed by a user in ''single user mode'', Crossover binaries will be located in {{ic|~/cxoffice}}. Windows applications and configuration files will be placed in {{ic|~/.cxoffice}}.
Assuming it was installed as ''user'', Crossover binaries should be located in {{ic|~/cxoffice}}.
+
 
 +
If installed with root privileges in ''multi-user shared mode'', Crossover binaries will be located in {{ic|/opt/cxoffice}}. Each user's bottles will be placed in {{ic|~/.cxoffice}}.
  
 
Some desktop environments like [[KDE]] may have automatically placed menu entries as part of the installation process.
 
Some desktop environments like [[KDE]] may have automatically placed menu entries as part of the installation process.
Line 25: Line 23:
 
Installed programs should be located under a new menu entry called ''Window Applications''.
 
Installed programs should be located under a new menu entry called ''Window Applications''.
  
{{Tip| If you get a registration failure, try: {{ic|# /opt/cxoffice/bin/cxregister}}. Registration should then complete and be valid for all users on the system.}}
+
{{Tip| If you get a registration failure, try to execute {{ic|/opt/cxoffice/bin/cxregister}} as root. Registration should then complete and be valid for all users on the system.}}
 +
 
 +
== Troubleshooting ==
 +
 
 +
There is also a way to generate a log file to assist you in tracking down errors that may be preventing you from running your desired Windows application(s). Follow the menu path ''CrossOver > Run a Windows Command > Debug Options'' and 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 are not 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 to have Crossover generate the log file in it.
 +
 
 +
Although the {{ic|libSM.so}} library was not shown in the cxdiag list of missing libraries - it did appear in the log file. The library belongs to the {{Pkg|libsm}} package. If you are having problems getting your application to run, check its installation status.

Latest revision as of 17:48, 16 June 2016

Related articles

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 less tech-savvy.

Installation

In this article it is suggested that you install the trial version of crossover. Install crossoverAUR package.

Usage

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 to execute /opt/cxoffice/bin/cxregister as root. Registration should then complete and be valid for all users on the system.

Troubleshooting

There is also a way to generate a log file to assist you in tracking down errors that may be preventing you from running your desired Windows application(s). Follow the menu path CrossOver > Run a Windows Command > Debug Options and 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 are not 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 to have Crossover generate the log file in it.

Although the libSM.so library was not shown in the cxdiag list of missing libraries - it did appear in the log file. The library belongs to the libsm package. If you are having problems getting your application to run, check its installation status.