Changeset View
Changeset View
Standalone View
Standalone View
chapter.xml
<!-- START SECTION 6: WINE MANAGEMENT GUIS --> | |||||
<sect1 xml:id="wine-management-guis"> | |||||
<title>WINE Management GUIs</title> | |||||
<para>While the base install of WINE comes with a GUI configuration tool | |||||
in <application>winecfg</application>, it's main | |||||
purpose is just that: strictly configuring an existing WINE | |||||
prefix. There are, however, more advanced applications that will | |||||
assist in the initial installation of applications as well as | |||||
optimizing their WINE environments. The below sections include a | |||||
selection of the most popular.</para> | |||||
<sect2 xml:id="winetricks"> | |||||
<title>winetricks</title> | |||||
<para><application>winetricks</application> is a | |||||
cross-platform, general purpose helper program for WINE. It is | |||||
not developed by the WINE project proper, but rather maintained | |||||
on | |||||
<link xlink:href="https://github.com/Winetricks/winetricks">Github</link> | |||||
bcr: See [[ https://www.freebsd.org/doc/en_US.ISO8859-1/books/fdp-primer/docbook-markup-links.html |… | |||||
by a group of contributors. It contains some automated | |||||
"recipes" for getting common applications to work on | |||||
WINE, both by optimizing the settings as well as acquiring some | |||||
DLL libraries automatically.</para> | |||||
<sect3 xml:id="installing-winetricks"> | |||||
<title>Installing winetricks</title> | |||||
<para>To install <application>winetricks</application> | |||||
on a &os; using binary packages, use the following | |||||
commands (note | |||||
<application>winetricks</application> requires | |||||
bcrUnsubmitted Done Inline ActionsThere are < and >'s here, which can be replaced by < and >, respectively. Is that your editor doing that? You can do a sweep over the whole document once you're done and do a search & replace for these. bcr: There are < and >'s here, which can be replaced by < and >, respectively. Is that your… | |||||
either the i386-wine or i386-wine-devel package, and is | |||||
therefore not installed automatically with other | |||||
dependencies):</para> | |||||
<screen>&prompt.root;<userinput>pkg install i386-wine | |||||
pkg install winetricks</userinput></screen> | |||||
bcrUnsubmitted Done Inline ActionsNo indentation within <screen> tags, see section 9.5.9 of the FDP primer. bcr: No indentation within <screen> tags, see [[ https://www.freebsd.org/doc/en_US.ISO8859… | |||||
<para>To compile it from source, issue the following in the | |||||
terminal:</para> | |||||
<screen>&prompt.root;<userinput>cd /usr/ports/emulators/i386-wine | |||||
make install | |||||
bcrUnsubmitted Not Done Inline ActionsUnindent this section here as well. bcr: Unindent this section here as well. | |||||
acpkendo_gmail.comAuthorUnsubmitted Done Inline ActionsThe start of this <screen> section is aligned with the start of the <para> section above it (although I have indented the second line to it), is this correct now? It does look like the example in the Primer. acpkendo_gmail.com: The start of this <screen> section is aligned with the start of the <para> section above it… | |||||
cd /usr/ports/emulators/winetricks | |||||
make install</userinput></screen> | |||||
<para>If a manual installation is required, refer to the | |||||
<link xlink:href="https://github.com/Winetricks/winetricks">Github</link> | |||||
account for instructions.</para> | |||||
</sect3> | |||||
<section xml:id="using-winetricks"> | |||||
<title>Using winetricks</title> | |||||
<para>Run <application>winetricks</application> with the | |||||
following command:</para> | |||||
<screen>&prompt;<userinput>winetricks</userinput></screen> | |||||
<para>Note you should be in a 32-bit prefix in order to run | |||||
<application>winetricks</application>. Launching | |||||
<application>winetricks</application> displays a | |||||
window with a number of choices, as follows:</para> | |||||
<para> | |||||
<inlinemediaobject> | |||||
<imageobject> | |||||
<imagedata fileref="./includes/winetricks-run-1.png" /> | |||||
</imageobject> | |||||
</inlinemediaobject> | |||||
</para> | |||||
<para>Selecting either <emphasis>Install an application</emphasis>, | |||||
<emphasis>Install a benchmark</emphasis>, or <emphasis>Install | |||||
a game</emphasis> shows a list with supported options, such as | |||||
the one below for applications:</para> | |||||
<para> | |||||
<inlinemediaobject> | |||||
<imageobject> | |||||
<imagedata fileref="./includes/winetricks-run-2.png" /> | |||||
</imageobject> | |||||
</inlinemediaobject> | |||||
</para> | |||||
<para>Selecting one or more items and clicking | |||||
<emphasis>OK</emphasis> will start their installation | |||||
process(es). Initially, some messages that appear to be errors | |||||
may show up, but they're actually informational alerts as | |||||
<application>winetricks</application> configures | |||||
the WINE environment to get around known issues for the | |||||
application: | |||||
</para> | |||||
<para> | |||||
<inlinemediaobject> | |||||
<imageobject> | |||||
<imagedata fileref="./includes/winetricks-app-install-1.png" /> | |||||
</imageobject> | |||||
</inlinemediaobject> | |||||
</para> | |||||
<para>Once these are circumvented, the actual installer for the | |||||
application will be run:</para> | |||||
<para> | |||||
<inlinemediaobject> | |||||
<imageobject> | |||||
<imagedata fileref="./includes/winetricks-app-install-2.png" /> | |||||
</imageobject> | |||||
</inlinemediaobject> | |||||
</para> | |||||
<para>Once the installation completes, the new Windows application | |||||
should be available from the desktop environment's standard | |||||
menu (shown in the screenshot below for the LXQT desktop | |||||
environment): | |||||
</para> | |||||
<para> | |||||
<inlinemediaobject> | |||||
<imageobject> | |||||
<imagedata fileref="./includes/winetricks-menu-1.jpg" /> | |||||
</imageobject> | |||||
</inlinemediaobject> | |||||
</para> | |||||
<para>In order to remove the application, run | |||||
<application>winetricks</application> again, and | |||||
select <emphasis>Run an uninstaller</emphasis>.</para> | |||||
<para> | |||||
<inlinemediaobject> | |||||
<imageobject> | |||||
<imagedata fileref="./includes/winetricks-uninstall-1.jpg" /> | |||||
</imageobject> | |||||
</inlinemediaobject> | |||||
</para> | |||||
<para>A &os.windows;-style dialog will appear with a list of | |||||
installed programs and components. Select the application to | |||||
be removed, then click the <emphasis>Modify/Remove</emphasis> | |||||
button.</para> | |||||
<para> | |||||
<inlinemediaobject> | |||||
<imageobject> | |||||
<imagedata fileref="./includes/winetricks-uninstall-2.jpg" /> | |||||
</imageobject> | |||||
</inlinemediaobject> | |||||
</para> | |||||
<para>This will run the applications built-in installer, which | |||||
should also have the option to uninstall.</para> | |||||
<para> | |||||
<inlinemediaobject> | |||||
<imageobject> | |||||
<imagedata fileref="./includes/winetricks-uninstall-3.jpg" /> | |||||
</imageobject> | |||||
</inlinemediaobject> | |||||
</para> | |||||
</sect3> | |||||
</sect2> | |||||
<sect2 xml:id="homura"> | |||||
<title>Homura</title> | |||||
<para>Homura is an application similar to | |||||
<application>winetricks</application>, although it | |||||
was inspired by the | |||||
<link xlink:href="https://lutris.net/">Lutris</link> gaming | |||||
system for Linux. But while it is focused on games, there are | |||||
also non-gaming applications available for install through | |||||
Homura.</para> | |||||
<sect3 xml:id="installing-homura"> | |||||
<title>Installing Homura</title> | |||||
<para>To install Homura's binary package, issue the following | |||||
command:</para> | |||||
<screen>&prompt.root;<userinput>pkg install homura</userinput></screen> | |||||
<para>Homura is avaialble in the FreeBSD Ports system. However, | |||||
bcrUnsubmitted Done Inline Actionss/avaialble/available/ bcr: s/avaialble/available/ | |||||
rather than the <emphasis>emulators</emphasis> section of | |||||
Ports or binary packages, look for it in the | |||||
<emphasis>games</emphasis> section. | |||||
</para> | |||||
<screen>&prompt.root;<userinput>cd /usr/ports/games/homura | |||||
make install</userinput></screen> | |||||
</sect3> | |||||
<sect3 xml:id="using-homura"> | |||||
<title>Using Homura</title> | |||||
<para>Homura's usage is quite similar to that of | |||||
<application>winetricks</application>. When using | |||||
it for the first time, launch it from the command line (or a | |||||
desktop environment runner applet) with:</para> | |||||
<screen>&prompt;<userinput>Homura</userinput></screen> | |||||
<para>This should result in a friendly welcome message. Click | |||||
<emphasis>OK</emphasis> to continue.</para> | |||||
<para> | |||||
<inlinemediaobject> | |||||
<imageobject> | |||||
<imagedata fileref="./includes/homura-launch-1.png.jpg" /> | |||||
</imageobject> | |||||
</inlinemediaobject> | |||||
</para> | |||||
<para>The program will also offer to place a link in the application | |||||
menu of compatible environments:</para> | |||||
<para> | |||||
<inlinemediaobject> | |||||
<imageobject> | |||||
<imagedata fileref="./includes/homura-run-2.png.jpg" /> | |||||
</imageobject> | |||||
</inlinemediaobject> | |||||
</para> | |||||
<para>Depending on the setup of the &os; machine, Homura may | |||||
display a message urging the install of native graphics | |||||
drivers.</para> | |||||
<para> | |||||
<inlinemediaobject> | |||||
<imageobject> | |||||
<imagedata fileref="./includes/homura-run-3.png.jpg" /> | |||||
</imageobject> | |||||
</inlinemediaobject> | |||||
</para> | |||||
<para>The application's window should then appear, which amounts to | |||||
a "main menu" with all its options. Many of the | |||||
items are the same as | |||||
<application>winetricks</application>, although | |||||
Homura offers some additional, helpful options such as opening | |||||
its data folder (<emphasis>Open Homura Folder</emphasis>) or | |||||
running a specified program (<emphasis>Run a executable in | |||||
prefix</emphasis>).</para> | |||||
<para> | |||||
<inlinemediaobject> | |||||
<imageobject> | |||||
<imagedata fileref="./includes/homura-install-1.png.jpg" /> | |||||
</imageobject> | |||||
</inlinemediaobject> | |||||
</para> | |||||
<para>To select one of Homura's supported applications to install, | |||||
select <emphasis>Installation</emphasis>, and click | |||||
<emphasis>OK</emphasis>. This will display a list of | |||||
applications Homura can install automatically. Select one, and | |||||
click <emphasis>OK</emphasis> to start the process.</para> | |||||
<para> | |||||
<inlinemediaobject> | |||||
<imageobject> | |||||
<imagedata fileref="./includes/homura-install-2.png.jpg" /> | |||||
</imageobject> | |||||
</inlinemediaobject> | |||||
</para> | |||||
<para>As a first step Homura will download the selected program. A | |||||
notification may appear in supported desktop environments.</para> | |||||
<para> | |||||
<inlinemediaobject> | |||||
<imageobject> | |||||
<imagedata fileref="./includes/homura-install-3.png.jpg" /> | |||||
</imageobject> | |||||
</inlinemediaobject> | |||||
</para> | |||||
<para>The program will also create a new prefix for the application. | |||||
A standard WINE dialog with this message will display.</para> | |||||
<para> | |||||
<inlinemediaobject> | |||||
<imageobject> | |||||
<imagedata fileref="./includes/homura-install-4.png.jpg" /> | |||||
</imageobject> | |||||
</inlinemediaobject> | |||||
</para> | |||||
<para>Next, Homura will install any prerequisites for the selected | |||||
program. This may involve downloading and extracting a fair | |||||
number of files, the details of which will show in dialogs.</para> | |||||
<para> | |||||
<inlinemediaobject> | |||||
<imageobject> | |||||
<imagedata fileref="./includes/homura-install-5.png.jpg" /> | |||||
</imageobject> | |||||
</inlinemediaobject> | |||||
</para> | |||||
<para>Downloaded packages are automatically opened and run as | |||||
required.</para> | |||||
<para> | |||||
<inlinemediaobject> | |||||
<imageobject> | |||||
<imagedata fileref="./includes/homura-install-6.png.jpg" /> | |||||
</imageobject> | |||||
</inlinemediaobject> | |||||
</para> | |||||
<para>The installation may end with a simple desktop notification or | |||||
message in the terminal, depending on how Homura was launched. | |||||
But in either case Homura should return to the main screen. To | |||||
confirm the installation was successful, select | |||||
<emphasis>Launcher</emphasis>, and click | |||||
<emphasis>OK</emphasis>.</para> | |||||
<para> | |||||
<inlinemediaobject> | |||||
<imageobject> | |||||
<imagedata fileref="./includes/homura-install-7.png.jpg" /> | |||||
</imageobject> | |||||
</inlinemediaobject> | |||||
</para> | |||||
<para>This will display a list of installed applications.</para> | |||||
<para> | |||||
<inlinemediaobject> | |||||
<imageobject> | |||||
<imagedata fileref="./includes/homura-install-8.png.jpg" /> | |||||
</imageobject> | |||||
</inlinemediaobject> | |||||
</para> | |||||
<para>To run the new program, select it from the list, and click | |||||
<emphasis>OK</emphasis>. To uninstall the application, select | |||||
<emphasis>Uninstallation</emphasis> from the main screen, | |||||
which will display a similar list. Select the program to be | |||||
removed, and click <emphasis>OK</emphasis>.</para> | |||||
<para> | |||||
<inlinemediaobject> | |||||
<imageobject> | |||||
<imagedata fileref="./includes/homura-uninstall-1.jpg" /> | |||||
</imageobject> | |||||
</inlinemediaobject> | |||||
</para> | |||||
</sect3> | |||||
</sect2> | |||||
<sect2 xml:id="running-multiple-management-guis"> | |||||
<title>Running Multiple Management GUIs</title> | |||||
<para>It's worth noting that the above solutions are not mutually | |||||
exclusive. It's perfectly acceptable, even advantageous, to have | |||||
both installed at the same time, as they support a different set | |||||
of programs.</para> | |||||
<para>However, it's wise to ensure that they don't access any of the | |||||
same WINE prefixes. Each of these solutions applies workarounds | |||||
and makes changes to the registries based on known workarounds | |||||
to existing WINE issues in order to make a given application run | |||||
smoothly. Allowing both | |||||
<application>winetricks</application> and Homura to | |||||
access the same prefix could lead to some of these being | |||||
overwritten, with the result being some or all applications do | |||||
not work as expected.</para> | |||||
</sect2> | |||||
</sect1> | |||||
See example 9.37 on how to pull up the "<link" part to save a bit of space in that line where the URL is. It's not wrong, just a tip.