[cw-discuss] Wine and Cxoffice

[Jeremy White]

Hi Martyn,

Check the archives on this thread; I supplied some advice on how to do this.

> * Some Wine binaries are modified to show CX how the product is licensed
>    (if CX binaries become Wine binaries does it provide accidental
> "circumvention" or does it prevent use of the proprietary components?)

No, and no.  We think of ourselves as a Free Software company; enabling
you to use and extend Wine is an important part of what we do.  So, it's
not licensing that will cause you heartache, and we will not consider
it any form of circumvention.

However, with that said, you are likely to run into some trouble.  The Wine
in CrossOver is different from stock Wine in little ways that are likely
to cause small hiccups and bumps.  For example, the 'wineprefixcreate'
script is different between the two.  (In this case, Wine's is actually
superior, but CrossOver is adapted to its own, which predated the
existence of the Wine one).

But, again, I provided advice on how to do this in another thread.

Candidly, your best bet is to set up Wine to run against a CrossOver bottle
using the WINEPREFIX environment variable; that's the path most likely to
give you some joy.

> * Development environments will differ
>    (from what I can tell Debian is used)

No, that shouldn't be a problem, although getting Wine to build correctly
isn't completely trivial.  It's mostly a matter of making sure ./configure
doesn't grumble at all.

> * No support, CodeWeavers can't support it :-(

That one, I'm afraid, is true :-/.

Cheers,

Jeremy