Difference between revisions of "Talk:CrossOver"

From ArchWiki
Jump to: navigation, search
(Merge to Wine)
Line 2: Line 2:
 
Codeweavers is the corporate backing of Wine, and Wine '''is''' the base code of all Crossover products (plus workarounds and fixes that aren't Wine approved).  Most Crossover employees are Wine developers. Does there ''really'' need to be a separate wiki article? [[User:T1nk3r3r|T1nk3r3r]] ([[User talk:T1nk3r3r|talk]]) 09:47, 31 July 2012 (UTC)
 
Codeweavers is the corporate backing of Wine, and Wine '''is''' the base code of all Crossover products (plus workarounds and fixes that aren't Wine approved).  Most Crossover employees are Wine developers. Does there ''really'' need to be a separate wiki article? [[User:T1nk3r3r|T1nk3r3r]] ([[User talk:T1nk3r3r|talk]]) 09:47, 31 July 2012 (UTC)
 
: This page is short enough to be merged. You can merge it and redirect this page to new section in [[Wine]]. -- [[User:Fengchao|Fengchao]] ([[User talk:Fengchao|talk]]) 11:24, 31 July 2012 (UTC)
 
: This page is short enough to be merged. You can merge it and redirect this page to new section in [[Wine]]. -- [[User:Fengchao|Fengchao]] ([[User talk:Fengchao|talk]]) 11:24, 31 July 2012 (UTC)
 +
:: Ultimately decided against it.  Despite Wine and Codeweavers being intertwined so tightly, to merge articles may very well make wiki:Wine ''too'' large. Besides, it appears that this can be expanded to include installation hints.  [[User:T1nk3r3r|T1nk3r3r]] ([[User talk:T1nk3r3r|talk]]) 05:42, 24 September 2012 (UTC)
  
 
== What I did ==
 
== What I did ==

Revision as of 05:42, 24 September 2012

Merge to Wine

Codeweavers is the corporate backing of Wine, and Wine is the base code of all Crossover products (plus workarounds and fixes that aren't Wine approved). Most Crossover employees are Wine developers. Does there really need to be a separate wiki article? T1nk3r3r (talk) 09:47, 31 July 2012 (UTC)

This page is short enough to be merged. You can merge it and redirect this page to new section in Wine. -- Fengchao (talk) 11:24, 31 July 2012 (UTC)
Ultimately decided against it. Despite Wine and Codeweavers being intertwined so tightly, to merge articles may very well make wiki:Wine too large. Besides, it appears that this can be expanded to include installation hints. T1nk3r3r (talk) 05:42, 24 September 2012 (UTC)

What I did

   $ wget http://www.codeweavers.com/account/downloads/install-crossover-standard-10.0.0.bin 
   $ sudo sh install-crossover-standard-10.0.0.bin 

accepted license agreement and the standard path (/opt/cxoffice), clicked install, got a python error that went away again, then clicked OK. Then I went into /opt/cxoffice/bin and did

   sed -i".tmp" 's/env python/env python2/' /opt/cxoffice/bin/*

and started /opt/cxoffice/cxsetup

Arch 64 Section

I found a link that is very helpful to those of us running the 64 bit version. https://bbs.archlinux.org/viewtopic.php?id=107765

Also, I'm not sure on the complete meaning of this part of the article: As the above isn't working now because of python3 and perhaps some more issues, it's likely better to install via AUR. One can you a helper such as bauer: bauerbill --aur -S crossover-games replace "/usr/bin/env python" with "/usr/bin/env python2" in the following files in directory cd /opt/cxgames/bin/: cxassocedit cxinstaller cxmenuedit cxmessage cxregister cxreset cxrun cxsetup cxupdatecheck cxwait

All should work now.

I get the main idea, however would somebody who knows more about this be able to add some more clarity?

Making PKGBUILD work without deb2targz

I tried to install Crossover Office Pro, but the PKGBUILD includes deb2targz which appears to be out of date now. I modified the PKGBUILD 10.2.0-1:

comment out makedepends=('deb2targz') to #makedepends=('deb2targz')

from:

build() {
cd "${srcdir}"
deb2targz crossover-standard-demo_${pkgver}-1_i386.deb
tar xf crossover-standard-demo_${pkgver}-1_i386.tar.gz -C "${pkgdir}"

to:
package() {
cd "${srcdir}"

ar tv crossover-pro-demo_${pkgver}-1_i386.deb

bsdtar -C "$pkgdir" -xvf data.tar.gz

and it works a treat.

Hope this helps someone else.

Regards,

Algenon.

(Please next time sign your edits in talk pages with ~~~~ :) )
Issues with AUR packages should be reported to their maintainers using the comments in the package pages, in this case I guess here.
-- Kynikos 16:56, 15 December 2011 (EST)