F5F Stay Refreshed Software Operating Systems Attempting to streamline Wine Staging processes

Attempting to streamline Wine Staging processes

Attempting to streamline Wine Staging processes

X
xanderzone317
Posting Freak
Find
957
03-13-2016, 05:28 PM
#1
You're using Wine on macOS Sierra, which is a bit unusual since Wine typically runs on Linux distributions. To simplify your workflow, you could explore installing a native GUI like WineGUI or a similar application that makes launching programs easier. Alternatively, you might consider using a virtual machine or a dedicated app that supports direct execution of Windows executables without opening a terminal each time.
Reply
Reply
X
xanderzone317
03-13-2016, 05:28 PM #1

You're using Wine on macOS Sierra, which is a bit unusual since Wine typically runs on Linux distributions. To simplify your workflow, you could explore installing a native GUI like WineGUI or a similar application that makes launching programs easier. Alternatively, you might consider using a virtual machine or a dedicated app that supports direct execution of Windows executables without opening a terminal each time.

Reply
Reply
M
markopolo1996
Member
Find
58
03-16-2016, 12:35 PM
#2
I believed you were attempting to produce real wine.
Reply
Reply
M
markopolo1996
03-16-2016, 12:35 PM #2

I believed you were attempting to produce real wine.

Reply
Reply
W
Waverabbit
Senior Member
Find
643
03-16-2016, 06:18 PM
#3
You seem unfamiliar with Linux, do you?
Reply
Reply
W
Waverabbit
03-16-2016, 06:18 PM #3

You seem unfamiliar with Linux, do you?

Reply
Reply
I
indy125
Junior Member
Find
3
03-17-2016, 10:54 AM
#4
You can definitely execute the wine command directly from the executable as an argument, which is the standard method on Linux.
Reply
Reply
I
indy125
03-17-2016, 10:54 AM #4

You can definitely execute the wine command directly from the executable as an argument, which is the standard method on Linux.

Reply
Reply
Y
yalex27
Senior Member
Find
461
03-17-2016, 11:36 AM
#5
The title sparked an instant connection to real wine.
Reply
Reply
Y
yalex27
03-17-2016, 11:36 AM #5

The title sparked an instant connection to real wine.

Reply
Reply
O
Ocanom
Member
Find
53
03-22-2016, 02:25 AM
#6
It's the reverse, you know? When they talk about wine, I instantly think of software.
Reply
Reply
O
Ocanom
03-22-2016, 02:25 AM #6

It's the reverse, you know? When they talk about wine, I instantly think of software.

Reply
Reply
S
sniperboy650
Senior Member
Find
735
03-22-2016, 06:47 AM
#7
Sure! An argument is the input you give to a command or script when you run it. It tells the program what to do. For example, when you type `ls -l`, that’s an argument telling the program to list files in long format.
Reply
Reply
S
sniperboy650
03-22-2016, 06:47 AM #7

Sure! An argument is the input you give to a command or script when you run it. It tells the program what to do. For example, when you type `ls -l`, that’s an argument telling the program to list files in long format.

Reply
Reply
T
Toodaloo_246
Senior Member
Find
439
03-27-2016, 04:29 AM
#8
On OS X, software setup differs from typical Linux systems. Fitst: Where did you get Wine? From macports or another source? Did you run Dn'D to programs inside OS X, or used a setup guide ("OS X installation program")? Wine might be set up so the executable isn't directly reachable by the shell (like in Programs or the OS X installer), or it could be accessible through macports or similar. If it's the latter, starting apps with "wine xxxx.exe" likely won't work as you do on Linux. Also, creating shortcuts is more complicated in OS X than in Linux distributions (or at least it wasn't before). I'm uncertain if any Wine installation on OS X enables true Windows and OS X desktop integration—such as automatically linking to installed Windows apps on your OS X desktop—as it does on Linux, where Wine tries this and sometimes succeeds. The desktop environment on OS X is designed not for modification; it treats each app as a standalone package, which clashes with tools like Wine that rely on libraries for running Windows programs on another OS.
Reply
Reply
T
Toodaloo_246
03-27-2016, 04:29 AM #8

On OS X, software setup differs from typical Linux systems. Fitst: Where did you get Wine? From macports or another source? Did you run Dn'D to programs inside OS X, or used a setup guide ("OS X installation program")? Wine might be set up so the executable isn't directly reachable by the shell (like in Programs or the OS X installer), or it could be accessible through macports or similar. If it's the latter, starting apps with "wine xxxx.exe" likely won't work as you do on Linux. Also, creating shortcuts is more complicated in OS X than in Linux distributions (or at least it wasn't before). I'm uncertain if any Wine installation on OS X enables true Windows and OS X desktop integration—such as automatically linking to installed Windows apps on your OS X desktop—as it does on Linux, where Wine tries this and sometimes succeeds. The desktop environment on OS X is designed not for modification; it treats each app as a standalone package, which clashes with tools like Wine that rely on libraries for running Windows programs on another OS.

Reply
Reply
L
llegal
Junior Member
Find
42
03-28-2016, 09:10 PM
#9
An argument refers to a value you enter after a command in a command line. Once I clarified Red Manikyath's response, it seems he likely intended to link it into the desktop. You can set this up via the OS X GUI if Wine appears in the programs list. A detailed walkthrough would be helpful, but I'm not ready to launch OS X just now. Check the context menu in Finder, examine properties of any .exe files, and locate the association menu there (that's where it should be). Link .exe with "wine" and the Finder should execute them using Wine afterward.
Reply
Reply
L
llegal
03-28-2016, 09:10 PM #9

An argument refers to a value you enter after a command in a command line. Once I clarified Red Manikyath's response, it seems he likely intended to link it into the desktop. You can set this up via the OS X GUI if Wine appears in the programs list. A detailed walkthrough would be helpful, but I'm not ready to launch OS X just now. Check the context menu in Finder, examine properties of any .exe files, and locate the association menu there (that's where it should be). Link .exe with "wine" and the Finder should execute them using Wine afterward.

Reply
Reply