Difference between revisions of "CrossOver"

From ArchWiki
Jump to: navigation, search
(Add a link.)
m (add ja link)
 
(17 intermediate revisions by 5 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 aren't so 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 want install trial verison of crossover.
 +
[[Install]] {{AUR|crossover}} package.
  
*Finally {{ic|$ ./install-crossover-*.bin}} for single user.
+
== Using CrossOver ==
  
==Using CrossOver==
+
If installed by a user in ''single user mode'', Crossover binaries will be located in {{ic|~/cxoffice}}.``
Assuming it was installed as ''user'', Crossover binaries should be located in {{ic|~/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 {{ic|/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.
 
Some desktop environments like [[KDE]] may have automatically placed menu entries as part of the installation process.
Line 26: Line 26:
  
 
{{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: {{ic|# /opt/cxoffice/bin/cxregister}}. Registration should then complete and be valid for all users on the system.}}
 +
 +
== Troubleshooting ==
 +
 +
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.

Latest revision as of 07:59, 5 July 2015

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 aren't so tech-savvy.

Installation

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

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.

Troubleshooting

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.