Hello, I am a regular user of Wine in 32-bit Ubuntu Studio v14.04.3
My current version of Wine is 1.7.55 and I'd like to upgrade to 1.8
I tried following the new format of instructions here: http://wiki.winehq.org/Ubuntu
But after the install worked, I checked the Ubuntu Wine menu and nothing was there except a link to WineTricks.
I tried running wineconfig from a terminal and it wasn't found.
So where is winehq-devel installed and what is it's name and syntax?
Something has changed from the last version in terms of instructions too.
The instructions are a bit vague and seem to imply support only for 64-bit Ubuntu.
I just want to run Wine 1.8 without compiling. I don't care if it's development still. I haven't experienced any regressions yet.
Anything seems better than dealing with 1.6
Can anybody help me? Thanks and happy holidays.
How do I launch winehq-devel ? Missing wine 1.8 for Ubuntu
Re: How do I launch winehq-devel ? Missing wine 1.8 for Ubu
Wine does not make menu entries for itself. The menu items you saw previously for winecfg, etc., were added by your distro to its packages. When you install a program, winemenubuilder will create menu entries for that (unless you've disabled it).Nystagmus wrote: But after the install worked, I checked the Ubuntu Wine menu and nothing was there except a link to WineTricks.
I tried running wineconfig from a terminal and it wasn't found.
The command is and always has been winecfg.
The WineHQ packages install Wine to /opt/wine-devel. The file names and command syntax are the same as they have always been. http://wiki.winehq.org/FAQ#run_from_terminalSo where is winehq-devel installed and what is it's name and syntax?
The instructions are a bit vague and seem to imply support only for 64-bit Ubuntu.
The exact steps needed to install are given. There is an extra step needed for 64 bit systems, but nowhere does it imply that only 64 bit is supported. If you have specific questions about any of the steps, ask.
Re: How do I launch winehq-devel ? Missing wine 1.8 for Ubu
OK thanks. I had figured this out on my own after reading more forum entries here.
The reason why it seemed like 64-bit systems were the main info is because the first step listed was for 64-bit systems and nowhere did it say, "skip this step if you are running a 32-bit system". It was kind of subtle.
But thanks for answering the questions quickly and completely.
The reason why it seemed like 64-bit systems were the main info is because the first step listed was for 64-bit systems and nowhere did it say, "skip this step if you are running a 32-bit system". It was kind of subtle.
But thanks for answering the questions quickly and completely.