More macOS install docs & some doc & manpage fixes

h/t Mark K. Kim & Shin-Ichi TOYAMA
This commit is contained in:
Bill Kendrick 2021-09-05 15:14:31 -07:00
parent 36c4be5549
commit ad47062a1a
16 changed files with 220 additions and 96 deletions

View file

@ -5,7 +5,7 @@
Copyright © 2002-2021 por varios colaboradores; vexa AUTHORS (AUTORES).
http://www.tuxpaint.org/
31 de Agosto de 2021
5 de Setembro de 2021
----------------------------------------------------------------------
@ -22,6 +22,7 @@
| * Debugging |
| * Uninstalling Tux Paint |
| * Windows |
| * macOS |
| * Linux |
+----------------------------------------------------+
@ -163,8 +164,7 @@ Compiling and Installation
Download the latest MSYS2 environment from
https://sourceforge.net/projects/msys2/files/Base/ and install it
where you'd like (the default is
"https://sourceforge.net/projects/msys2/files/Base/")
where you'd like (the default is "C:\msys64")
Open the MSYS2 shell from the "Start Menu" -> "MSYS2 64bit" ->
"MSYS2 MSYS" and execute following command (press [Intro] or
@ -740,9 +740,10 @@ Compiling and Installation
Debugging
A depuración (a «STDOUT», por exemplo, á terminal ou a un ficheiro
«stdout.txt» en Windows) pódese activar co axuste «DEBUG» (e, se se
quere un rexistro detallado, «VERBOSE») #define en «src/debug.h».
Debugging output — to "STDOUT" on Linux and Unix, to a "stdout.txt" file
on Windows, and to the file "/tmp/tuxpaint.log" on macOS — can be
enabled by setting "DEBUG" (and, if verbose logging is wanted,
"VERBOSE") #defines in "src/debug.h" and (re)compiling Tux Paint.
----------------------------------------------------------------------
@ -767,12 +768,22 @@ Uninstalling Tux Paint
----------------------------------------------------------------------
macOS
Delete "TuxPaint.app" from the "Applications" folder. Data files,
including the configuration files, stamps, and saved pictures, may be
found in "Library/Application Support/TuxPaint" (all users) and
"/Users/USERNAME/Library/Application Support/TuxPaint" (individual
users).
----------------------------------------------------------------------
Linux
Dentro do directorio de orixe de Tux Paint (onde compilou Tux Paint),
pode usar o destino «make uninstall» para desinstalar Tux Paint. De
xeito predeterminado, debe facelo o usuario «root» («superusuario»),
mais se instalou Tux Paint noutro lugar (por exemplo, usando a
configuración «PREFIX=...» en «make» e «make install»), pode que non e
queira proporcionar a mesma configuración aquí. (Consulte as
instrucións de instalación anteriores para obter máis información.)
Within the Tux Paint source directory (where you compiled Tux Paint),
you can use the "make uninstall" target to uninstall Tux Paint. By
default, this must be done by the "root" user ('superuser'), but if
you installed Tux Paint somewhere else (e.g., using a "PREFIX=..."
setting to "make" and "make install"), you may not, and will want to
provide those same settings here. (See the installation instructions
above for further information.)

View file

@ -26,7 +26,7 @@
</p>
<p>
31 de Agosto de 2021 </p>
5 de Setembro de 2021 </p>
</center>
<hr size="2" noshade />
@ -77,6 +77,9 @@
<li>
<a href="#uninstalling-windows">Windows</a>
</li>
<li>
<a href="#uninstalling-macOS">macOS</a>
</li>
<li>
<a href="#uninstalling-linux">Linux</a>
</li>
@ -177,7 +180,7 @@
<h4>Compatibilidade de SVG</h4>
<blockquote>
<p>
A partir de Tux Paint 0.9.17, Tux Paint pode cargar imaxes SVG (Scalable Vector Graphics — Gráficos Vectoriais Escalábeis) como selos. Admítense dous conxuntos de bibliotecas e pódese desactivar completamente a compatibilidade SVG (a través de «<code>make SVG_LIB:=</code>») </p>
A partir de Tux Paint 0.9.17, Tux Paint pode cargar imaxes SVG (Scalable Vector Graphics — Gráficos Vectoriais Escalábeis) como selos. Admítense dous conxuntos de bibliotecas e pódese desactivar completamente a compatibilidade SVG (a través de «<code style="white-space: nowrap;">make SVG_LIB:=</code>») </p>
<h5>librsvg-2 &amp; libCairo2 (bibliotecas máis recentes)</h5>
<ul>
@ -251,7 +254,7 @@
Many tools and libraries are required to build Tux Paint. The package management system "<code>pacman</code>" helps you install them automatically solving complicated dependencies. </p>
<p>
Download the latest MSYS2 environment from <a href="https://sourceforge.net/projects/msys2/files/Base/">https://sourceforge.net/projects/msys2/files/Base/</a> and install it where you'd like (the default is "<a href="https://sourceforge.net/projects/msys2/files/Base/">https://sourceforge.net/projects/msys2/files/Base/</a>") </p>
Download the latest MSYS2 environment from <a href="https://sourceforge.net/projects/msys2/files/Base/">https://sourceforge.net/projects/msys2/files/Base/</a> and install it where you'd like (the default is "<code>C:\msys64</code>") </p>
<p>
Open the MSYS2 shell from the "Start Menu" -&gt; "MSYS2 64bit" -&gt; "MSYS2 MSYS" and execute following command (press <b><code>[Intro]</code></b> or <b><code>[Retorno]</code></b> to accept the defaults for all questions):
<blockquote>
@ -632,7 +635,7 @@
Desactivar a compatibilidade de «SVG» (e, polo tanto, as dependencias de «Cairo, libSVG, e svg-cairo»: </h4>
<blockquote>
<p>
Para desactivar a compatibilidade con SVG (por exemplo, se o seu sistema non é compatíbel coa biblioteca de Cairo ou outras dependencias relacionadas co SVG), pode executar «<code>make</code>» engadindo «<code>SVG_LIB= SVG_CFLAGS= NOSVGFLAG=NOSVG</code>»:
Para desactivar a compatibilidade con SVG (por exemplo, se o seu sistema non é compatíbel coa biblioteca de Cairo ou outras dependencias relacionadas co SVG), pode executar «<code>make</code>» engadindo «<code style="white-space: nowrap;">SVG_LIB= SVG_CFLAGS= NOSVGFLAG=NOSVG</code>»:
<blockquote>
<code>
$ make SVG_LIB= SVG_CFLAGS=
@ -846,8 +849,7 @@
% make install
</code>
</blockquote>
... to create the <code>TuxPaint.app</code> application bundle that can be run in-place or
copied to <code>/Applications</code>. It also creates <code>TuxPaint.dmg</code> for distribution. </p>
... to create the <code>TuxPaint.app</code> application bundle that can be run in-place or copied to <code>/Applications</code>. It also creates <code>TuxPaint.dmg</code> for distribution. </p>
</blockquote>
<hr size="1" noshade width="75%" />
@ -888,7 +890,7 @@ copied to <code>/Applications</code>. It also creates <code>TuxPaint.dmg</code>
The list of macOS versions and the last version of Xcode compatible with them are laid out nicely on the Wikipedia page on Xcode: <a href="https://en.wikipedia.org/wiki/Xcode#Version_comparison_table">https://en.wikipedia.org/wiki/Xcode#Version_comparison_table</a> </p>
<p>
And because Xcode is being installed manually, you can skip the step to install the Xcode command line tools (do not run "<code>xcode-select --install</code>") but otherwise build Tux Paint using the same steps described in the earlier part of this document. </p>
And because Xcode is being installed manually, you can skip the step to install the Xcode command line tools (do not run "<code style="white-space: nowrap;">xcode-select --install</code>") but otherwise build Tux Paint using the same steps described in the earlier part of this document. </p>
</blockquote>
@ -903,7 +905,7 @@ copied to <code>/Applications</code>. It also creates <code>TuxPaint.dmg</code>
Debugging </a>
</h2>
<blockquote>
A depuración (a «STDOUT», por exemplo, á terminal ou a un ficheiro «<code>stdout.txt</code>» en Windows) pódese activar co axuste «<code>DEBUG</code>» (e, se se quere un rexistro detallado, «<code>VERBOSE</code>») <code>#define </code> en «<code>src/debug.h</code>». </blockquote>
Debugging output &mdash; to "STDOUT" on Linux and Unix, to a "<code>stdout.txt</code>" file on Windows, and to the file "<code>/tmp/tuxpaint.log</code>" on macOS &mdash; can be enabled by setting "<code>DEBUG</code>" (and, if verbose logging is wanted, "<code>VERBOSE</code>") <code>#define</code>s in "<code>src/debug.h</code>" and (re)compiling Tux Paint. </blockquote>
<hr size="2" noshade />
@ -935,13 +937,25 @@ copied to <code>/Applications</code>. It also creates <code>TuxPaint.dmg</code>
<hr size="1" noshade />
<h3>
<a name="uninstalling-macos" id="uninstalling-macos">
macOS </a>
</h3>
<blockquote>
<p>
Delete "<code>TuxPaint.app</code>" from the "Applications" folder. Data files, including the configuration files, stamps, and saved pictures, may be found in "<code style="white-space: nowrap;">Library/Application Support/TuxPaint</code>" (all users) and "<code style="white-space: nowrap;">/Users/<i>USERNAME</i>/Library/Application Support/TuxPaint</code>" (individual users). </p>
</blockquote>
<hr size="1" noshade />
<h3>
<a name="uninstalling-linux" id="uninstalling-linux">
Linux </a>
</h3>
<blockquote>
<p>
Dentro do directorio de orixe de Tux Paint (onde compilou Tux Paint), pode usar o destino «<code>make uninstall</code>» para desinstalar Tux Paint. De xeito predeterminado, debe facelo o usuario «root» («superusuario»), mais se instalou Tux Paint noutro lugar (por exemplo, usando a configuración «<code>PREFIX=...</code>» en «<code>make</code>» e «<code>make install</code>»), pode que non e queira proporcionar a mesma configuración aquí. (Consulte as instrucións de instalación anteriores para obter máis información.) </p>
Within the Tux Paint source directory (where you compiled Tux Paint), you can use the "<code style="white-space: nowrap;">make uninstall</code>" target to uninstall Tux Paint. By default, this must be done by the "root" user ('superuser'), but if you installed Tux Paint somewhere else (e.g., using a "<code>PREFIX=...</code>" setting to "<code>make</code>" and "<code style="white-space: nowrap;">make install</code>"), you may not, and will want to provide those same settings here. (See the <a href="#compiling-linux">installation instructions above</a> for further information.) </p>
</blockquote>
<blockquote>
</body>