How to Run? about macos-crossover-wine-cloud-builder

[Gcenx]

You seem to be misunderstanding something, this project compiles the FOSS portion of CrossOver that CodeWeavers provide.

CodeWeavers don’t provide the sources for there GUI and some other components that are closed source, the wine portion is provided and that’s what is project compiles.

[firefinchdev]

You seem to be misunderstanding something, this project compiles the FOSS portion of CrossOver that CodeWeavers provide.

CodeWeavers don’t provide the sources for there GUI and some other components that are closed source, the wine portion is provided and that’s what is project compiles.

My bad, I interpreted it wrongly...
Just to confirm, Crossover maintains a fork of wine, and due to licensing, they have to provide source for their own fork of wine.
Am I right?

[Gcenx]

Also, Crossover has the concept of "Bottles". If we are using crossover wine, do we need that "bottle"?

Replace "Bottle" with "Prefix" and you'd be more inline with upstream wine.

If yes, any way to use those bottles from command line?

CrossOver stores it's "bottle" at ~/Library/Application\ Support/CrossOver/Bottles to use one of those say "Steam" for example set;

export WINEPREFIX="/Users/$whoami/Library/Application Support/CrossOver/Bottles/Steam"

Now call wine32on64 or wine64 as usual.

[Gcenx]

@firefinchdev I'm not entirely sure what’s the best course of action.

I guess explaining “Bottle” = “Prefix” and the location where CrossOver saves it’s “Bottles” might be helpful but otherwise it’s all just wine knowledge.

@GabLeRoux did a little tweak to your comment as you can just call wine64 explorer

[firefinchdev]

Oh okay..
If its common knowledge, then we can close it...

[dasmy]

Yep, I just renamed from macos-crossover-cloud-build to macos-crossover-wine-cloud-builder 👍

Gcenx's right, the project allows you to download an already built version of wine for macos using github-actions so you can simply download the binaries, add them to your $PATH (or run it directly) and use them to launch windows apps on macOS :)

You can find the binaries built on github-actions in the Artifacts section of the succeeding jobs

Here's a random example where I install and run soldat game 😆

1. Use latest successful build (I used this one)
2. Download and unzip wine-cx21.0.0.zip:

1. Use wine to run the downloaded .exe:

cd ~/downloads/wine-cx21.0.0/
./usr/local/bin/wine64 ~/Downloads/soldat1711.exe

1. You can then use Wine's explorer to launch installed things:

./usr/local/bin/wine64 explorer

🦾

@GabLeRoux maybe, it makes sense to add something similar to this and also answers to the questions of @firefinchdev to Readme.md ? - These hints might be very helpful for others as well...

[Gcenx]

@dasmy my view is to only provide some basic information like “Bottle” = “Wineprefix” etc.

As @GabLeRoux seems to be in favor of providing “releases” so that would avoid some additional confusion.

After these two it’s a matter of how much duplication is desirable?, maybe adding some links to Winehq macOS wiki etc

[Gcenx]

@GabLeRoux might want to rename the project to avoid any more confusion.

Maybe something like macos-crossover-wine-cloud-builder

[GabLeRoux]

Yep, I just renamed from macos-crossover-cloud-build to macos-crossover-wine-cloud-builder 👍

Gcenx's right, the project allows you to download an already built version of wine for macos using github-actions so you can simply download the binaries, add them to your $PATH (or run it directly) and use them to launch windows apps on macOS :)

You can find the binaries built on github-actions in the Artifacts section of the succeeding jobs

Here's a random example where I install and run soldat game 😆

1. Use latest successful build (I used this one)

2. Download and unzip wine-cx21.0.0.zip:

3. Use wine to run the downloaded .exe:

cd ~/downloads/wine-cx21.0.0/
./usr/local/bin/wine64 ~/Downloads/soldat1711.exe

4. You can then use Wine's explorer to launch installed things:

./usr/local/bin/wine64 explorer

🦾

[firefinchdev]

Also, Crossover has the concept of "Bottles". If we are using crossover wine, do we need that "bottle"?
If yes, any way to use those bottles from command line?
Thanks.

[firefinchdev]

@Gcenx
This solves all of my queries.
Thanks a lot :)

Should we keep this open? I think the above discussion is useful for users...

[Gcenx]

Making another comment instead of editing the above so everyone see it.

If the Winehq macOS wiki is lacking or something would make sense written another way just message me with the desired changes and I can update the information.

Currently working on gstreamer1 plugins to hopefully drop winequicktime decoder since that’s useless at this point, the plan is to eventually rework the Winehq macOS wiki sections so any help on that would be appreciated.