1324 lines
68 KiB
HTML
1324 lines
68 KiB
HTML
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
|
||
<html>
|
||
<head>
|
||
<title>
|
||
Documentación da instalación de Tux Paint </title>
|
||
<meta http-equiv="Content-Type"
|
||
content="text/html; charset=utf-8">
|
||
<style>
|
||
body { font-size: large; }
|
||
table { font-size: large; }
|
||
div.screenshot-center {
|
||
text-align: center;
|
||
}
|
||
div.screenshot-right {
|
||
float: right;
|
||
margin-left: 1em;
|
||
margin-bottom: 1em;
|
||
}
|
||
div.screenshot-right-after {
|
||
clear: both;
|
||
}
|
||
div.keeptogether { page-break-inside: avoid; }
|
||
section h1 { font-size: 2em; }
|
||
h1, h2, h3, h4, h5 { font-family: sans; }
|
||
h1 { color: #800; page-break-before: always; break-before: always; }
|
||
h2 { color: #440; page-break-after: avoid; break-after: avoid; }
|
||
h3 { color: #080; page-break-after: avoid; break-after: avoid; }
|
||
h4 { color: #008; page-break-after: avoid; break-after: avoid; }
|
||
h5 { color: #808; page-break-after: avoid; break-after: avoid; }
|
||
h1 + p { page-break-inside: avoid; }
|
||
h2 + p { page-break-inside: avoid; }
|
||
h3 + p { page-break-inside: avoid; }
|
||
h4 + p { page-break-inside: avoid; }
|
||
h5 + p { page-break-inside: avoid; }
|
||
dt {
|
||
font-size: large;
|
||
color: #404;
|
||
font-family: sans;
|
||
margin-top: 1em;
|
||
margin-bottom: 0.25em;
|
||
}
|
||
dd, blockquote {
|
||
border-left: 1px solid #888;
|
||
padding-left: 1em;
|
||
border-radius: 0 0 0 1em;
|
||
}
|
||
p.note {
|
||
border: 1px solid #000;
|
||
background-color: #eee;
|
||
border-radius: 0.5em;
|
||
padding: 0.5em;
|
||
display: inline-block;
|
||
margin-right: 3em;
|
||
margin-top: 0.5em;
|
||
margin-bottom: 0.5em;
|
||
}
|
||
section.outer {
|
||
padding-bottom: 1em;
|
||
border-bottom: 2px solid #000;
|
||
}
|
||
section.indent p,dl {
|
||
margin-left: 2em;
|
||
}
|
||
section.indent dl p {
|
||
margin-left: 0;
|
||
}
|
||
p + ul, p + ol {
|
||
margin-left: 2em;
|
||
}
|
||
|
||
@media print {
|
||
p {
|
||
orphans: 3;
|
||
widows: 3;
|
||
}
|
||
}
|
||
</style>
|
||
</head>
|
||
<body bgcolor="#FFFFFF"
|
||
text="#000000"
|
||
link="#0000FF"
|
||
vlink="#FF0000"
|
||
alink="#FF00FF">
|
||
<section class="outer">
|
||
<header>
|
||
<center>
|
||
<h1>
|
||
<img src="../../html/images/tuxpaint-title.png"
|
||
width="205"
|
||
height="210"
|
||
alt="Tux Paint"><br>
|
||
versión 0.9.30<br/>
|
||
Documentación da instalación </h1>
|
||
|
||
<p>
|
||
Copyright © 2002-2023 by varios colaboradores; see <a href="../../AUTHORS.txt">AUTHORS.txt</a>.<br>
|
||
<a href="https://tuxpaint.org/">https://tuxpaint.org/</a>
|
||
</p>
|
||
|
||
<p>
|
||
29 de Marzo de 2023 </p>
|
||
</center>
|
||
</header>
|
||
|
||
<table border="2"
|
||
cellspacing="0"
|
||
cellpadding="2"
|
||
summary="Índice"
|
||
align="center"
|
||
style="page-break-inside: avoid;">
|
||
<tr>
|
||
<th>
|
||
Índice </th>
|
||
</tr>
|
||
|
||
<tr>
|
||
<td>
|
||
<ul>
|
||
<li><a href="#requirements">Requirements</a> <ul>
|
||
<li><a href="#req-libsdl">Simple DirectMedia Layer library (libSDL)</a></li> <li><a href="#req-other-libs">Outras bibliotecas</a></li> </ul>
|
||
</li>
|
||
<li><a href="#compiling">Compiling and Installation</a> <ul>
|
||
<li><a href="#compiling-windows">Windows</a></li> <li><a href="#compiling-linux">Linux/Unix</a></li> <li><a href="#compiling-macos">macOS</a></li> <li><a href="#compiling-android">Android</a></li> </ul>
|
||
</li>
|
||
<li><a href="#debugging">Debugging</a></li> <li><a href="#uninstalling">Uninstalling Tux Paint</a> <ul>
|
||
<li><a href="#uninstalling-windows">Windows</a></li> <li><a href="#uninstalling-macOS">macOS</a></li> <li><a href="#uninstalling-linux">Linux</a></li> </ul>
|
||
</li>
|
||
</ul>
|
||
</td>
|
||
</tr>
|
||
</table>
|
||
</section>
|
||
|
||
<section class="outer indent"><!-- H1: Requirements -->
|
||
<header>
|
||
<h1>
|
||
<a name="requirements" id="requirements">
|
||
Requirements </a>
|
||
</h1>
|
||
</header>
|
||
|
||
<section class="indent"><!-- H2: Simple DirectMedia Layer library (libSDL) -->
|
||
<header>
|
||
<h2>
|
||
<a name="req-libsdl" id="req-libsdl">
|
||
Simple DirectMedia Layer library (libSDL) </a>
|
||
</h2>
|
||
</header>
|
||
|
||
<p>
|
||
Tux Paint require a «Simple DirectMedia Layer Library (libSDL)», unha biblioteca de programación multimedia de código aberto dispoñíbel baixo a licenza pública GNU Lesser General Public License (LGPL). </p>
|
||
|
||
<p>
|
||
Along with libSDL, Tux Paint depends on a number of other SDL 'helper' libraries: SDL_Image (for graphics files), SDL_gfx (for some graphical functions, like rotation), SDL_TTF and (optionally) SDL2_Pango (for True Type Font support) and, optionally, SDL_Mixer (for sound effects). </p>
|
||
|
||
<p>
|
||
As bibliotecas SDL están dispoñíbeis como código fonte ou como paquetes RPM ou Debian para varias distribucións de Linux. Pódense descargar dende: </p>
|
||
<ul>
|
||
<li>libSDL: <a href="http://www.libsdl.org/">http://www.libsdl.org/</a></li>
|
||
<li>SDL_image: <a href="https://github.com/libsdl-org/SDL_image">https://github.com/libsdl-org/SDL_image</a></li>
|
||
<li>SDL_gfx: <a href="https://www.ferzkopp.net/wordpress/2016/01/02/sdl_gfx-sdl2_gfx/">https://www.ferzkopp.net/wordpress/2016/01/02/sdl_gfx-sdl2_gfx/</a> (<a href="https://sourceforge.net/projects/sdlgfx/">https://sourceforge.net/projects/sdlgfx/</a>)</li>
|
||
<li>SDL_ttf: <a href="https://github.com/libsdl-org/SDL_ttf">https://github.com/libsdl-org/SDL_ttf</a></li>
|
||
<li>SDL2_Pango: <a href="https://github.com/markuskimius/SDL2_Pango">https://github.com/markuskimius/SDL2_Pango</a> (opcional)</li>
|
||
<li>SDL_mixer: <a href="https://github.com/libsdl-org/SDL_mixer">https://github.com/libsdl-org/SDL_mixer</a> (opcional)</li>
|
||
</ul>
|
||
|
||
<p>
|
||
Normalmente tamén están dispoñíbeis xunto coa súa distribución de Linux (p. ex.: nun medio de instalación ou dispoñíbeis a través dun software de mantemento de paquetes como «<code>apt</code>» de Debian). </p>
|
||
|
||
<p class="note">
|
||
<span title="Information">💡</span> <strong>Note:</strong> When installing libraries from packages, be sure to ALSO install the development versions of the packages. (For example, install both "<code>SDL2-2.24.0.rpm</code>" <em>and</em> "<code>SDL2-devel-2.24.0.rpm</code>".) </p>
|
||
</section><!-- H2: Simple DirectMedia Layer library (libSDL) -->
|
||
|
||
<section class="indent"><!-- H2: Other Libraries -->
|
||
<header>
|
||
<h3>
|
||
<a name="req-other-libs" id="req-other-libs">
|
||
Outras bibliotecas </a>
|
||
</h3>
|
||
</header>
|
||
|
||
<p>
|
||
Tux Paint tamén aproveita outras bibliotecas libres con licenza LGPL. En Linux, do mesmo xeito que SDL, deberían estar xa instaladas ou estar dispoñíbeis para a súa instalación como parte da súa distribución de Linux. </p>
|
||
|
||
<dl>
|
||
<dt><strong>libPNG</strong></dt>
|
||
<dd>
|
||
<p>
|
||
Tux Paint utiliza o formato PNG (Portable Network Graphics – Gráficos de Rede Portátiles) para os seus ficheiros de datos. A imaxe SDL requirirá a instalación de libPNG. </p>
|
||
|
||
<p>
|
||
<a href="http://www.libpng.org/pub/png/libpng.html">http://www.libpng.org/pub/png/libpng.html</a>
|
||
</p>
|
||
</dd>
|
||
|
||
<dt><strong>gettext</strong></dt>
|
||
<dd>
|
||
<p>
|
||
Tux Paint utiliza a configuración local do sistema xunto coa biblioteca «gettext» para admitir varios idiomas (p. ex., o español). Necesitará ter a biblioteca gettext instalada. </p>
|
||
|
||
<p>
|
||
<a href="http://www.gnu.org/software/gettext/">http://www.gnu.org/software/gettext/</a>
|
||
</p>
|
||
</dd>
|
||
|
||
<dt><strong>libpaper (Só Linux/Unix)</strong></dt>
|
||
<dd>
|
||
<p>
|
||
A partir de Tux Paint 0.9.17, Tux Paint pode determinar o tamaño de papel predeterminado do seu sistema (p. ex.: A4 ou Carta), ou pódeselle indicar que use un tamaño de papel particular, grazas a «libpaper». </p>
|
||
|
||
<p>
|
||
<a href="https://github.com/naota/libpaper">https://github.com/naota/libpaper</a>
|
||
</p>
|
||
</dd>
|
||
|
||
<dt><strong>FriBiDi</strong></dt>
|
||
<dd>
|
||
<p>
|
||
As ferramentas «Texto» e «Etiqueta» de Tux Paint admiten linguaxes bidireccionais grazas á biblioteca «FriBiDi». </p>
|
||
|
||
<p>
|
||
<a href="http://fribidi.org/">http://fribidi.org/</a>
|
||
</p>
|
||
</dd>
|
||
|
||
<dt><strong>Compatibilidade de SVG</strong></dt>
|
||
<dd>
|
||
<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>
|
||
|
||
<dl>
|
||
<dt>librsvg-2 & libCairo2 (bibliotecas máis recentes)</dt>
|
||
<dd>
|
||
<ul>
|
||
<li>libRSVG 2: <a href="http://librsvg.sourceforge.net/">http://librsvg.sourceforge.net/</a></li>
|
||
<li>Cairo 2: <a href="http://www.cairographics.org/">http://www.cairographics.org/</a></li>
|
||
<li>Estes tamén dependen do seguinte: <ul>
|
||
<li>GdkPixbuf & GLib: <a href="http://www.gtk.org/">http://www.gtk.org/</a></li>
|
||
<li>Pango: <a href="http://www.pango.org/">http://www.pango.org/</a></li>
|
||
</ul>
|
||
</li>
|
||
</ul>
|
||
</dd>
|
||
|
||
<dt>Bibliotecas SVG máis antigas</dt>
|
||
<dd>
|
||
<ul>
|
||
<li>libcairo1, libsvg1, & libsvg-cairo1: <a href="http://www.cairographics.org/">http://www.cairographics.org/</a></li>
|
||
<li>Estes tamén dependen do seguinte: <ul>
|
||
<li>libxml2: <a href="https://gitlab.gnome.org/GNOME/libxml2">https://gitlab.gnome.org/GNOME/libxml2</a></li>
|
||
</ul>
|
||
</li>
|
||
</ul>
|
||
</dd>
|
||
</dl>
|
||
</dd>
|
||
|
||
<dt><strong>Función de exportación de GIF animado</strong></dt>
|
||
<dd>
|
||
<p>
|
||
Para a compatibilidade da exportación de GIF animados (presentacións de diapositivas), é necesaria a biblioteca «libimagequant» (do proxecto «pngquant2»). </p>
|
||
|
||
<p>
|
||
<a href="https://github.com/ImageOptim/libimagequant">https://github.com/ImageOptim/libimagequant</a>
|
||
</p>
|
||
</dd>
|
||
|
||
<dt><strong>Ferramentas NetPBM (opcional) Xa non se usa, de xeito predeterminado</strong></dt>
|
||
<dd>
|
||
<p class="note">
|
||
<span title="Version variation">📜</span> En Linux e Unix, as versións anteriores de Tux Paint utilizaban as ferramentas NetPBM para axudar á impresión. (Tux Paint xera un PNG e convértese nun PostScript usando as ferramentas da liña de ordes NetPBM «<code>pngtopnm</code>» e «<code>pnmtops</code>»). </p>
|
||
|
||
<p>
|
||
<a href="http://netpbm.sourceforge.net/">http://netpbm.sourceforge.net/</a>
|
||
</p>
|
||
</dd>
|
||
</dl>
|
||
</section>
|
||
</section>
|
||
|
||
<section class="outer indent"><!-- H1: Compiling and Installation -->
|
||
<header>
|
||
<h1>
|
||
<a name="compiling" id="compiling">
|
||
Compiling and Installation </a>
|
||
</h1>
|
||
</header>
|
||
|
||
<p>
|
||
Tux Paint publícase baixo a Licenza Pública Xeral de GNU (GPL) (consulte «COPYING.txt» para máis detalles) e, polo tanto, o «código fonte» do programa está dispoñíbel libremente. </p>
|
||
|
||
<section class="indent"><!-- H2: Windows -->
|
||
<header>
|
||
<h2>
|
||
<a name="compiling-windows" id="compiling-windows">
|
||
Windows </a>
|
||
</h2>
|
||
|
||
<p style="font-size: small;">
|
||
<em>
|
||
10 de Xullo de 2022 Shin-ichi TOYAMA <<a href="mailto:dolphin6k@wmail.plala.or.jp">dolphin6k@wmail.plala.or.jp</a>>
|
||
</em>
|
||
</p>
|
||
</header>
|
||
|
||
<section class="indent"><!-- H3: Compiling Set-Up -->
|
||
<header>
|
||
<h3>Compiling Set-Up</h3>
|
||
</header>
|
||
|
||
<p>
|
||
A partir de febreiro de 2005 (comezando con Tux Paint 0.9.15), o «<code>Makefile</code>» inclúe compatibilidade para construír nun sistema Windows usando MinGW/MSYS (<a href="https://sourceforge.net/projects/msys2/">https://sourceforge.net/projects/msys2/</a>). </p>
|
||
|
||
<p>
|
||
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>
|
||
|
||
<section class="indent"><!-- H4: MSYS2 -->
|
||
<header>
|
||
<h4>MYSYS2</h4>
|
||
</header>
|
||
|
||
<p>
|
||
Download the latest MSYS2 environment from <a href="https://www.msys2.org/">https://www.msys2.org/</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" -> "MSYS2 64bit" -> "MSYS2 MSYS" and execute following command: <blockquote>
|
||
<code>
|
||
$ yes "" | pacman -Syu
|
||
</code>
|
||
</blockquote>
|
||
</p>
|
||
|
||
<p>
|
||
This will update core system and the window will close automatically. Open the msys2 shell again and execute following command to finish remaining updating process. <blockquote>
|
||
<code>
|
||
$ yes "" | pacman -Syu
|
||
</code>
|
||
</blockquote>
|
||
</p>
|
||
|
||
<p>
|
||
Within the MSYS2 shell, run the following command to install basic development tools: <blockquote>
|
||
<code>
|
||
$ yes "" | pacman -S make automake-wrapper autoconf-wrapper libtool git zip patch gperf dos2unix
|
||
</code>
|
||
</blockquote>
|
||
</p>
|
||
|
||
<p>
|
||
<i>
|
||
Proceed to the next "<a href="#64bit">MinGW 64bit (x86_64) toolchains</a>" section, or skip to the "<a href="#32bit">MinGW 32bit (i686) toolchains</a>" section if you need only a 32bit build environment. </i>
|
||
</p>
|
||
</section>
|
||
|
||
<hr size="1" noshade width="75%" />
|
||
<section class="indent"><!-- H4: MinGW...compiler and tools -->
|
||
<header>
|
||
<h4>
|
||
<a name="64bit" id="64bit">
|
||
MinGW 64bit (x86_64) compiler and tools </a>
|
||
</h4>
|
||
</header>
|
||
|
||
<p>
|
||
Within the MSYS2 shell, run the following command to install 64bit compiler and basic development tools: <blockquote>
|
||
<code>
|
||
$ yes "" | pacman -S mingw-w64-x86_64-{gcc,pkgconf,ntldd-git}
|
||
</code>
|
||
</blockquote>
|
||
</p>
|
||
<p>
|
||
"<code>ntldd</code>" is a small tool which examine windows executable files to list Dynamic Link Library (<code>.dll</code>) files they depends on. Tux Paint's packaging process for binary distribution uses it to find required <code>.dll</code> files. </p>
|
||
</section><!-- H4: MinGW...toolchains -->
|
||
|
||
<section class="indent"><!-- H4: ...dependency libraries for Tux Paint -->
|
||
<header>
|
||
<h4>
|
||
64bit (x86_64) dependency libraries for Tux Paint and Tux Paint Config </h4>
|
||
</header>
|
||
|
||
<p>
|
||
You can install tools and libraries required for compiling Tux Paint and Tux Paint Config on MSYS2/MINGW using "<code>pacman</code>" except for SDL2_Pango and libunibreak. </p>
|
||
<p>
|
||
FLTK is a cross-platform GUI toolkit used by "Tux Paint Config". You can skip installing it if you are <em>only</em> building "Tux Paint". </p>
|
||
<p>
|
||
<blockquote>
|
||
<code>
|
||
$ pacman -S mingw-w64-x86_64-SDL_{image,ttf,gfx}<br/>
|
||
$ pacman -S mingw-w64-x86_64-{librsvg,fribidi,libimagequant,fltk}<br/>
|
||
</code>
|
||
</blockquote>
|
||
</p>
|
||
<p class="note">
|
||
<span title="Information">💡</span> <strong>Note:</strong> Close the shell before proceeding to the remaining process. </p>
|
||
</section><!-- H4: ...dependency libraries for Tux Paint -->
|
||
|
||
<section class="indent"><!-- H4: Install SDL2_Pango... -->
|
||
<header>
|
||
<h4>
|
||
Install SDL2_Pango and libunibreak on the 64bit environment </h4>
|
||
</header>
|
||
|
||
<p>
|
||
SDL2_Pango and libunibreak should be installed manually. </p>
|
||
<p>
|
||
This time, use the MinGW "64bit" shell. Open the shell from the "Start Menu" -> "MSYS2 64bit" -> "MSYS2 MinGW 64-bit" </p>
|
||
|
||
<section class="indent"><!-- H5: SDL2_Pango -->
|
||
<header>
|
||
<h5>SDL2_Pango</h5>
|
||
</header>
|
||
|
||
<p>
|
||
You can fetch the source code from the Mark K. Kim's git repositry, compile and install it as follows. <blockquote>
|
||
<code>
|
||
$ git clone https://github.com/markuskimius/SDL2_Pango<br/>
|
||
$ cd SDL2_Pango<br/>
|
||
$ ./configure --prefix=/mingw64 && make && make install<br/>
|
||
</code>
|
||
</blockquote>
|
||
</p>
|
||
</section><!-- H5: SDL2_Pango -->
|
||
|
||
<section class="indent"><!-- H5: libunibreak -->
|
||
<header>
|
||
<h5>libunibreak</h5>
|
||
</header>
|
||
|
||
<p>
|
||
libunibreak is required for compiling Tux Paint Config. You can skip installing it if you are <em>only</em> building "Tux Paint". </p>
|
||
<p>
|
||
You can fetch the source code from the git repositry and compile it as follows. <blockquote>
|
||
<code>
|
||
$ git clone https://github.com/adah1972/libunibreak libunibreak<br/>
|
||
$ cd libunibreak<br/>
|
||
$ ./augogen.sh --prefix=/mingw64 && make && make install
|
||
</code>
|
||
</blockquote>
|
||
</p>
|
||
</section><!-- H5: libunibreak -->
|
||
|
||
<p>
|
||
<i>
|
||
Proceed to the next "<a href="#32bit">MinGW 32bit (i686) toolchains</a>" section, or skip to the "<a href="#imagemagick">ImageMagick</a>" section if you need only a 64bit build environment. </i>
|
||
</p>
|
||
|
||
</section><!-- H4: Install SDL2_Pango... -->
|
||
|
||
<hr size="1" noshade width="75%" />
|
||
<section class="indent"><!-- H4: MinGW...compiler and tools -->
|
||
<header>
|
||
<h4>
|
||
<a name="32bit" id="32bit">
|
||
MinGW 32bit (i686) compiler and tools </a>
|
||
</h4>
|
||
</header>
|
||
|
||
<p>
|
||
Within the MSYS2 shell, run the following command to install 32bit compiler and basic development tools: <blockquote>
|
||
<code>
|
||
$ yes "" | pacman -S mingw-w64-i686-{gcc,pkgconf,ntldd-git}
|
||
</code>
|
||
</blockquote>
|
||
</p>
|
||
<p>
|
||
"<code>ntldd</code>" is a small tool which examine windows executable files to list Dynamic Link Library (<code>.dll</code>) files they depends on. Tux Paint's packaging process for binary distribution uses it to find required <code>.dll</code> files. </p>
|
||
</section><!-- H4: MinGW...toolchains -->
|
||
|
||
<section class="indent"><!-- H4: ...dependency libraries for Tux Paint -->
|
||
<header>
|
||
<h4>
|
||
32bit (i686) dependency libraries for Tux Paint and Tux Paint Config </h4>
|
||
</header>
|
||
|
||
<p>
|
||
You can install tools and libraries required for compiling Tux Paint and Tux Paint Config on MSYS2/MINGW using "<code>pacman</code>" except for SDL2_Pango and libunibreak. </p>
|
||
<p>
|
||
FLTK is a cross-platform GUI toolkit used by "Tux Paint Config". You can skip installing it if you are <em>only</em> building "Tux Paint". </p>
|
||
<p>
|
||
<blockquote>
|
||
<code>
|
||
$ pacman -S mingw-w64-i686-SDL_{image,ttf,gfx}<br/>
|
||
$ pacman -S mingw-w64-i686-{librsvg,fribidi,libimagequant,fltk}<br/>
|
||
</code>
|
||
</blockquote>
|
||
</p>
|
||
<p class="note">
|
||
<span title="Information">💡</span> <strong>Note:</strong> Close the shell before proceeding to the remaining process. </p>
|
||
</section><!-- H4: ...dependency libraries for Tux Paint -->
|
||
|
||
<section class="indent"><!-- H4: Install SDL2_Pango... -->
|
||
<header>
|
||
<h4>
|
||
Install SDL2_Pango and libunibreak on the 32bit environment </h4>
|
||
</header>
|
||
|
||
<p>
|
||
SDL2_Pango and libunibreak should be installed manually. </p>
|
||
<p>
|
||
This time, use the MinGW "32bit" shell. Open the shell from the "Start Menu" -> "MSYS2 64bit" -> "MSYS2 MinGW 32-bit" </p>
|
||
|
||
<section class="indent"><!-- H5: SDL2_Pango -->
|
||
<header>
|
||
<h5>SDL2_Pango</h5>
|
||
</header>
|
||
|
||
<p>
|
||
You can fetch the source code from the Mark K. Kim's git repositry, compile and install it as follows. <blockquote>
|
||
<code>
|
||
$ git clone https://github.com/markuskimius/SDL2_Pango<br/>
|
||
$ cd SDL2_Pango<br/>
|
||
$ ./configure --prefix=/mingw32 && make && make install<br/>
|
||
</code>
|
||
</blockquote>
|
||
</p>
|
||
</section><!-- H5: SDL2_Pango -->
|
||
|
||
<section class="indent"><!-- H5: libunibreak -->
|
||
<header>
|
||
<h5>libunibreak</h5>
|
||
</header>
|
||
|
||
<p>
|
||
libunibreak is required for compiling Tux Paint Config. You can skip installing it if you are <em>only</em> building "Tux Paint". </p>
|
||
<p>
|
||
You can fetch the source code from the git repositry and compile it as follows. <blockquote>
|
||
<code>
|
||
$ git clone https://github.com/adah1972/libunibreak libunibreak<br/>
|
||
$ cd libunibreak<br/>
|
||
$ ./augogen.sh --prefix=/mingw32 && make && make install
|
||
</code>
|
||
</blockquote>
|
||
</p>
|
||
</section><!-- H5: libunibreak -->
|
||
|
||
|
||
</section><!-- H4: Install SDL2_Pango... -->
|
||
|
||
</section><!-- H3: Compiling Set-Up -->
|
||
|
||
<section class="indent"><!-- H3: ImageMagick -->
|
||
<header>
|
||
<h3>
|
||
<a name="imagemagick" id="imagemagick">ImageMagick</a>
|
||
</h3>
|
||
</header>
|
||
|
||
<p>
|
||
<a href="https://imagemagick.org">ImageMagick</a> is a compilation of command line tools to create, edit, compose, or convert bitmap images supporting quite a large number of image formats. Tux Paint uses two functions ("convert" and "composite") in it to generate thumbnails for startar images and templates during the build process. </p>
|
||
<p>
|
||
Using official binary release available from "<a href="https://imagemagick.org/script/download.php#windows">Windows Binary Release</a>" is recommended, due to the commands installed with "<code>pacman</code>" on MinGW/MSYS not working as expected! </p>
|
||
<p>
|
||
Do not forget to enable "Install legacy utilities (e.g. convert)" while installing it, because Tux Paint's build process uses them. </p>
|
||
<p>
|
||
Add the path to the directory in which ImageMagick is installed at the top of your "PATH" environment variable. For example: <blockquote>
|
||
<code>
|
||
$ export PATH=/c/Program\ Files/ImageMagick-7.0.10-Q16-HDRI:$PATH
|
||
</code>
|
||
</blockquote>
|
||
</p>
|
||
<p>
|
||
You can make this permanent by adding the above to your the BASH shell configuration file, "<code>~/.bash_profile</code>". </p>
|
||
</section><!-- H3: ImageMagick -->
|
||
|
||
<section class="indent"><!-- H3: Tux Paint & Tux Paint Config. -->
|
||
<header>
|
||
<h3>Tux Paint & Tux Paint Config.</h3>
|
||
</header>
|
||
|
||
<p>
|
||
You can compile 64-bit binaries using "MSYS2 64bit" shell, and 32-bit binaries using "MSYS2 32bit" shell, respectively. </p>
|
||
<ul>
|
||
<li>
|
||
Select "MSYS2 64bit" -> "MSYS2 MinGW 64-bit" from the "Start Menu" to open the 64bit shell. </li>
|
||
<li>
|
||
Select "MSYS2 64bit" -> "MSYS2 MinGW 32-bit" from the "Start Menu" to open the 32bit shell. </li>
|
||
</ul>
|
||
|
||
<section class="indent"><!-- H4: Tux Paint Config. -->
|
||
<header>
|
||
<h4>Tux Paint Config.</h4>
|
||
</header>
|
||
<p>
|
||
"Tux Paint Config" is a useful graphical tool for tweaking Tux Paint's behavior. You have to build this component before compiling Tux Paint if you want to have it included in your package. </p>
|
||
<p>
|
||
You can use either (a) a stable tar-ball release, or (b) the developing source tree. <ol type="a">
|
||
<li>
|
||
Using stable tar-ball release: <ul>
|
||
<li>
|
||
<a href="https://sourceforge.net/projects/tuxpaint/files/tuxpaint-config/">Download a source tar-ball</a>
|
||
</li>
|
||
<li>
|
||
Expand the tar-ball and change the directory name so that the final packaging process can find related files. <blockquote>
|
||
<code>
|
||
$ tar zxvf tuxpaint-config-A.B.C.tar.gz<br/>
|
||
$ mv tuxpaint-config-A.B.C tuxpaint-config<br/>
|
||
</code>
|
||
</blockquote>
|
||
</li>
|
||
</ul>
|
||
</li>
|
||
<li>
|
||
Using the developing source tree: <ul>
|
||
<li>
|
||
Fetch the developing source tree from git repository: <blockquote>
|
||
<code>
|
||
$ git clone https://git.code.sf.net/p/tuxpaint/tuxpaint-config tuxpaint-config
|
||
</code>
|
||
</blockquote>
|
||
</li>
|
||
</ul>
|
||
</li>
|
||
</ol>
|
||
</p>
|
||
<p>
|
||
Now you can build Tux Paint Config. as follows: <blockquote>
|
||
<code>
|
||
$ cd tuxpaint-config<br/>
|
||
$ make win32<br/>
|
||
</code>
|
||
</blockquote>
|
||
</p>
|
||
</section><!-- H4: Tux Paint Config. -->
|
||
|
||
<section class="indent"><!-- H4: Tux Paint -->
|
||
<header>
|
||
<h4>Tux Paint</h4>
|
||
</header>
|
||
|
||
<p>
|
||
You can use either (a) a stable tar-ball release, or (b) the developing source tree. <ol type="a">
|
||
<li>
|
||
Using stable tar-ball release: <ul>
|
||
<li>
|
||
<a href="https://sourceforge.net/projects/tuxpaint/files/tuxpaint/">Download a source tar-ball</a>
|
||
</li>
|
||
<li>
|
||
Expand the tar-ball and change the directory name so that the final packaging process can find related files. <blockquote>
|
||
<code>
|
||
$ tar zxvf tuxpaint-A.B.C.tar.gz<br/>
|
||
$ mv tuxpaint-A.B.C tuxpaint<br/>
|
||
</code>
|
||
</blockquote>
|
||
</li>
|
||
</ul>
|
||
</li>
|
||
<li>
|
||
Using the developing source tree: <ul>
|
||
<li>
|
||
Fetch the developing source tree from git repository: <blockquote>
|
||
<code>
|
||
$ git clone https://git.code.sf.net/p/tuxpaint/tuxpaint tuxpaint
|
||
</code>
|
||
</blockquote>
|
||
</li>
|
||
</ul>
|
||
</li>
|
||
</ol>
|
||
</p>
|
||
<p>
|
||
Now you can build Tux Paint as follows: <blockquote>
|
||
<code>
|
||
$ cd tuxpaint<br/>
|
||
$ make bdist-win32<br/>
|
||
</code>
|
||
</blockquote>
|
||
</p>
|
||
</section><!-- H4: Tux Paint -->
|
||
|
||
<p>
|
||
All the files needed for starting Tux Paint (and Tux Paint Config.) are collected in the directory for binary distribution "<code>bdist</code>" directory under "<code>win32</code>". You can start them by double-clicking their executable (<code>.exe</code>) files in the "<code>bdist</code>" directory. </p>
|
||
</section><!-- H3: Tux Paint & Tux Paint Config. -->
|
||
|
||
<section class="indent"><!-- H3: Building the Tux Paint Windows Installer -->
|
||
<header>
|
||
<h3>
|
||
Building the Tux Paint Windows Installer </h3>
|
||
</header>
|
||
|
||
<p>
|
||
<a href="https://jrsoftware.org/isinfo.php">Inno Setup</a> is used to build executable installer for Tux Paint. Therefore you have to install it in the first place. </p>
|
||
<p>
|
||
Inno Setup officially supports translations for only about 20 languages. However, one of the great points of Tux Paint is it supports so many languages. Therefore, the set up script "<code>tuxpaint.iss</code>" to build the installer is written to use much more translations including unofficial one which are available on "<a href="https://jrsoftware.org/files/istrans/">Inno Setup Translations</a>". You have to download translation files (<code>.isl</code>) required and put them in "Languages" directory under the directory in which Inno Setup is installed. </p>
|
||
<p>
|
||
Before building an installer, edit the "<code>tuxpaint.iss</code>" file and enable one of the lines starting with "<code>#define BuildTarget=</code>", depending on the architecture of the installer you want to create. </p>
|
||
<p>
|
||
Then, you can easily build an executable installer by right-clicking on the "<code>tuxpaint.iss</code>" icon in the "<code>win32</code>" directory and selecting "Compile" on the list. It will run for a while, and eventually you will find a "<code>tuxpaint-<i>X.Y.Z</i>-windows-<arch>-installer.exe</code>" file in the same directory. </p>
|
||
</section><!-- H3: Building the Tux Paint Windows Installer -->
|
||
|
||
<section class="indent"><!-- H3: Running the Tux Paint Windows Installer -->
|
||
<header>
|
||
<h3>
|
||
Running the Tux Paint Windows Installer </h3>
|
||
</header>
|
||
|
||
<p>
|
||
Faga dobre clic no executábel do instalador de Tux Paint (ficheiro .EXE) e siga as instrucións. </p>
|
||
|
||
<p>
|
||
First, you will be asked to read the license. (It is the GNU General Public License (GPL), which is also available as "COPYING.txt".) </p>
|
||
|
||
<p>
|
||
Após preguntaráselle se quere instalar accesos directos a Tux Paint no seu menú de inicio de Windows e no escritorio de Windows. (Ámbalas dúas opcións están definidas de xeito predeterminado.) </p>
|
||
|
||
<p>
|
||
A seguir preguntaráselle onde quere instalar Tux Paint. O valor predeterminado debería ser axeitado, sempre que haxa espazo dispoñíbel. Se non, escolla un lugar diferente. </p>
|
||
|
||
<p>
|
||
Neste punto, pode premer en «Instalar» para instalar Tux Paint. </p>
|
||
</section><!-- H3: Running the Tux Paint Windows Installer -->
|
||
|
||
<section class="indent"><!-- H3: Changing the Settings Using the Shortcut -->
|
||
<header>
|
||
<h3>
|
||
Changing the Settings Using the Shortcut </h3>
|
||
</header>
|
||
|
||
<p>
|
||
Para cambiar os axustes do programa, prema co botón dereito no atallo de TuxPaint e seleccione «Propiedades» (na parte inferior). </p>
|
||
|
||
<p>
|
||
Asegúrese de que a lapela «Atallo» está seleccionada na xanela que aparece e examine o campo «Obxectivo:». Debería ver algo así: </p>
|
||
|
||
<blockquote>
|
||
<code>
|
||
"C:\Program Files\TuxPaint\TuxPaint.exe"
|
||
</code>
|
||
</blockquote>
|
||
|
||
<p>
|
||
Agora pode engadir opcións de liña de ordes que se activarán ao facer dobre clic na icona. </p>
|
||
|
||
<p>
|
||
Por exemplo, para que o xogo se execute en modo de pantalla completa, con formas sinxelas (sen opción de rotación) e en francés, engada as opcións (após «TuxPaint.exe»), así: </p>
|
||
|
||
<blockquote>
|
||
<code>
|
||
"C:\Program Files\TuxPaint\TuxPaint.exe" -f -s --lang french
|
||
</code>
|
||
</blockquote>
|
||
|
||
<p>
|
||
(Vexa a documentación principal para obter unha lista completa das opcións dispoñíbeis da liña de ordes.) </p>
|
||
|
||
<p>
|
||
Se se trabuca ou desaparece todo, use <b><code>[Control]</code></b> + <b><code>[Z]</code></b> para desfacer ou só prema a tecla <b><code>[Esc]</code></b> e a caixa pecharase sen facer cambios (a non ser que premera o botón «Aplicar»). </p>
|
||
|
||
<p>
|
||
Cando teña rematado, prema en «Aceptar». </p>
|
||
</section><!-- H3: Changing the Settings Using the Shortcut -->
|
||
|
||
<section class="indent"><!-- H3: If Something Goes Wrong -->
|
||
<header>
|
||
<h3>
|
||
If Something Goes Wrong </h3>
|
||
</header>
|
||
|
||
<p>
|
||
If, when you double-click on the shortcut to run Tux Paint, nothing happens, it is probably because some of these command-line options are wrong. Open an Explorer, and look for a file called "<code>stderr.txt</code>" in your personal saving folder for TuxPaint which is normaly "C:\Users\<i>username</i>\AppData\Roaming\TuxPaint". </p>
|
||
|
||
<p>
|
||
Conterá unha descrición do que estaba mal. Normalmente só se debe a maiúsculas e minúsculas incorrectas (maiúsculas «Z» no canto de minúsculas «z») ou a falta (ou exceso) de «-» (guións). </p>
|
||
</section><!-- H3: If Something Goes Wrong -->
|
||
</section><!-- H2: Windows -->
|
||
|
||
<section class="indent"><!-- H2: Linux/Unux -->
|
||
<header>
|
||
<h2>
|
||
<a name="compiling-linux" id="compiling-linux">
|
||
Linux/Unix </a>
|
||
</h2>
|
||
</header>
|
||
|
||
<section class="indent"><!-- H3: Compiling -->
|
||
<header>
|
||
<h3>
|
||
Compilación: </h3>
|
||
</header>
|
||
|
||
<p class="note">
|
||
<span title="Information">💡</span> <strong>Note:</strong> Tux Paint does not use <code>autoconf</code>/<code>automake</code>, so there is no "<code>./configure</code>" script to run. Compiling should be straight-forward though, assuming everything Tux Paint needs is installed. </p>
|
||
|
||
<p>
|
||
Para compilar o programa dende o código fonte, simplemente execute a seguinte orde dende un indicador do sistema (p. ex.: «$»): </p>
|
||
|
||
<blockquote>
|
||
<code>
|
||
$ make
|
||
</code>
|
||
</blockquote>
|
||
</section><!-- H3: Compiling -->
|
||
|
||
<section class="indent"><!-- H3: Disabling SVG support... -->
|
||
<header>
|
||
<h3>
|
||
Desactivar a compatibilidade de «SVG» (e, polo tanto, as dependencias de «Cairo, libSVG, e svg-cairo»: </h3>
|
||
</header>
|
||
|
||
<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 style="white-space: nowrap;">SVG_LIB= SVG_CFLAGS= NOSVGFLAG=NOSVG</code>»:
|
||
<blockquote>
|
||
<code>
|
||
$ make SVG_LIB= SVG_CFLAGS=
|
||
</code>
|
||
</blockquote>
|
||
</section><!-- H3: Disabling SVG support... -->
|
||
|
||
<section class="indent"><!-- H3: Disabling Pango support... -->
|
||
<header>
|
||
<h3>
|
||
Desactivar a compatibilidade de «Pango» (e, polo tanto, as dependencias de «Pango, Cairo, etc.»: </h3>
|
||
</header>
|
||
|
||
<p class="note">
|
||
<span title="Version variation">📜</span> Antes da versión 0.9.18, Tux Paint utilizaba a biblioteca <code>libSDL_ttf</code> para renderizar texto usando tipos de letra TrueType. Dende o 0.9.18 úsase <code>libSDL_Pango</code>, xa que ten unha mellor compatibilidade coa internacionalización. Non obstante, se quere desactivar o uso de SDL_Pango, pode facelo executando «<code>make</code>» engadindo «<code>SDL_PANGO_LIB=</code>»: </p>
|
||
<blockquote>
|
||
<code>
|
||
$ make SDL_PANGO_LIB=
|
||
</code>
|
||
</blockquote>
|
||
</section><!-- H3: Disabling Pango support... -->
|
||
|
||
<section class="indent"><!-- H3: Disabling Sound at Compile-time -->
|
||
<header>
|
||
<h3>
|
||
Disabling Sound at Compile-time </h3>
|
||
</header>
|
||
|
||
<p>
|
||
Se non te unha tarxeta de son ou prefire construír o programa sen asistencia de son (e polo tanto sen a dependencia <code>SDL_mixer</code>), pode executar «<code>make</code>» con «<code>SDL_MIXER_LIB=</code>» engadido: </p>
|
||
<blockquote>
|
||
<code>
|
||
$ make SDL_MIXER_LIB=
|
||
</code>
|
||
</blockquote>
|
||
</section><!-- H3: Disabling Sound at Compile-time -->
|
||
|
||
<section class="indent"><!-- H3: Other options -->
|
||
<header>
|
||
<h3>
|
||
Other options </h3>
|
||
</header>
|
||
|
||
<p>
|
||
Outras opcións (p. ex.: rutas de instalación) poden ser anuladas; véxaas en «<code>Makefile</code>» para máis detalles. </p>
|
||
</section><!-- H3: Other options -->
|
||
|
||
<section class="indent"><!-- H3: If you get errors -->
|
||
<header>
|
||
<h3>
|
||
If you get errors </h3>
|
||
</header>
|
||
|
||
<p>
|
||
Se recibe algún erro durante o tempo de compilación, asegúrese de ter instaladas as bibliotecas axeitadas (ver máis arriba). Se está a empregar versións empaquetadas das bibliotecas (por exemplo, RPM en RedHat ou DEB en Debian), asegúrese de obter tamén os correspondentes paquetes «<code>-dev</code>» ou «<code>-devel</code>», se non, non poderá compilar Tux Paint (e outros programas) dende o código fonte. </p>
|
||
</section><!-- H3: If you get errors -->
|
||
|
||
<section class="indent"><!-- H3: Installing -->
|
||
<header>
|
||
<h3>
|
||
Installng </h3>
|
||
</header>
|
||
|
||
<p>
|
||
Supoñendo que non se produciron erros graves, agora pode instalar o programa para que os usuarios do sistema poidan executalo. De xeito predeterminado, isto debe facelo o usuario «root» («superusuario»). Cambie a «root» escribindo a orde: </p>
|
||
|
||
<blockquote>
|
||
<code>
|
||
$ su
|
||
</code>
|
||
</blockquote>
|
||
|
||
<p>
|
||
Introduza o contrasinal de «root» no indicador do sistema. Agora debería ser «root» (cun indicador como «#»). Para instalar o programa e os seus ficheiros de datos, escriba: </p>
|
||
|
||
<blockquote>
|
||
<code>
|
||
# make install
|
||
</code>
|
||
</blockquote>
|
||
|
||
<p>
|
||
Finalmente, pode volver ao seu usuario habitual saíndo do modo de superusuario: </p>
|
||
|
||
<blockquote>
|
||
<code>
|
||
# exit
|
||
</code>
|
||
</blockquote>
|
||
|
||
<p>
|
||
Como alternativa, pode simplemente usar a orde «sudo» (po.ex.: en Ubuntu Linux): </p>
|
||
|
||
<blockquote>
|
||
<code>
|
||
$ sudo make install
|
||
</code>
|
||
</blockquote>
|
||
|
||
<p class="note">
|
||
<span title="Information">💡</span> <strong>Note:</strong> By default, "<code>tuxpaint</code>", the executable program, is placed in "<code>/usr/local/bin/</code>". The data files (images, sounds, etc.) are placed in "<code>/usr/local/share/tuxpaint/</code>". </p>
|
||
|
||
<section class="indent"><!-- H4: Changing Where Things Go -->
|
||
<header>
|
||
<h4>
|
||
Cambiar onde van as cousas </h4>
|
||
</header>
|
||
|
||
<p>
|
||
Pode cambiar onde irán as cousas axustando as variábeis de «<code>Makefile</code>» na liña de ordes. «<code>DESTDIR</code>» úsase para colocar a saída nunha área de espera para a creación de paquetes. «<code>PREFIX</code>» é a base de onde van todos os demais ficheiros e, de xeito predeterminado, está estabelecido en «<code>/usr/local</code>». </p>
|
||
|
||
<p>
|
||
Outras variábeis son: </p>
|
||
<dl>
|
||
<dt><code>BIN_PREFIX</code></dt>
|
||
<dd>
|
||
Onde se instalará o binario «<code>tuxpaint</code>». (Estabelécese como «<code>$(PREFIX)/bin</code>»como predeterminado, p. ex.: «<code>/usr/local/bin</code>») </dd>
|
||
|
||
<dt><code>DATA_PREFIX</code></dt>
|
||
<dd>
|
||
Onde irán os ficheiros de datos (son, gráficos, pinceis, selos, tipos de letra) e onde os buscará Tux Paint cando se execute. (Estabelecer en «<code>$(PREFIX)/share/tuxpaint</code>») </dd>
|
||
|
||
<dt><code>DOC_PREFIX</code></dt>
|
||
<dd>
|
||
Onde irán os ficheiros de texto da documentación (o directorio «<code>docs</code>»). (Estabelecer como «<code>$(PREFIX)/share/doc/tuxpaint</code>») </dd>
|
||
|
||
<dt><code>MAN_PREFIX</code></dt>
|
||
<dd>
|
||
Onde irá a páxina do manual de Tux Paint. (Estabelecer como «<code>$(PREFIX)/share/man</code>») </dd>
|
||
|
||
<dt><code>ICON_PREFIX</code> — <code>$(PREFIX)/share/pixmaps</code></dt>
|
||
<dt><code>X11_ICON_PREFIX</code> — <code>$(PREFIX)/X11R6/include/X11/pixmaps</code></dt>
|
||
<dt><code>GNOME_PREFIX</code> — <code>$(PREFIX)/share/gnome/apps/Graphics</code></dt>
|
||
<dt><code>KDE_PREFIX</code> — <code>$(PREFIX)/share/applnk/Graphics</code></dt>
|
||
<dd>
|
||
Onde irán as iconas e os lanzadores (para GNOME e KDE). </dd>
|
||
|
||
<dt><code>LOCALE_PREFIX</code></dt>
|
||
<dd>
|
||
Onde irán os ficheiros de tradución para Tux Paint e onde os buscará Tux Paint. (Estabelécese en «<code>$(PREFIX)/share/locale/</code>») (A localización final dun ficheiro de tradución estará no directorio da configuración local (por exemplo, «<code>es</code>» para o español), dentro do subdirectorio «<code>LC_MESSAGES</code>»). </dd>
|
||
</dl>
|
||
|
||
<p class="note">
|
||
<span title="Information">💡</span> <strong>Note:</strong> This list is out of date. See "<code>Makefile</code>" and "<code>Makefile-i18n</code>" for a complete list. </p>
|
||
</section class="indent"><!-- H4: Changing Where Things Go -->
|
||
</section><!-- H3: Installing -->
|
||
</section><!-- H2: Linux/Unux -->
|
||
|
||
<section class="indent"><!-- H2: macOS -->
|
||
<header>
|
||
<h2>
|
||
<a name="compiling-macos" id="compiling-macos">
|
||
macOS </a>
|
||
</h2>
|
||
<p style="font-size: small;">
|
||
<em>
|
||
5 de Xuño de 2022 Mark Kim <<a href="mailto:markuskimius@gmail.com">markuskimius@gmail.com</a>>
|
||
</em>
|
||
</p>
|
||
</header>
|
||
|
||
<p>
|
||
Starting with Tux Paint 0.9.23, Tux Paint for macOS is built as though it were a Linux application. </p>
|
||
|
||
<section class="indent"><!-- H3: Prerequisites -->
|
||
<header>
|
||
<h3>
|
||
Prerequisites </h3>
|
||
</header>
|
||
|
||
<p>
|
||
Although Tux Paint is built without the Xcode IDE, Xcode itself is still required to build Tux Paint. <a href="https://developer.apple.com/xcode/ide/">Download it from the App Store</a>, and launch it once to accept its license agreements. You may also need to install the Xcode command line tools using the command: <blockquote>
|
||
<code>
|
||
$ xcode-select --install
|
||
</code>
|
||
</blockquote>
|
||
</p>
|
||
|
||
<p>
|
||
Building Tux Paint also requires various libraries. We install them from MacPorts where possible, source code otherwise. Install MacPorts to the default <code>/opt/local</code> path according to the instructions found on their website: <a href="https://www.macports.org/">https://www.macports.org/</a> <ul>
|
||
<li><code>ImageMagick</code></li>
|
||
<li><code>cairo</code></li>
|
||
<li><code>fribidi</code></li>
|
||
<li><code>lbzip2</code></li>
|
||
<li><code>libimagequant</code><sup>*</sup></li>
|
||
<li><code>libpaper</code></li>
|
||
<li><code>libpng</code></li>
|
||
<li><code>librsvg</code></li>
|
||
<li><code>libsdl2</code></li>
|
||
<li><code>libsdl2_image</code></li>
|
||
<li><code>libsdl2_mixer</code></li>
|
||
<li><code>libsdl2_pango</code><sup>*</sup></li>
|
||
<li><code>libsdl2_ttf</code></li>
|
||
<li><code>libsdl2_gfx</code></li>
|
||
<li><code>pkgconfig</code></li>
|
||
<li><code>zlib</code></li>
|
||
</ul>
|
||
... but you should install any package that is required by the latest version of Tux Paint.<br/>
|
||
<br/>
|
||
<sup>*</sup> Not available from MacPorts as of this writing, see below. </p>
|
||
|
||
<section class="indent"><!-- H4: libimagequant -->
|
||
<header>
|
||
<h4>
|
||
libimagequant
|
||
</h4>
|
||
</header>
|
||
|
||
<p>
|
||
<code>libimagequant</code> is not available from MacPorts as of this writing. It can be installed from the source code as follows. It should be installed to <code>/opt/local</code> (same as MacPorts) for the library to be included in <code>TuxPaint.dmg</code>. <blockquote>
|
||
<code>
|
||
$ sudo port install rust cargo<br/>
|
||
$ git clone https://github.com/ImageOptim/libimagequant.git<br/>
|
||
$ cd libimagequant/imagequant-sys<br/>
|
||
$ cargo build --release # Must use cargo from MacPorts<br/>
|
||
$ sudo make PREFIX=/opt/local install
|
||
</code>
|
||
</blockquote>
|
||
</p>
|
||
</section><!-- H4: libimagequant -->
|
||
|
||
<section class="indent"><!-- H4: sdl2_pango -->
|
||
<header>
|
||
<h4>
|
||
sdl2_pango
|
||
</h4>
|
||
</header>
|
||
|
||
<p>
|
||
<code>sdl2_pango</code> is not available from MacPorts as of this writing. It can be installed from the source code as follows. It should be installed to <code>/opt/local</code> (same as MacPorts) for the library to be included in <code>TuxPaint.dmg</code>. <blockquote>
|
||
<code>
|
||
$ git clone https://github.com/markuskimius/SDL2_Pango.git<br/>
|
||
$ cd SDL2_Pango<br/>
|
||
$ ./configure --prefix=/opt/local && make && sudo make install
|
||
</code>
|
||
</blockquote>
|
||
</p>
|
||
</section><!-- H4: sdl2_pango -->
|
||
|
||
<p>
|
||
<strong>WARNING:</strong> Having any UNIX-like toolset installed on your Mac besides MacPorts and Xcode, such as Fink or Brew, will prevent your app bundle from being portable. Be sure Fink and Brew are not accessible from your build environment. </p>
|
||
</section><!-- H3: Prerequisites -->
|
||
|
||
<section class="indent"><!-- H3: How to Build -->
|
||
<header>
|
||
<h3>
|
||
How to Build </h3>
|
||
</header>
|
||
|
||
<p>
|
||
Simply, run: <blockquote>
|
||
<code>
|
||
% make<br/>
|
||
% 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>. To create the DMG file for distribution, use 'make TuxPaint.dmg'. </p>
|
||
|
||
<p>
|
||
Additional steps may be required when building for the Apple Silicon. See "Building for Apple Silicon" below. </p>
|
||
</section><!-- H3: How to Build -->
|
||
|
||
<section class="indent"><!-- H3: Known Issues -->
|
||
<header>
|
||
<h3>
|
||
Known Issues </h3>
|
||
</header>
|
||
|
||
<ul>
|
||
<li>
|
||
A macOS binary built on a specific version of macOS only runs on that version of macOS or later. To ensure Tux Paint can run on the oldest version of macOS possible, build it on the oldest version of macOS available. As of this writing we know Tux Paint cannot be built to run on macOS 10.7 or earlier.<br/>
|
||
<br/>
|
||
See "Old Versions of macOS" below for best-effort instructions on how to obtain, install, and build Tux Paint on an old version of macOS.<br/>
|
||
<br/>
|
||
Alternatively, Tux Paint and all of its library dependencies may be compiled with appropriate options to be runnable on older versions of macOS. These options are already set on Tux Paint, so only its dependencies (from MacPorts) need to be recompiled. See "Recompiling MacPorts" below for the instructions. </li>
|
||
</ul>
|
||
</section><!-- H3: Known Issues -->
|
||
|
||
<section class="indent"><!-- H3: Old Versions of macOS -->
|
||
<header>
|
||
<h3>
|
||
Old Versions of macOS </h3>
|
||
</header>
|
||
|
||
<p>
|
||
Some old versions of macOS can be downloaded from Apple's support page: <a href="https://support.apple.com/en-us/HT211683">https://support.apple.com/en-us/HT211683</a> </p>
|
||
|
||
<p>
|
||
macOS for Intel CPU does allow dual booting of multiple versions of the OS, but it's safer and easier to install the old macOS onto a flash drive. Wherever you're installing it, the target drive's partitioniong scheme and partition type must match what the old macOS expects, so use the Disk Utility to partition and format the flash drive accordingly. </p>
|
||
|
||
<p>
|
||
Dual booting multiple versions of macOS for Apple Silicon has been so far unsuccessful. Instead of installing an older version of macOS for Apple Silicon to build Tux Paint to run on the old version of macOS for Apple Silicon, use the instructions found in the "Recompiling MacPorts" section to build Tux Paint to run on older versions of macOS for Apple Silicon. </p>
|
||
|
||
<p>
|
||
As of this writing, the oldest version of macOS available on Apple's support site is Yosemite 10.10, which expects "GPT (GUID Partition Table)" partitioning scheme instead of the older MBR scheme, and "Mac OS Extended (Journaled)" as the partition type instead of the newer APFS partition type. </p>
|
||
|
||
<p>
|
||
Upon launching the installer, if you get a popup about macOS being too old or new to be installed, a bootable installer can be created using the instructions found here: <a href="https://support.apple.com/en-mide/HT201372">https://support.apple.com/en-mide/HT201372</a> </p>
|
||
|
||
<p>
|
||
Once the old macOS is installed, you may find the Xcode on the App Store is too new to run on the version of the old macOS. Old versions of Xcode can be downloaded from Apple's Developer site in an area accessible with free registration: <a href="https://developer.apple.com/download/more/">https://developer.apple.com/download/more/</a> </p>
|
||
|
||
<p>
|
||
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 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>
|
||
</section><!-- H3: Old Versions of macOS -->
|
||
|
||
<section class="indent"><!-- H3: Recompiling MacPorts -->
|
||
<header>
|
||
<h3>
|
||
Recompiling MacPorts </h3>
|
||
</header>
|
||
|
||
<p>
|
||
To recompile MacPorts to be usable on older versions of macOS, set the following options in <code style="white-space: nowrap;">/opt/local/etc/macports/macports.conf</code>: <blockquote>
|
||
<code>
|
||
buildfromsource always<br/>
|
||
macosx_deployment_target 10.10
|
||
</code>
|
||
</blockquote>
|
||
</p>
|
||
|
||
<p>
|
||
Then uninstall all MacPorts packages: <blockquote>
|
||
<code>
|
||
$ sudo port -fp uninstall installed
|
||
</code>
|
||
</blockquote>
|
||
</p>
|
||
|
||
<p>
|
||
Then reinstall all MacPorts packages needed by Tux Paint. Also rebuild libimagequant using the updated Cargo package from MacPorts. </p>
|
||
|
||
<p>
|
||
As of this writing, all libraries Tux Paint requires from MacPorts can be recompiled in this manner to run on macOS 10.10 Yosemite and later on Intel CPUs, and macOS 11.0 Big Sur and later on Apple Silicon. Unfortunately, although MacPorts has the option to enable the building of universal libraries, several libraries Tux Paint require cannot be built as universal libraries so they can only be built to run natively on the hardware on which they were built. See "Building a Universal Binary" below for instructions on how to build Tux Paint as a Universal Binary. </p>
|
||
</section><!-- H3: Recompiling MacPorts -->
|
||
|
||
<section class="indent"><!-- H3: Building for Apple Silicon -->
|
||
<header>
|
||
<h3>
|
||
Building for Apple Silicon </h3>
|
||
</header>
|
||
|
||
<p>macOS for Apple Silicon requires all native Apple Silicon applications be signed, even if it is signed "ad-hoc" (anonymously). Because of this, compilers that produce native Apple Silicon applications sign all produced binaries and libraries as a part of the compilation process.<sup>*</sup> However, the Tux Paint compilation process modifies the libraries to be modular (using <code>install_name_tool</code>) so they can be added into the application bundle, which has the unfortunate side effect of breaking the signature. This can be addressed by signing the application bundle ad-hoc (example below) or using your own Apple Developer Identity if you have one. The DMG file, if needed, must be created after signing the App Bundle so the DMG file is created with signed App Bundle: <blockquote>
|
||
<code>
|
||
$ codesign -s - TuxPaint.app<br/>
|
||
$ make TuxPaint.dmg
|
||
</code>
|
||
</blockquote>
|
||
<sup>*</sup> For more information on the code signing requirements on the Apple Silicon, see <a href="https://developer.apple.com/documentation/macos-release-notes/macos-big-sur-11_0_1-universal-apps-release-notes#:~:text=New%20in%20macOS,pass%20through%20Gatekeeper">https://developer.apple.com/documentation/macos-release-notes/macos-big-sur-11_0_1-universal-apps-release-notes#:~:text=New%20in%20macOS,pass%20through%20Gatekeeper</a>. </p>
|
||
<p>If you get an error that the application bundle is already signed, remove it before signing:: <blockquote>
|
||
<code>
|
||
$ codesign --remove-signature TuxPaint.app
|
||
</code>
|
||
</blockquote>
|
||
</p>
|
||
<p>If you plan to combine the Apple Silicon bundle with the Intel CPU bundle to produce the Universal bundle, the code signing must be done after they are combined. See "Building a Universal Binary" below. </p>
|
||
</section><!-- H3: Building for Apple Silicon -->
|
||
|
||
<section class="indent"><!-- H3: Building a Universal Binary -->
|
||
<header>
|
||
<h3>
|
||
Building a Universal Binary </h3>
|
||
</header>
|
||
|
||
<p>
|
||
To build Tux Paint as a Universal Binary, compile Tux Paint for the Intel CPU and the Apple Silicon separately first. Then rename the app bundle for the Intel CPU to TuxPaint-x86_64.app, and the bundle for the Apple Silicon to TuxPaint-arm64.app, copy the app bundle from the Intel machine to the Apple Silicon machine, then use the provided <code>build-universal.sh</code> script to combine the two application bundles as below. The produced bundle must be signed (see "Building for Apple Silicon" above for more details). The DMG file, if required, must be built after the signing: <blockquote>
|
||
<code>
|
||
$ macos/build-universal.sh<br/>
|
||
$ codesign -s - TuxPaint.app <br/>
|
||
$ make TuxPaint.dmg
|
||
</code>
|
||
</blockquote>
|
||
</p>
|
||
</section><!-- H3: Building a Universal Binary -->
|
||
|
||
</section><!-- H2: macOS -->
|
||
|
||
<section class="indent"><!-- H2: Android -->
|
||
<header>
|
||
<h2>
|
||
<a name="compiling-macos" id="compiling-android">
|
||
Android </a>
|
||
</h2>
|
||
<p style="font-size: small;">
|
||
<em>
|
||
29 de Marzo de 2023 Pere Pujal i Carabantes <<a href="mailto:perepujal@gmail.com">perepujal@gmail.com</a>>
|
||
(Edited by Bill Kendrick)
|
||
</em>
|
||
</p>
|
||
</header>
|
||
|
||
<p>
|
||
As of March 2023, the Android build of Tux Paint is maintained in a separate code repository at GitHub: <a href="https://github.com/tux4kids/Tuxpaint-Android">https://github.com/tux4kids/Tuxpaint-Android</a>. Detailed instructions are there; this acts as an overview. </p>
|
||
|
||
<section class="indent"><!-- H3: Prerequisites -->
|
||
<header>
|
||
<h3>
|
||
Prerequisites </h3>
|
||
</header>
|
||
|
||
<p>You will need recent versions of: <ul>
|
||
<li>
|
||
<a href="https://gradle.org/">Gradle</a> — build automation tool </li>
|
||
<li>
|
||
<a href="https://developer.android.com/studio">Android Studio (Software Development Kit (SDK))</a> — to support Android app development (Java) </li>
|
||
<li>
|
||
<a href="https://developer.android.com/ndk">Android Native Development Kit (NDK)</a> — to support native development in C/C++ </li>
|
||
</ul>
|
||
</p>
|
||
|
||
<p>
|
||
To compile the latest Tux Paint, one has to sync the main SourceForge project's <code>tuxpaint</code> Git repository with the GitHub project's <code>TuxPaint-Android</code> Git repository. (Pere uses a shell script that backs up the <code>app/src/main/jni/tuxpaint</code> directory in the <code>Tuxpaint-Android</code> GitHub repo and makes a build of SourceForge's <code>tuxpaint</code> to generate translations and other things that are not autogenerated in the Android builds, and then copies the SourceForge <code>tuxpaint</code> back to <code>Tuxpaint-Android</code>.) (FIXME: It should be checked-in somewhere. For now, see <a href="https://sourceforge.net/p/tuxpaint/feature-requests/224/">https://sourceforge.net/p/tuxpaint/feature-requests/224/</a>) </p>
|
||
|
||
<p>
|
||
For it to run you need the <code>tuxpaint</code> and <code>Tuxpaint-Android</code> sources one next to one another, and the script in the directory containing both. </p>
|
||
|
||
<p>
|
||
Fill the <code>app/src/main/assets</code> directory by running <code>cd app/src/main/jni/tuxpaint && ./mkzip_assets.sh</code> </p>
|
||
</section><!-- H3: Prerequisites -->
|
||
|
||
<section class="indent"><!-- H3: Building -->
|
||
<header>
|
||
<h3>
|
||
Building </h3>
|
||
</header>
|
||
|
||
<p>
|
||
The Gradle build generates some variants: PlayStore, debugPlayStore, offPlayStore and debugoffPlayStore. You must sign the non-debug ones to be able to install them. (FIXME: Link to info on how to sign.) (Note: "playStore" ones are intended to be uploaded to Google Play; this is currently managed by Terrence Sheflin —March 2023. "offPlayStore" is the flavor that we distribute as APK files on the Tux Paint website and SourceForge file hosting, and is the variant built by the F-Droid app. repository.) </p>
|
||
|
||
<p>
|
||
To trigger a build from F-droid, it suffices to tag a commit and push it to GitHub. That doesn't guarantee the build will succeed though, so Pere usually runs a local F-droid server to test the build and eventually adapt the F-droid's build receipt before pushing the tag to GitHub. </p>
|
||
|
||
<p>
|
||
The builds Pere distributes are all made with that local F-droid server. It has the advantage of packing the sources and logs, and signing the APK. Most importantly, it uses the same tools F-Droid will use to build Tux Paint, so you can detect problems beforehand. </p>
|
||
|
||
<p>
|
||
The receipt Pere uses for F-Droid builds is in the metadata dir of <a href="https://gitlab.com/fdroid/fdroiddata">https://gitlab.com/fdroid/fdroiddata</a>. The F-Droid server code is at <a href="https://gitlab.com/fdroid/fdroidserver">https://gitlab.com/fdroid/fdroidserver</a>. To generate the server you will need 1GB free on disk. Run the <code>makebuildserver</code> tool they provide, then, from the root of <code>fdroiddata</code>, run <code>../fdroidserver/fdroid build --server org.tuxpaint:NNNN</code> (NNNN = version, e.g. 9288) </p>
|
||
|
||
</section><!-- H3: Building -->
|
||
|
||
</section><!-- H2: Android -->
|
||
|
||
</section><!-- H1: Compiling and Installation -->
|
||
|
||
<section class="outer indent"><!-- H1: Debugging -->
|
||
<header>
|
||
<h1>
|
||
<a name="debugging" id="debugging">
|
||
Debugging </a>
|
||
</h1>
|
||
</header>
|
||
|
||
<p class="note">
|
||
<span title="Configuration option">⚙</span> Debugging output — 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 — 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. </p>
|
||
</section><!-- H1: Debugging -->
|
||
|
||
<section class="outer indent"><!-- H1: Uninstalling Tux Paint -->
|
||
<header>
|
||
<h1>
|
||
<a name="uninstalling" id="uninstalling">
|
||
Uninstalling Tux Paint </a>
|
||
</h1>
|
||
</header>
|
||
|
||
<section class="indent"><!-- H2: Windows -->
|
||
<header>
|
||
<h2>
|
||
<a name="uninstalling-windows" id="uninstalling-windows">
|
||
Windows </a>
|
||
</h2>
|
||
</header>
|
||
|
||
<section class="indent"><!-- H3: Using the Uninstaller -->
|
||
<header>
|
||
<h3>
|
||
Uso do desinstalador </h3>
|
||
</header>
|
||
|
||
<p>
|
||
Se instalou os atallos do menú Inicio (o predeterminado), vaia ao cartafol TuxPaint e seleccione «Desinstalar». Amosarase unha caixa que confirmará que está a piques de desinstalar Tux Paint e, se está seguro de que quere eliminar permanentemente Tux Paint, prema no botón «Desinstalar». </p>
|
||
|
||
<p>
|
||
Cando remate, prema no botón pechar. </p>
|
||
</section><!-- H3: Using the Uninstaller -->
|
||
|
||
<section class="indent"><!-- H3: Using the Control Panel -->
|
||
<header>
|
||
<h3>
|
||
Usar o Panel de control </h3>
|
||
</header>
|
||
|
||
<p>
|
||
Tamén é posíbel usar a entrada «TuxPaint (só eliminar)« na sección Engadir/Eliminar programas do Panel de control. </p>
|
||
</section><!-- H3: Using the Control Panel -->
|
||
</section><!-- H2: Windows -->
|
||
|
||
<section class="indent"><!-- H2: macOS -->
|
||
<header>
|
||
<h2>
|
||
<a name="uninstalling-macos" id="uninstalling-macos">
|
||
macOS </a>
|
||
</h2>
|
||
</header>
|
||
|
||
<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>
|
||
</section><!-- H2: macOS -->
|
||
|
||
<section class="indent"><!-- H2: Linux -->
|
||
<header>
|
||
<h2>
|
||
<a name="uninstalling-linux" id="uninstalling-linux">
|
||
Linux </a>
|
||
</h2>
|
||
</header>
|
||
|
||
<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>
|
||
</section><!-- H2: Linux -->
|
||
</section><!-- H1: Uninstalling Tux Paint -->
|
||
</body>
|
||
</html>
|