Add macOS compile/install instructions to INSTALL
This commit is contained in:
Bill Kendrick
parent
6407bec2a2
commit
987b2c1cc3
12 changed files with 1643 additions and 149 deletions
|
|
@ -32,8 +32,8 @@ $Id$
|
|||
("Options Documentation", "FAQ", "Installation Documentation",
|
||||
and "Advanced Stamps 'How-To'").
|
||||
|
||||
* Moved Windows compilation instructions into main
|
||||
"Installation Documentation".
|
||||
* Moved Windows and macOS compilation instructions into main
|
||||
"Installation Documentation" (docs/.../INSTALL...).
|
||||
|
||||
|
||||
2021.June.28 (0.9.26)
|
||||
|
|
|
|||
|
|
@ -18,6 +18,7 @@
|
|||
| * Compiling and Installation |
|
||||
| * Windows Users |
|
||||
| * Linux/Unix Users |
|
||||
| * macOS Users |
|
||||
| * Debugging |
|
||||
| * Uninstalling Tux Paint |
|
||||
| * Windows |
|
||||
|
|
@ -177,6 +178,8 @@ Compiling and Installation
|
|||
to the "MinGW 32bit (i686) toolchains" section if you need only a
|
||||
32bit build environment.
|
||||
|
||||
-------------------------------------------------------
|
||||
|
||||
MinGW 64bit (x86_64) toolchains
|
||||
|
||||
Within the MSYS2 shell, run the following command to install basic
|
||||
|
|
@ -247,6 +250,8 @@ Compiling and Installation
|
|||
to the "ImageMagick" section if you need only a 64bit build
|
||||
environment.
|
||||
|
||||
-------------------------------------------------------
|
||||
|
||||
MinGW 32bit (i686) toolchains
|
||||
|
||||
Within the MSYS2 shell, run the following command to install basic
|
||||
|
|
@ -313,6 +318,8 @@ Compiling and Installation
|
|||
$ cd SDL-1.2.15
|
||||
$ ./configure --prefix=/mingw32 && make && make install
|
||||
|
||||
-------------------------------------------------------
|
||||
|
||||
ImageMagick
|
||||
|
||||
ImageMagick is a compilation of command line tools to create, edit,
|
||||
|
|
@ -336,6 +343,8 @@ Compiling and Installation
|
|||
You can make this permanent by adding the above to your the BASH
|
||||
shell configuration file, "~/.bash_profile".
|
||||
|
||||
-------------------------------------------------------
|
||||
|
||||
Tux Paint
|
||||
|
||||
You can compile 64bit binaries using MSYS2 64bit shell, and 32bit
|
||||
|
|
@ -362,6 +371,8 @@ Compiling and Installation
|
|||
directory under "win32". You can start them by double-clicking their
|
||||
executable (.exe) files in the "bdist" directory.
|
||||
|
||||
-------------------------------------------------------
|
||||
|
||||
Building the Tux Paint Windows Installer:
|
||||
|
||||
Inno Setup is used to build executable installer for Tux Paint.
|
||||
|
|
@ -373,6 +384,8 @@ Compiling and Installation
|
|||
will find a "tuxpaint-X.Y.Z-win32-installer.exe" file in the same
|
||||
directory.
|
||||
|
||||
-------------------------------------------------------
|
||||
|
||||
Running the Tux Paint Windows Installer:
|
||||
|
||||
Double-click the Tux Paint installer executable (.EXE file) and
|
||||
|
|
@ -392,6 +405,8 @@ Compiling and Installation
|
|||
|
||||
At this point, you can click 'Install' to install Tux Paint!
|
||||
|
||||
-------------------------------------------------------
|
||||
|
||||
Changing the Settings Using the Shortcut:
|
||||
|
||||
To change program settings, right-click on the TuxPaint shortcut and
|
||||
|
|
@ -420,6 +435,8 @@ Compiling and Installation
|
|||
|
||||
When you have finished, click "OK."
|
||||
|
||||
-------------------------------------------------------
|
||||
|
||||
If Something Goes Wrong:
|
||||
|
||||
If, when you double-click on the shortcut to run Tux Paint, nothing
|
||||
|
|
@ -431,6 +448,8 @@ Compiling and Installation
|
|||
just be due to incorrect character-case (capital 'Z' instead of
|
||||
lowercase 'z') or a missing (or extra) '-' (dash).
|
||||
|
||||
----------------------------------------------------------------------
|
||||
|
||||
Linux/Unix Users
|
||||
|
||||
Compiling:
|
||||
|
|
@ -444,6 +463,8 @@ Compiling and Installation
|
|||
|
||||
$ make
|
||||
|
||||
-------------------------------------------------------
|
||||
|
||||
Disabling SVG support (and hence Cairo, libSVG, and svg-cairo dependencies):
|
||||
|
||||
To disable SVG support (e.g., if your system is not currently
|
||||
|
|
@ -453,6 +474,8 @@ Compiling and Installation
|
|||
|
||||
$ make SVG_LIB= SVG_CFLAGS=
|
||||
|
||||
-------------------------------------------------------
|
||||
|
||||
Disabling Pango support (and hence Pango, Cairo, etc. dependencies):
|
||||
|
||||
Prior to version 0.9.18, Tux Paint used the libSDL_ttf library for
|
||||
|
|
@ -463,6 +486,8 @@ Compiling and Installation
|
|||
|
||||
$ make SDL_PANGO_LIB=
|
||||
|
||||
-------------------------------------------------------
|
||||
|
||||
Disabling Sound at Compile-time:
|
||||
|
||||
If you don't have a sound card, or would prefer to build the program
|
||||
|
|
@ -471,11 +496,15 @@ Compiling and Installation
|
|||
|
||||
$ make SDL_MIXER_LIB=
|
||||
|
||||
-------------------------------------------------------
|
||||
|
||||
Other options:
|
||||
|
||||
Various other options (e.g., installation paths) may be overridden;
|
||||
see them in "Makefile" for further details.
|
||||
|
||||
-------------------------------------------------------
|
||||
|
||||
If you get errors:
|
||||
|
||||
If you receive any errors during compile-time, make sure you have
|
||||
|
|
@ -485,6 +514,8 @@ Compiling and Installation
|
|||
packages as well, otherwise you won't be able to compile Tux Paint
|
||||
(and other programs) from source!
|
||||
|
||||
-------------------------------------------------------
|
||||
|
||||
Installng:
|
||||
|
||||
Assuming no fatal errors occured, you can now install the program so
|
||||
|
|
@ -562,6 +593,138 @@ Compiling and Installation
|
|||
|
||||
----------------------------------------------------------------------
|
||||
|
||||
macOS Users
|
||||
|
||||
September 21, 2021 Mark K. Kim <markuskimius@gmail.com>
|
||||
|
||||
Tux Paint 0.9.22 and earlier required building Tux Paint from the
|
||||
Xcode IDE. Starting with 0.9.23, however, Tux Paint for macOS is built
|
||||
as though it were a Linux application.
|
||||
|
||||
Prerequisites
|
||||
|
||||
Although Tux Paint is built without the Xcode IDE, Xcode itself is
|
||||
still required to build Tux Paint. Download it from the App Store,
|
||||
and launch it once to accept its license agreements. You may also
|
||||
need to install the Xcode command line tools using the command:
|
||||
|
||||
xcode-select --install
|
||||
|
||||
Building Tux Paint also requires various libraries. We install them
|
||||
from MacPorts where possible, source code otherwise. Install
|
||||
MacPorts to the default /opt/local path according to the
|
||||
instructions found on their website: https://www.macports.org/
|
||||
* ImageMagick
|
||||
* cairo
|
||||
* fribidi
|
||||
* lbzip2
|
||||
* libimagequant^*
|
||||
* libpaper
|
||||
* libpng
|
||||
* librsvg
|
||||
* libsdl
|
||||
* libsdl_image
|
||||
* libsdl_mixer
|
||||
* libsdl_pango
|
||||
* libsdl_ttf
|
||||
* pkgconfig
|
||||
* zlib
|
||||
... but you should install any package that is required by the
|
||||
latest version of Tux Paint.
|
||||
|
||||
^* Not available from MacPorts as of this writing, see below.
|
||||
|
||||
libimagequant
|
||||
|
||||
libimagequant is not available from MacPorts as of this writing.
|
||||
It can be installed from the source code as follows. It should be
|
||||
installed to /opt/local (same as MacPorts) for the library to be
|
||||
included in TuxPaint.dmg.
|
||||
|
||||
$ git clone https://github.com/ImageOptim/libimagequant.git
|
||||
$ cd libimagequant
|
||||
$ ./configure --prefix=/opt/local
|
||||
$ make
|
||||
$ sudo make install
|
||||
|
||||
WARNING: 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.
|
||||
|
||||
-------------------------------------------------------
|
||||
|
||||
How to Build
|
||||
|
||||
Simply, run:
|
||||
|
||||
% make
|
||||
% make install
|
||||
|
||||
... to create the TuxPaint.app application bundle that can be run
|
||||
in-place or copied to /Applications. It also creates TuxPaint.dmg
|
||||
for distribution.
|
||||
|
||||
-------------------------------------------------------
|
||||
|
||||
Known Issues
|
||||
|
||||
* 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.
|
||||
|
||||
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.
|
||||
|
||||
-------------------------------------------------------
|
||||
|
||||
Old Versions of macOS
|
||||
|
||||
Some old versions of macOS can be downloaded from Apple's support
|
||||
page: https://support.apple.com/en-us/HT211683
|
||||
|
||||
macOS 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.
|
||||
|
||||
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.
|
||||
|
||||
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:
|
||||
https://support.apple.com/en-mide/HT201372
|
||||
|
||||
It has been found that macOS can be installed onto the bootable
|
||||
media itself, so you can make the flash drive into a bootable
|
||||
installer then install the old macOS onto the same flash drive.
|
||||
|
||||
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:
|
||||
https://developer.apple.com/download/more/
|
||||
|
||||
The list of macOS versions and the last version of Xcode compatible
|
||||
with them are laid out nicely on the Wikipedia page on Xcode:
|
||||
https://en.wikipedia.org/wiki/Xcode#Version_comparison_table
|
||||
|
||||
And because Xcode is being installed manually, you can skip the step
|
||||
to install the Xcode command line tools (do not run "xcode-select
|
||||
--install") but otherwise build Tux Paint using the same steps
|
||||
described in the earlier part of this document.
|
||||
|
||||
----------------------------------------------------------------------
|
||||
|
||||
Debugging
|
||||
|
||||
Debugging (to "STDOUT", e.g. to the terminal, or to a "stdout.txt" file,
|
||||
|
|
@ -589,6 +752,8 @@ Uninstalling Tux Paint
|
|||
It is also possible to use the entry "TuxPaint (remove only)" in the
|
||||
Control Panel Add/Remove programs section.
|
||||
|
||||
----------------------------------------------------------------------
|
||||
|
||||
Linux
|
||||
|
||||
Within the Tux Paint source directory (where you compiled Tux Paint),
|
||||
|
|
|
|||
|
|
@ -63,6 +63,9 @@
|
|||
<li>
|
||||
<a href="#compiling-linux">Linux/Unix Users</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href="#compiling-macos">macOS Users</a>
|
||||
</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
|
|
@ -271,6 +274,7 @@
|
|||
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>
|
||||
|
||||
<hr size="1" noshade width="75%" />
|
||||
<h4>
|
||||
<a name="64bit" id="64bit">
|
||||
MinGW 64bit (x86_64) toolchains </a>
|
||||
|
|
@ -368,6 +372,7 @@
|
|||
<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>
|
||||
<hr size="1" noshade width="75%" />
|
||||
<h4>
|
||||
<a name="32bit" id="32bit">
|
||||
MinGW 32bit (i686) toolchains </a>
|
||||
|
|
@ -462,6 +467,8 @@
|
|||
</blockquote>
|
||||
|
||||
|
||||
<hr size="1" noshade width="75%" />
|
||||
|
||||
<h4>
|
||||
<a name="imagemagick" id="imagemagick">ImageMagick</a>
|
||||
</h4>
|
||||
|
|
@ -484,6 +491,8 @@
|
|||
You can make this permanent by adding the above to your the BASH shell configuration file, "<code>~/.bash_profile</code>". </p>
|
||||
</blockquote>
|
||||
|
||||
<hr size="1" noshade width="75%" />
|
||||
|
||||
<h4>Tux Paint</h4>
|
||||
|
||||
<blockquote>
|
||||
|
|
@ -508,6 +517,8 @@
|
|||
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>
|
||||
</blockquote>
|
||||
|
||||
<hr size="1" noshade width="75%" />
|
||||
|
||||
<h4>Building the Tux Paint Windows Installer:</h4>
|
||||
<blockquote>
|
||||
|
||||
|
|
@ -519,6 +530,8 @@
|
|||
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>-win32-installer.exe</code>" file in the same directory. </p>
|
||||
</blockquote>
|
||||
|
||||
<hr size="1" noshade width="75%" />
|
||||
|
||||
<h4>Running the Tux Paint Windows Installer:</h4>
|
||||
<blockquote>
|
||||
<p>
|
||||
|
|
@ -536,6 +549,8 @@
|
|||
At this point, you can click 'Install' to install Tux Paint! </p>
|
||||
</blockquote>
|
||||
|
||||
<hr size="1" noshade width="75%" />
|
||||
|
||||
<h4>Changing the Settings Using the Shortcut:</h4>
|
||||
<blockquote>
|
||||
<p>
|
||||
|
|
@ -572,6 +587,8 @@
|
|||
When you have finished, click "OK." </p>
|
||||
</blockquote>
|
||||
|
||||
<hr size="1" noshade width="75%" />
|
||||
|
||||
<h4>If Something Goes Wrong:</h4>
|
||||
<blockquote>
|
||||
<p>
|
||||
|
|
@ -582,6 +599,8 @@
|
|||
</blockquote>
|
||||
</blockquote>
|
||||
|
||||
<hr size="1" noshade />
|
||||
|
||||
<h3>
|
||||
<a name="compiling-linux" id="compiling-linux">
|
||||
Linux/Unix Users </a>
|
||||
|
|
@ -602,6 +621,8 @@
|
|||
</blockquote>
|
||||
</blockquote>
|
||||
|
||||
<hr size="1" noshade width="75%" />
|
||||
|
||||
<h4>
|
||||
Disabling SVG support (and hence Cairo, libSVG, and svg-cairo dependencies): </h4>
|
||||
<blockquote>
|
||||
|
|
@ -614,6 +635,8 @@
|
|||
</blockquote>
|
||||
</blockquote>
|
||||
|
||||
<hr size="1" noshade width="75%" />
|
||||
|
||||
<h4>
|
||||
Disabling Pango support (and hence Pango, Cairo, etc. dependencies): </h4>
|
||||
<blockquote>
|
||||
|
|
@ -626,6 +649,8 @@
|
|||
</blockquote>
|
||||
</blockquote>
|
||||
|
||||
<hr size="1" noshade width="75%" />
|
||||
|
||||
<h4>Disabling Sound at Compile-time:</h4>
|
||||
<blockquote>
|
||||
If you don't have a sound card, or would prefer to build the program with no sound support (and therefore without a the <code>SDL_mixer</code> dependency), you can run "<code>make</code>" with "<code>SDL_MIXER_LIB=</code>" added: </p>
|
||||
|
|
@ -636,18 +661,24 @@
|
|||
</blockquote>
|
||||
</blockquote>
|
||||
|
||||
<hr size="1" noshade width="75%" />
|
||||
|
||||
<h4>Other options:</h4>
|
||||
<blockquote>
|
||||
<p>
|
||||
Various other options (e.g., installation paths) may be overridden; see them in "<code>Makefile</code>" for further details. </p>
|
||||
</blockquote>
|
||||
|
||||
<hr size="1" noshade width="75%" />
|
||||
|
||||
<h4>If you get errors:</h4>
|
||||
<blockquote>
|
||||
<p>
|
||||
If you receive any errors during compile-time, make sure you have the appropriate libraries installed (see above). If using packaged versions of the libraries (e.g., RPMs under RedHat or DEBs under Debian), be sure to get the corresponding "<code>-dev</code>" or "<code>-devel</code>" packages as well, otherwise you won't be able to compile Tux Paint (and other programs) from source! </p>
|
||||
</blockquote>
|
||||
|
||||
<hr size="1" noshade width="75%" />
|
||||
|
||||
<h4>Installng:</h4>
|
||||
<blockquote>
|
||||
<p>
|
||||
|
|
@ -730,6 +761,134 @@
|
|||
</blockquote>
|
||||
</blockquote>
|
||||
</blockquote>
|
||||
|
||||
<hr size="1" noshade />
|
||||
|
||||
<h3>
|
||||
<a name="compiling-macos" id="compiling-macos">
|
||||
macOS Users </a>
|
||||
</h3>
|
||||
<p style="font-size: small;">
|
||||
<em>
|
||||
September 21, 2021 Mark K. Kim <<a href="mailto:markuskimius@gmail.com">markuskimius@gmail.com</a>>
|
||||
</em>
|
||||
</p>
|
||||
|
||||
<blockquote>
|
||||
<p>
|
||||
Tux Paint 0.9.22 and earlier required building Tux Paint from the Xcode IDE. Starting with 0.9.23, however, Tux Paint for macOS is built as though it were a Linux application. </p>
|
||||
|
||||
<h4>Prerequisites</h4>
|
||||
<blockquote>
|
||||
<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>libsdl</code></li>
|
||||
<li><code>libsdl_image</code></li>
|
||||
<li><code>libsdl_mixer</code></li>
|
||||
<li><code>libsdl_pango</code></li>
|
||||
<li><code>libsdl_ttf</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>
|
||||
|
||||
<h5>libimagequant</h5>
|
||||
<blockquote>
|
||||
<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>
|
||||
$ git clone https://github.com/ImageOptim/libimagequant.git<br/>
|
||||
$ cd libimagequant<br/>
|
||||
$ ./configure --prefix=/opt/local<br/>
|
||||
$ make<br/>
|
||||
$ sudo make install
|
||||
</code>
|
||||
</blockquote>
|
||||
</p>
|
||||
|
||||
</blockquote>
|
||||
|
||||
<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>
|
||||
</blockquote>
|
||||
|
||||
<hr size="1" noshade width="75%" />
|
||||
|
||||
<h4>How to Build</h4>
|
||||
<blockquote>
|
||||
<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>. It also creates <code>TuxPaint.dmg</code> for distribution. </p>
|
||||
</blockquote>
|
||||
|
||||
<hr size="1" noshade width="75%" />
|
||||
|
||||
<h4>Known Issues</h4>
|
||||
<blockquote>
|
||||
<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. </li>
|
||||
</ul>
|
||||
</blockquote>
|
||||
|
||||
<hr size="1" noshade width="75%" />
|
||||
|
||||
<h4>Old Versions of macOS</h4>
|
||||
<blockquote>
|
||||
<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 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>
|
||||
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>
|
||||
It has been found that macOS can be installed onto the bootable media itself, so you can make the flash drive into a bootable installer then install the old macOS onto the same flash drive. </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>xcode-select --install</code>") but otherwise build Tux Paint using the same steps described in the earlier part of this document. </p>
|
||||
|
||||
</blockquote>
|
||||
|
||||
</blockquote>
|
||||
|
||||
</blockquote>
|
||||
|
||||
<hr size="2" noshade />
|
||||
|
|
@ -769,6 +928,8 @@
|
|||
</blockquote>
|
||||
</blockquote>
|
||||
|
||||
<hr size="1" noshade />
|
||||
|
||||
<h3>
|
||||
<a name="uninstalling-linux" id="uninstalling-linux">
|
||||
Linux </a>
|
||||
|
|
|
|||
|
|
@ -18,6 +18,7 @@
|
|||
| * Compiling and Installation |
|
||||
| * Windows Users |
|
||||
| * Linux/Unix Users |
|
||||
| * macOS Users |
|
||||
| * Debugging |
|
||||
| * Uninstalling Tux Paint |
|
||||
| * Windows |
|
||||
|
|
@ -177,6 +178,8 @@ Compiling and Installation
|
|||
to the "MinGW 32bit (i686) toolchains" section if you need only a
|
||||
32bit build environment.
|
||||
|
||||
-------------------------------------------------------
|
||||
|
||||
MinGW 64bit (x86_64) toolchains
|
||||
|
||||
Within the MSYS2 shell, run the following command to install basic
|
||||
|
|
@ -247,6 +250,8 @@ Compiling and Installation
|
|||
to the "ImageMagick" section if you need only a 64bit build
|
||||
environment.
|
||||
|
||||
-------------------------------------------------------
|
||||
|
||||
MinGW 32bit (i686) toolchains
|
||||
|
||||
Within the MSYS2 shell, run the following command to install basic
|
||||
|
|
@ -313,6 +318,8 @@ Compiling and Installation
|
|||
$ cd SDL-1.2.15
|
||||
$ ./configure --prefix=/mingw32 && make && make install
|
||||
|
||||
-------------------------------------------------------
|
||||
|
||||
ImageMagick
|
||||
|
||||
ImageMagick is a compilation of command line tools to create, edit,
|
||||
|
|
@ -336,6 +343,8 @@ Compiling and Installation
|
|||
You can make this permanent by adding the above to your the BASH
|
||||
shell configuration file, "~/.bash_profile".
|
||||
|
||||
-------------------------------------------------------
|
||||
|
||||
Tux Paint
|
||||
|
||||
You can compile 64bit binaries using MSYS2 64bit shell, and 32bit
|
||||
|
|
@ -362,6 +371,8 @@ Compiling and Installation
|
|||
directory under "win32". You can start them by double-clicking their
|
||||
executable (.exe) files in the "bdist" directory.
|
||||
|
||||
-------------------------------------------------------
|
||||
|
||||
Building the Tux Paint Windows Installer:
|
||||
|
||||
Inno Setup is used to build executable installer for Tux Paint.
|
||||
|
|
@ -373,6 +384,8 @@ Compiling and Installation
|
|||
will find a "tuxpaint-X.Y.Z-win32-installer.exe" file in the same
|
||||
directory.
|
||||
|
||||
-------------------------------------------------------
|
||||
|
||||
Running the Tux Paint Windows Installer:
|
||||
|
||||
Double-click the Tux Paint installer executable (.EXE file) and
|
||||
|
|
@ -392,6 +405,8 @@ Compiling and Installation
|
|||
|
||||
At this point, you can click 'Install' to install Tux Paint!
|
||||
|
||||
-------------------------------------------------------
|
||||
|
||||
Changing the Settings Using the Shortcut:
|
||||
|
||||
To change program settings, right-click on the TuxPaint shortcut and
|
||||
|
|
@ -420,6 +435,8 @@ Compiling and Installation
|
|||
|
||||
When you have finished, click "OK."
|
||||
|
||||
-------------------------------------------------------
|
||||
|
||||
If Something Goes Wrong:
|
||||
|
||||
If, when you double-click on the shortcut to run Tux Paint, nothing
|
||||
|
|
@ -431,6 +448,8 @@ Compiling and Installation
|
|||
just be due to incorrect character-case (capital 'Z' instead of
|
||||
lowercase 'z') or a missing (or extra) '-' (dash).
|
||||
|
||||
----------------------------------------------------------------------
|
||||
|
||||
Linux/Unix Users
|
||||
|
||||
Compiling:
|
||||
|
|
@ -444,6 +463,8 @@ Compiling and Installation
|
|||
|
||||
$ make
|
||||
|
||||
-------------------------------------------------------
|
||||
|
||||
Disabling SVG support (and hence Cairo, libSVG, and svg-cairo dependencies):
|
||||
|
||||
To disable SVG support (e.g., if your system is not currently
|
||||
|
|
@ -453,6 +474,8 @@ Compiling and Installation
|
|||
|
||||
$ make SVG_LIB= SVG_CFLAGS=
|
||||
|
||||
-------------------------------------------------------
|
||||
|
||||
Disabling Pango support (and hence Pango, Cairo, etc. dependencies):
|
||||
|
||||
Prior to version 0.9.18, Tux Paint used the libSDL_ttf library for
|
||||
|
|
@ -463,6 +486,8 @@ Compiling and Installation
|
|||
|
||||
$ make SDL_PANGO_LIB=
|
||||
|
||||
-------------------------------------------------------
|
||||
|
||||
Disabling Sound at Compile-time:
|
||||
|
||||
If you don't have a sound card, or would prefer to build the program
|
||||
|
|
@ -471,11 +496,15 @@ Compiling and Installation
|
|||
|
||||
$ make SDL_MIXER_LIB=
|
||||
|
||||
-------------------------------------------------------
|
||||
|
||||
Other options:
|
||||
|
||||
Various other options (e.g., installation paths) may be overridden;
|
||||
see them in "Makefile" for further details.
|
||||
|
||||
-------------------------------------------------------
|
||||
|
||||
If you get errors:
|
||||
|
||||
If you receive any errors during compile-time, make sure you have
|
||||
|
|
@ -485,6 +514,8 @@ Compiling and Installation
|
|||
packages as well, otherwise you won't be able to compile Tux Paint
|
||||
(and other programs) from source!
|
||||
|
||||
-------------------------------------------------------
|
||||
|
||||
Installng:
|
||||
|
||||
Assuming no fatal errors occured, you can now install the program so
|
||||
|
|
@ -562,6 +593,138 @@ Compiling and Installation
|
|||
|
||||
----------------------------------------------------------------------
|
||||
|
||||
macOS Users
|
||||
|
||||
septiembre 21, 2021 Mark K. Kim <markuskimius@gmail.com>
|
||||
|
||||
Tux Paint 0.9.22 and earlier required building Tux Paint from the
|
||||
Xcode IDE. Starting with 0.9.23, however, Tux Paint for macOS is built
|
||||
as though it were a Linux application.
|
||||
|
||||
Prerequisites
|
||||
|
||||
Although Tux Paint is built without the Xcode IDE, Xcode itself is
|
||||
still required to build Tux Paint. Download it from the App Store,
|
||||
and launch it once to accept its license agreements. You may also
|
||||
need to install the Xcode command line tools using the command:
|
||||
|
||||
xcode-select --install
|
||||
|
||||
Building Tux Paint also requires various libraries. We install them
|
||||
from MacPorts where possible, source code otherwise. Install
|
||||
MacPorts to the default /opt/local path according to the
|
||||
instructions found on their website: https://www.macports.org/
|
||||
* ImageMagick
|
||||
* cairo
|
||||
* fribidi
|
||||
* lbzip2
|
||||
* libimagequant^*
|
||||
* libpaper
|
||||
* libpng
|
||||
* librsvg
|
||||
* libsdl
|
||||
* libsdl_image
|
||||
* libsdl_mixer
|
||||
* libsdl_pango
|
||||
* libsdl_ttf
|
||||
* pkgconfig
|
||||
* zlib
|
||||
... but you should install any package that is required by the
|
||||
latest version of Tux Paint.
|
||||
|
||||
^* Not available from MacPorts as of this writing, see below.
|
||||
|
||||
libimagequant
|
||||
|
||||
libimagequant is not available from MacPorts as of this writing.
|
||||
It can be installed from the source code as follows. It should be
|
||||
installed to /opt/local (same as MacPorts) for the library to be
|
||||
included in TuxPaint.dmg.
|
||||
|
||||
$ git clone https://github.com/ImageOptim/libimagequant.git
|
||||
$ cd libimagequant
|
||||
$ ./configure --prefix=/opt/local
|
||||
$ make
|
||||
$ sudo make install
|
||||
|
||||
WARNING: 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.
|
||||
|
||||
-------------------------------------------------------
|
||||
|
||||
How to Build
|
||||
|
||||
Simply, run:
|
||||
|
||||
% make
|
||||
% make install
|
||||
|
||||
... to create the TuxPaint.app application bundle that can be run
|
||||
in-place or copied to /Applications. It also creates TuxPaint.dmg
|
||||
for distribution.
|
||||
|
||||
-------------------------------------------------------
|
||||
|
||||
Known Issues
|
||||
|
||||
* 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.
|
||||
|
||||
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.
|
||||
|
||||
-------------------------------------------------------
|
||||
|
||||
Old Versions of macOS
|
||||
|
||||
Some old versions of macOS can be downloaded from Apple's support
|
||||
page: https://support.apple.com/en-us/HT211683
|
||||
|
||||
macOS 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.
|
||||
|
||||
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.
|
||||
|
||||
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:
|
||||
https://support.apple.com/en-mide/HT201372
|
||||
|
||||
It has been found that macOS can be installed onto the bootable
|
||||
media itself, so you can make the flash drive into a bootable
|
||||
installer then install the old macOS onto the same flash drive.
|
||||
|
||||
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:
|
||||
https://developer.apple.com/download/more/
|
||||
|
||||
The list of macOS versions and the last version of Xcode compatible
|
||||
with them are laid out nicely on the Wikipedia page on Xcode:
|
||||
https://en.wikipedia.org/wiki/Xcode#Version_comparison_table
|
||||
|
||||
And because Xcode is being installed manually, you can skip the step
|
||||
to install the Xcode command line tools (do not run "xcode-select
|
||||
--install") but otherwise build Tux Paint using the same steps
|
||||
described in the earlier part of this document.
|
||||
|
||||
----------------------------------------------------------------------
|
||||
|
||||
Debugging
|
||||
|
||||
Debugging (to "STDOUT", e.g. to the terminal, or to a "stdout.txt" file,
|
||||
|
|
@ -589,6 +752,8 @@ Uninstalling Tux Paint
|
|||
It is also possible to use the entry "TuxPaint (remove only)" in the
|
||||
Control Panel Add/Remove programs section.
|
||||
|
||||
----------------------------------------------------------------------
|
||||
|
||||
Linux
|
||||
|
||||
Within the Tux Paint source directory (where you compiled Tux Paint),
|
||||
|
|
|
|||
|
|
@ -63,6 +63,9 @@
|
|||
<li>
|
||||
<a href="#compiling-linux">Linux/Unix Users</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href="#compiling-macos">macOS Users</a>
|
||||
</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
|
|
@ -271,6 +274,7 @@
|
|||
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>
|
||||
|
||||
<hr size="1" noshade width="75%" />
|
||||
<h4>
|
||||
<a name="64bit" id="64bit">
|
||||
MinGW 64bit (x86_64) toolchains </a>
|
||||
|
|
@ -368,6 +372,7 @@
|
|||
<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>
|
||||
<hr size="1" noshade width="75%" />
|
||||
<h4>
|
||||
<a name="32bit" id="32bit">
|
||||
MinGW 32bit (i686) toolchains </a>
|
||||
|
|
@ -462,6 +467,8 @@
|
|||
</blockquote>
|
||||
|
||||
|
||||
<hr size="1" noshade width="75%" />
|
||||
|
||||
<h4>
|
||||
<a name="imagemagick" id="imagemagick">ImageMagick</a>
|
||||
</h4>
|
||||
|
|
@ -484,6 +491,8 @@
|
|||
You can make this permanent by adding the above to your the BASH shell configuration file, "<code>~/.bash_profile</code>". </p>
|
||||
</blockquote>
|
||||
|
||||
<hr size="1" noshade width="75%" />
|
||||
|
||||
<h4>Tux Paint</h4>
|
||||
|
||||
<blockquote>
|
||||
|
|
@ -508,6 +517,8 @@
|
|||
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>
|
||||
</blockquote>
|
||||
|
||||
<hr size="1" noshade width="75%" />
|
||||
|
||||
<h4>Building the Tux Paint Windows Installer:</h4>
|
||||
<blockquote>
|
||||
|
||||
|
|
@ -519,6 +530,8 @@
|
|||
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>-win32-installer.exe</code>" file in the same directory. </p>
|
||||
</blockquote>
|
||||
|
||||
<hr size="1" noshade width="75%" />
|
||||
|
||||
<h4>Running the Tux Paint Windows Installer:</h4>
|
||||
<blockquote>
|
||||
<p>
|
||||
|
|
@ -536,6 +549,8 @@
|
|||
At this point, you can click 'Install' to install Tux Paint! </p>
|
||||
</blockquote>
|
||||
|
||||
<hr size="1" noshade width="75%" />
|
||||
|
||||
<h4>Changing the Settings Using the Shortcut:</h4>
|
||||
<blockquote>
|
||||
<p>
|
||||
|
|
@ -572,6 +587,8 @@
|
|||
When you have finished, click "OK." </p>
|
||||
</blockquote>
|
||||
|
||||
<hr size="1" noshade width="75%" />
|
||||
|
||||
<h4>If Something Goes Wrong:</h4>
|
||||
<blockquote>
|
||||
<p>
|
||||
|
|
@ -582,6 +599,8 @@
|
|||
</blockquote>
|
||||
</blockquote>
|
||||
|
||||
<hr size="1" noshade />
|
||||
|
||||
<h3>
|
||||
<a name="compiling-linux" id="compiling-linux">
|
||||
Linux/Unix Users </a>
|
||||
|
|
@ -602,6 +621,8 @@
|
|||
</blockquote>
|
||||
</blockquote>
|
||||
|
||||
<hr size="1" noshade width="75%" />
|
||||
|
||||
<h4>
|
||||
Disabling SVG support (and hence Cairo, libSVG, and svg-cairo dependencies): </h4>
|
||||
<blockquote>
|
||||
|
|
@ -614,6 +635,8 @@
|
|||
</blockquote>
|
||||
</blockquote>
|
||||
|
||||
<hr size="1" noshade width="75%" />
|
||||
|
||||
<h4>
|
||||
Disabling Pango support (and hence Pango, Cairo, etc. dependencies): </h4>
|
||||
<blockquote>
|
||||
|
|
@ -626,6 +649,8 @@
|
|||
</blockquote>
|
||||
</blockquote>
|
||||
|
||||
<hr size="1" noshade width="75%" />
|
||||
|
||||
<h4>Disabling Sound at Compile-time:</h4>
|
||||
<blockquote>
|
||||
If you don't have a sound card, or would prefer to build the program with no sound support (and therefore without a the <code>SDL_mixer</code> dependency), you can run "<code>make</code>" with "<code>SDL_MIXER_LIB=</code>" added: </p>
|
||||
|
|
@ -636,18 +661,24 @@
|
|||
</blockquote>
|
||||
</blockquote>
|
||||
|
||||
<hr size="1" noshade width="75%" />
|
||||
|
||||
<h4>Other options:</h4>
|
||||
<blockquote>
|
||||
<p>
|
||||
Various other options (e.g., installation paths) may be overridden; see them in "<code>Makefile</code>" for further details. </p>
|
||||
</blockquote>
|
||||
|
||||
<hr size="1" noshade width="75%" />
|
||||
|
||||
<h4>If you get errors:</h4>
|
||||
<blockquote>
|
||||
<p>
|
||||
If you receive any errors during compile-time, make sure you have the appropriate libraries installed (see above). If using packaged versions of the libraries (e.g., RPMs under RedHat or DEBs under Debian), be sure to get the corresponding "<code>-dev</code>" or "<code>-devel</code>" packages as well, otherwise you won't be able to compile Tux Paint (and other programs) from source! </p>
|
||||
</blockquote>
|
||||
|
||||
<hr size="1" noshade width="75%" />
|
||||
|
||||
<h4>Installng:</h4>
|
||||
<blockquote>
|
||||
<p>
|
||||
|
|
@ -730,6 +761,134 @@
|
|||
</blockquote>
|
||||
</blockquote>
|
||||
</blockquote>
|
||||
|
||||
<hr size="1" noshade />
|
||||
|
||||
<h3>
|
||||
<a name="compiling-macos" id="compiling-macos">
|
||||
macOS Users </a>
|
||||
</h3>
|
||||
<p style="font-size: small;">
|
||||
<em>
|
||||
septiembre 21, 2021 Mark K. Kim <<a href="mailto:markuskimius@gmail.com">markuskimius@gmail.com</a>>
|
||||
</em>
|
||||
</p>
|
||||
|
||||
<blockquote>
|
||||
<p>
|
||||
Tux Paint 0.9.22 and earlier required building Tux Paint from the Xcode IDE. Starting with 0.9.23, however, Tux Paint for macOS is built as though it were a Linux application. </p>
|
||||
|
||||
<h4>Prerequisites</h4>
|
||||
<blockquote>
|
||||
<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>libsdl</code></li>
|
||||
<li><code>libsdl_image</code></li>
|
||||
<li><code>libsdl_mixer</code></li>
|
||||
<li><code>libsdl_pango</code></li>
|
||||
<li><code>libsdl_ttf</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>
|
||||
|
||||
<h5>libimagequant</h5>
|
||||
<blockquote>
|
||||
<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>
|
||||
$ git clone https://github.com/ImageOptim/libimagequant.git<br/>
|
||||
$ cd libimagequant<br/>
|
||||
$ ./configure --prefix=/opt/local<br/>
|
||||
$ make<br/>
|
||||
$ sudo make install
|
||||
</code>
|
||||
</blockquote>
|
||||
</p>
|
||||
|
||||
</blockquote>
|
||||
|
||||
<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>
|
||||
</blockquote>
|
||||
|
||||
<hr size="1" noshade width="75%" />
|
||||
|
||||
<h4>How to Build</h4>
|
||||
<blockquote>
|
||||
<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>. It also creates <code>TuxPaint.dmg</code> for distribution. </p>
|
||||
</blockquote>
|
||||
|
||||
<hr size="1" noshade width="75%" />
|
||||
|
||||
<h4>Known Issues</h4>
|
||||
<blockquote>
|
||||
<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. </li>
|
||||
</ul>
|
||||
</blockquote>
|
||||
|
||||
<hr size="1" noshade width="75%" />
|
||||
|
||||
<h4>Old Versions of macOS</h4>
|
||||
<blockquote>
|
||||
<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 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>
|
||||
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>
|
||||
It has been found that macOS can be installed onto the bootable media itself, so you can make the flash drive into a bootable installer then install the old macOS onto the same flash drive. </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>xcode-select --install</code>") but otherwise build Tux Paint using the same steps described in the earlier part of this document. </p>
|
||||
|
||||
</blockquote>
|
||||
|
||||
</blockquote>
|
||||
|
||||
</blockquote>
|
||||
|
||||
<hr size="2" noshade />
|
||||
|
|
@ -769,6 +928,8 @@
|
|||
</blockquote>
|
||||
</blockquote>
|
||||
|
||||
<hr size="1" noshade />
|
||||
|
||||
<h3>
|
||||
<a name="uninstalling-linux" id="uninstalling-linux">
|
||||
Linux </a>
|
||||
|
|
|
|||
|
|
@ -18,6 +18,7 @@
|
|||
| * Compiling and Installation |
|
||||
| * Utilisateurs de Windows |
|
||||
| * Utilisateurs de Linux/Unix |
|
||||
| * Utilisateurs de macOS |
|
||||
| * Debugging |
|
||||
| * Uninstalling Tux Paint |
|
||||
| * Windows |
|
||||
|
|
@ -180,6 +181,8 @@ Compiling and Installation
|
|||
to the "MinGW 32bit (i686) toolchains" section if you need only a
|
||||
32bit build environment.
|
||||
|
||||
-------------------------------------------------------
|
||||
|
||||
MinGW 64bit (x86_64) toolchains
|
||||
|
||||
Within the MSYS2 shell, run the following command to install basic
|
||||
|
|
@ -250,6 +253,8 @@ Compiling and Installation
|
|||
to the "ImageMagick" section if you need only a 64bit build
|
||||
environment.
|
||||
|
||||
-------------------------------------------------------
|
||||
|
||||
MinGW 32bit (i686) toolchains
|
||||
|
||||
Within the MSYS2 shell, run the following command to install basic
|
||||
|
|
@ -316,6 +321,8 @@ Compiling and Installation
|
|||
$ cd SDL-1.2.15
|
||||
$ ./configure --prefix=/mingw32 && make && make install
|
||||
|
||||
-------------------------------------------------------
|
||||
|
||||
ImageMagick
|
||||
|
||||
ImageMagick is a compilation of command line tools to create, edit,
|
||||
|
|
@ -339,6 +346,8 @@ Compiling and Installation
|
|||
You can make this permanent by adding the above to your the BASH
|
||||
shell configuration file, "~/.bash_profile".
|
||||
|
||||
-------------------------------------------------------
|
||||
|
||||
Tux Paint
|
||||
|
||||
You can compile 64bit binaries using MSYS2 64bit shell, and 32bit
|
||||
|
|
@ -365,6 +374,8 @@ Compiling and Installation
|
|||
directory under "win32". You can start them by double-clicking their
|
||||
executable (.exe) files in the "bdist" directory.
|
||||
|
||||
-------------------------------------------------------
|
||||
|
||||
Building the Tux Paint Windows Installer:
|
||||
|
||||
Inno Setup is used to build executable installer for Tux Paint.
|
||||
|
|
@ -376,6 +387,8 @@ Compiling and Installation
|
|||
will find a "tuxpaint-X.Y.Z-win32-installer.exe" file in the same
|
||||
directory.
|
||||
|
||||
-------------------------------------------------------
|
||||
|
||||
Running the Tux Paint Windows Installer:
|
||||
|
||||
Double-cliquez sur l'exécutable du programme d'installation de Tux
|
||||
|
|
@ -396,6 +409,8 @@ Compiling and Installation
|
|||
À ce stade, vous pouvez cliquer sur «Installer» pour installer Tux
|
||||
Paint !
|
||||
|
||||
-------------------------------------------------------
|
||||
|
||||
Modification des paramètres à l'aide du raccourci :
|
||||
|
||||
Pour modifier les paramètres du programme, cliquez avec le bouton
|
||||
|
|
@ -427,6 +442,8 @@ Compiling and Installation
|
|||
|
||||
Quand vous avez fini, appuyez sur "OK".
|
||||
|
||||
-------------------------------------------------------
|
||||
|
||||
Si quelque chose ne va pas :
|
||||
|
||||
Si, lorsque vous double-cliquez sur le raccourci pour lancer le jeu,
|
||||
|
|
@ -440,6 +457,8 @@ Compiling and Installation
|
|||
incorrecte (majuscule 'Z' à la place de 'z' minuscule) ou un '-'
|
||||
(tiret) manquant (en trop).
|
||||
|
||||
----------------------------------------------------------------------
|
||||
|
||||
Utilisateurs de Linux/Unix
|
||||
|
||||
Compilation :
|
||||
|
|
@ -454,6 +473,8 @@ Compiling and Installation
|
|||
|
||||
$ make
|
||||
|
||||
-------------------------------------------------------
|
||||
|
||||
Désactivation du support SVG (donc des dépendances Cairo, libSVG, et
|
||||
svg-cairo)
|
||||
|
||||
|
|
@ -464,6 +485,8 @@ Compiling and Installation
|
|||
|
||||
$ make SVG_LIB= SVG_CFLAGS=
|
||||
|
||||
-------------------------------------------------------
|
||||
|
||||
Désactivation du support Pango (donc des dépendances Pango, Cairo, etc ...)
|
||||
|
||||
Avant la version 0.9.18, Tuxpaint utilisait la bibliothèque
|
||||
|
|
@ -475,6 +498,8 @@ Compiling and Installation
|
|||
|
||||
$ make SDL_PANGO_LIB=
|
||||
|
||||
-------------------------------------------------------
|
||||
|
||||
Désactiver le son lors de la compilation :
|
||||
|
||||
Si vous n'avez pas de carte son ou si vous préférez créer le
|
||||
|
|
@ -483,11 +508,15 @@ Compiling and Installation
|
|||
|
||||
$ make SDL_MIXER_LIB=
|
||||
|
||||
-------------------------------------------------------
|
||||
|
||||
Autres options :
|
||||
|
||||
Diverses autres options (par exemple, les dossiers d'installation)
|
||||
peuvent être remplacées; voir dans "Makefile" pour plus de détails.
|
||||
|
||||
-------------------------------------------------------
|
||||
|
||||
Si vous obtenez des erreurs :
|
||||
|
||||
Si vous avez des erreurs lors de la compilation, assurez-vous
|
||||
|
|
@ -498,6 +527,8 @@ Compiling and Installation
|
|||
correspondants, sinon vous ne pourrez pas compiler Tux Paint (et
|
||||
d'autres programmes) provenant des sources !
|
||||
|
||||
-------------------------------------------------------
|
||||
|
||||
Installation :
|
||||
|
||||
En supposant qu'aucune erreur fatale ne s'est produite, vous pouvez
|
||||
|
|
@ -576,6 +607,138 @@ Compiling and Installation
|
|||
|
||||
----------------------------------------------------------------------
|
||||
|
||||
Utilisateurs de macOS
|
||||
|
||||
septembre 21, 2021 Mark K. Kim <markuskimius@gmail.com>
|
||||
|
||||
Tux Paint 0.9.22 and earlier required building Tux Paint from the
|
||||
Xcode IDE. Starting with 0.9.23, however, Tux Paint for macOS is built
|
||||
as though it were a Linux application.
|
||||
|
||||
Prerequisites
|
||||
|
||||
Although Tux Paint is built without the Xcode IDE, Xcode itself is
|
||||
still required to build Tux Paint. Download it from the App Store,
|
||||
and launch it once to accept its license agreements. You may also
|
||||
need to install the Xcode command line tools using the command:
|
||||
|
||||
xcode-select --install
|
||||
|
||||
Building Tux Paint also requires various libraries. We install them
|
||||
from MacPorts where possible, source code otherwise. Install
|
||||
MacPorts to the default /opt/local path according to the
|
||||
instructions found on their website: https://www.macports.org/
|
||||
* ImageMagick
|
||||
* cairo
|
||||
* fribidi
|
||||
* lbzip2
|
||||
* libimagequant^*
|
||||
* libpaper
|
||||
* libpng
|
||||
* librsvg
|
||||
* libsdl
|
||||
* libsdl_image
|
||||
* libsdl_mixer
|
||||
* libsdl_pango
|
||||
* libsdl_ttf
|
||||
* pkgconfig
|
||||
* zlib
|
||||
... but you should install any package that is required by the
|
||||
latest version of Tux Paint.
|
||||
|
||||
^* Not available from MacPorts as of this writing, see below.
|
||||
|
||||
libimagequant
|
||||
|
||||
libimagequant is not available from MacPorts as of this writing.
|
||||
It can be installed from the source code as follows. It should be
|
||||
installed to /opt/local (same as MacPorts) for the library to be
|
||||
included in TuxPaint.dmg.
|
||||
|
||||
$ git clone https://github.com/ImageOptim/libimagequant.git
|
||||
$ cd libimagequant
|
||||
$ ./configure --prefix=/opt/local
|
||||
$ make
|
||||
$ sudo make install
|
||||
|
||||
WARNING: 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.
|
||||
|
||||
-------------------------------------------------------
|
||||
|
||||
How to Build
|
||||
|
||||
Simply, run:
|
||||
|
||||
% make
|
||||
% make install
|
||||
|
||||
... to create the TuxPaint.app application bundle that can be run
|
||||
in-place or copied to /Applications. It also creates TuxPaint.dmg
|
||||
for distribution.
|
||||
|
||||
-------------------------------------------------------
|
||||
|
||||
Known Issues
|
||||
|
||||
* 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.
|
||||
|
||||
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.
|
||||
|
||||
-------------------------------------------------------
|
||||
|
||||
Old Versions of macOS
|
||||
|
||||
Some old versions of macOS can be downloaded from Apple's support
|
||||
page: https://support.apple.com/en-us/HT211683
|
||||
|
||||
macOS 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.
|
||||
|
||||
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.
|
||||
|
||||
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:
|
||||
https://support.apple.com/en-mide/HT201372
|
||||
|
||||
It has been found that macOS can be installed onto the bootable
|
||||
media itself, so you can make the flash drive into a bootable
|
||||
installer then install the old macOS onto the same flash drive.
|
||||
|
||||
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:
|
||||
https://developer.apple.com/download/more/
|
||||
|
||||
The list of macOS versions and the last version of Xcode compatible
|
||||
with them are laid out nicely on the Wikipedia page on Xcode:
|
||||
https://en.wikipedia.org/wiki/Xcode#Version_comparison_table
|
||||
|
||||
And because Xcode is being installed manually, you can skip the step
|
||||
to install the Xcode command line tools (do not run "xcode-select
|
||||
--install") but otherwise build Tux Paint using the same steps
|
||||
described in the earlier part of this document.
|
||||
|
||||
----------------------------------------------------------------------
|
||||
|
||||
Debugging
|
||||
|
||||
Le débogage (vers "STDOUT", par exemple le terminal, ou vers un fichier
|
||||
|
|
@ -605,6 +768,8 @@ Uninstalling Tux Paint
|
|||
uniquement)" dans la Section Ajout / Suppression de programmes du
|
||||
Panneau de configuration.
|
||||
|
||||
----------------------------------------------------------------------
|
||||
|
||||
Linux
|
||||
|
||||
Dans le répertoire source de Tux Paint (où vous avez compilé Tux
|
||||
|
|
|
|||
|
|
@ -63,6 +63,9 @@
|
|||
<li>
|
||||
<a href="#compiling-linux">Utilisateurs de Linux/Unix</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href="#compiling-macos">Utilisateurs de macOS</a>
|
||||
</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
|
|
@ -271,6 +274,7 @@
|
|||
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>
|
||||
|
||||
<hr size="1" noshade width="75%" />
|
||||
<h4>
|
||||
<a name="64bit" id="64bit">
|
||||
MinGW 64bit (x86_64) toolchains </a>
|
||||
|
|
@ -368,6 +372,7 @@
|
|||
<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>
|
||||
<hr size="1" noshade width="75%" />
|
||||
<h4>
|
||||
<a name="32bit" id="32bit">
|
||||
MinGW 32bit (i686) toolchains </a>
|
||||
|
|
@ -462,6 +467,8 @@
|
|||
</blockquote>
|
||||
|
||||
|
||||
<hr size="1" noshade width="75%" />
|
||||
|
||||
<h4>
|
||||
<a name="imagemagick" id="imagemagick">ImageMagick</a>
|
||||
</h4>
|
||||
|
|
@ -484,6 +491,8 @@
|
|||
You can make this permanent by adding the above to your the BASH shell configuration file, "<code>~/.bash_profile</code>". </p>
|
||||
</blockquote>
|
||||
|
||||
<hr size="1" noshade width="75%" />
|
||||
|
||||
<h4>Tux Paint</h4>
|
||||
|
||||
<blockquote>
|
||||
|
|
@ -508,6 +517,8 @@
|
|||
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>
|
||||
</blockquote>
|
||||
|
||||
<hr size="1" noshade width="75%" />
|
||||
|
||||
<h4>Building the Tux Paint Windows Installer:</h4>
|
||||
<blockquote>
|
||||
|
||||
|
|
@ -519,6 +530,8 @@
|
|||
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>-win32-installer.exe</code>" file in the same directory. </p>
|
||||
</blockquote>
|
||||
|
||||
<hr size="1" noshade width="75%" />
|
||||
|
||||
<h4>Running the Tux Paint Windows Installer:</h4>
|
||||
<blockquote>
|
||||
<p>
|
||||
|
|
@ -536,6 +549,8 @@
|
|||
À ce stade, vous pouvez cliquer sur «Installer» pour installer Tux Paint ! </p>
|
||||
</blockquote>
|
||||
|
||||
<hr size="1" noshade width="75%" />
|
||||
|
||||
<h4>Modification des paramètres à l'aide du raccourci :</h4>
|
||||
<blockquote>
|
||||
<p>
|
||||
|
|
@ -572,6 +587,8 @@
|
|||
Quand vous avez fini, appuyez sur "OK". </p>
|
||||
</blockquote>
|
||||
|
||||
<hr size="1" noshade width="75%" />
|
||||
|
||||
<h4>Si quelque chose ne va pas :</h4>
|
||||
<blockquote>
|
||||
<p>
|
||||
|
|
@ -582,6 +599,8 @@
|
|||
</blockquote>
|
||||
</blockquote>
|
||||
|
||||
<hr size="1" noshade />
|
||||
|
||||
<h3>
|
||||
<a name="compiling-linux" id="compiling-linux">
|
||||
Utilisateurs de Linux/Unix </a>
|
||||
|
|
@ -602,6 +621,8 @@
|
|||
</blockquote>
|
||||
</blockquote>
|
||||
|
||||
<hr size="1" noshade width="75%" />
|
||||
|
||||
<h4>
|
||||
Désactivation du support SVG (donc des dépendances Cairo, libSVG, et svg-cairo) </h4>
|
||||
<blockquote>
|
||||
|
|
@ -614,6 +635,8 @@
|
|||
</blockquote>
|
||||
</blockquote>
|
||||
|
||||
<hr size="1" noshade width="75%" />
|
||||
|
||||
<h4>
|
||||
Désactivation du support Pango (donc des dépendances Pango, Cairo, etc ...) </h4>
|
||||
<blockquote>
|
||||
|
|
@ -626,6 +649,8 @@
|
|||
</blockquote>
|
||||
</blockquote>
|
||||
|
||||
<hr size="1" noshade width="75%" />
|
||||
|
||||
<h4>Désactiver le son lors de la compilation :</h4>
|
||||
<blockquote>
|
||||
Si vous n'avez pas de carte son ou si vous préférez créer le programme sans support sonore (et donc sans dépendance <code>SDL_mixer</code>), vous pouvez exécuter "<code>make</code>" avec "<code>SDL_MIXER_LIB=</code>" comme paramètre : </p>
|
||||
|
|
@ -636,18 +661,24 @@
|
|||
</blockquote>
|
||||
</blockquote>
|
||||
|
||||
<hr size="1" noshade width="75%" />
|
||||
|
||||
<h4>Autres options :</h4>
|
||||
<blockquote>
|
||||
<p>
|
||||
Diverses autres options (par exemple, les dossiers d'installation) peuvent être remplacées; voir dans "<code>Makefile</code>" pour plus de détails. </p>
|
||||
</blockquote>
|
||||
|
||||
<hr size="1" noshade width="75%" />
|
||||
|
||||
<h4>Si vous obtenez des erreurs :</h4>
|
||||
<blockquote>
|
||||
<p>
|
||||
Si vous avez des erreurs lors de la compilation, assurez-vous d'avoir les bibliothèques adéquates installées (voir ci-dessus). Si vous utilisez les versions issues des paquets des bibliothèques (par exemple, les RPM sous RedHat ou les DEB sous Debian), assurez-vous d'avoir choisi également les packages "<code>-dev</code>" ou "<code>-devel</code>" correspondants, sinon vous ne pourrez pas compiler Tux Paint (et d'autres programmes) provenant des sources ! </p>
|
||||
</blockquote>
|
||||
|
||||
<hr size="1" noshade width="75%" />
|
||||
|
||||
<h4>Installation :</h4>
|
||||
<blockquote>
|
||||
<p>
|
||||
|
|
@ -730,6 +761,134 @@
|
|||
</blockquote>
|
||||
</blockquote>
|
||||
</blockquote>
|
||||
|
||||
<hr size="1" noshade />
|
||||
|
||||
<h3>
|
||||
<a name="compiling-macos" id="compiling-macos">
|
||||
Utilisateurs de macOS </a>
|
||||
</h3>
|
||||
<p style="font-size: small;">
|
||||
<em>
|
||||
septembre 21, 2021 Mark K. Kim <<a href="mailto:markuskimius@gmail.com">markuskimius@gmail.com</a>>
|
||||
</em>
|
||||
</p>
|
||||
|
||||
<blockquote>
|
||||
<p>
|
||||
Tux Paint 0.9.22 and earlier required building Tux Paint from the Xcode IDE. Starting with 0.9.23, however, Tux Paint for macOS is built as though it were a Linux application. </p>
|
||||
|
||||
<h4>Prerequisites</h4>
|
||||
<blockquote>
|
||||
<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>libsdl</code></li>
|
||||
<li><code>libsdl_image</code></li>
|
||||
<li><code>libsdl_mixer</code></li>
|
||||
<li><code>libsdl_pango</code></li>
|
||||
<li><code>libsdl_ttf</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>
|
||||
|
||||
<h5>libimagequant</h5>
|
||||
<blockquote>
|
||||
<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>
|
||||
$ git clone https://github.com/ImageOptim/libimagequant.git<br/>
|
||||
$ cd libimagequant<br/>
|
||||
$ ./configure --prefix=/opt/local<br/>
|
||||
$ make<br/>
|
||||
$ sudo make install
|
||||
</code>
|
||||
</blockquote>
|
||||
</p>
|
||||
|
||||
</blockquote>
|
||||
|
||||
<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>
|
||||
</blockquote>
|
||||
|
||||
<hr size="1" noshade width="75%" />
|
||||
|
||||
<h4>How to Build</h4>
|
||||
<blockquote>
|
||||
<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>. It also creates <code>TuxPaint.dmg</code> for distribution. </p>
|
||||
</blockquote>
|
||||
|
||||
<hr size="1" noshade width="75%" />
|
||||
|
||||
<h4>Known Issues</h4>
|
||||
<blockquote>
|
||||
<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. </li>
|
||||
</ul>
|
||||
</blockquote>
|
||||
|
||||
<hr size="1" noshade width="75%" />
|
||||
|
||||
<h4>Old Versions of macOS</h4>
|
||||
<blockquote>
|
||||
<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 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>
|
||||
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>
|
||||
It has been found that macOS can be installed onto the bootable media itself, so you can make the flash drive into a bootable installer then install the old macOS onto the same flash drive. </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>xcode-select --install</code>") but otherwise build Tux Paint using the same steps described in the earlier part of this document. </p>
|
||||
|
||||
</blockquote>
|
||||
|
||||
</blockquote>
|
||||
|
||||
</blockquote>
|
||||
|
||||
<hr size="2" noshade />
|
||||
|
|
@ -769,6 +928,8 @@
|
|||
</blockquote>
|
||||
</blockquote>
|
||||
|
||||
<hr size="1" noshade />
|
||||
|
||||
<h3>
|
||||
<a name="uninstalling-linux" id="uninstalling-linux">
|
||||
Linux </a>
|
||||
|
|
|
|||
|
|
@ -18,6 +18,7 @@
|
|||
| * Compiling and Installation |
|
||||
| * Usuarios de Windows |
|
||||
| * Usuarios de Linux/Unix |
|
||||
| * Usuarios de macOS |
|
||||
| * Debugging |
|
||||
| * Uninstalling Tux Paint |
|
||||
| * Windows |
|
||||
|
|
@ -181,6 +182,8 @@ Compiling and Installation
|
|||
to the "MinGW 32bit (i686) toolchains" section if you need only a
|
||||
32bit build environment.
|
||||
|
||||
-------------------------------------------------------
|
||||
|
||||
MinGW 64bit (x86_64) toolchains
|
||||
|
||||
Within the MSYS2 shell, run the following command to install basic
|
||||
|
|
@ -251,6 +254,8 @@ Compiling and Installation
|
|||
to the "ImageMagick" section if you need only a 64bit build
|
||||
environment.
|
||||
|
||||
-------------------------------------------------------
|
||||
|
||||
MinGW 32bit (i686) toolchains
|
||||
|
||||
Within the MSYS2 shell, run the following command to install basic
|
||||
|
|
@ -317,6 +322,8 @@ Compiling and Installation
|
|||
$ cd SDL-1.2.15
|
||||
$ ./configure --prefix=/mingw32 && make && make install
|
||||
|
||||
-------------------------------------------------------
|
||||
|
||||
ImageMagick
|
||||
|
||||
ImageMagick is a compilation of command line tools to create, edit,
|
||||
|
|
@ -340,6 +347,8 @@ Compiling and Installation
|
|||
You can make this permanent by adding the above to your the BASH
|
||||
shell configuration file, "~/.bash_profile".
|
||||
|
||||
-------------------------------------------------------
|
||||
|
||||
Tux Paint
|
||||
|
||||
You can compile 64bit binaries using MSYS2 64bit shell, and 32bit
|
||||
|
|
@ -366,6 +375,8 @@ Compiling and Installation
|
|||
directory under "win32". You can start them by double-clicking their
|
||||
executable (.exe) files in the "bdist" directory.
|
||||
|
||||
-------------------------------------------------------
|
||||
|
||||
Building the Tux Paint Windows Installer:
|
||||
|
||||
Inno Setup is used to build executable installer for Tux Paint.
|
||||
|
|
@ -377,6 +388,8 @@ Compiling and Installation
|
|||
will find a "tuxpaint-X.Y.Z-win32-installer.exe" file in the same
|
||||
directory.
|
||||
|
||||
-------------------------------------------------------
|
||||
|
||||
Running the Tux Paint Windows Installer:
|
||||
|
||||
Faga dobre clic no executábel do instalador de Tux Paint (ficheiro
|
||||
|
|
@ -396,6 +409,8 @@ Compiling and Installation
|
|||
|
||||
Neste punto, pode premer en «Instalar» para instalar Tux Paint.
|
||||
|
||||
-------------------------------------------------------
|
||||
|
||||
Cambiar os axustes usando o acceso directo:
|
||||
|
||||
Para cambiar os axustes do programa, prema co botón dereito no
|
||||
|
|
@ -424,6 +439,8 @@ Compiling and Installation
|
|||
|
||||
Cando teña rematado, prema en «Aceptar».
|
||||
|
||||
-------------------------------------------------------
|
||||
|
||||
Se algo vai mal:
|
||||
|
||||
Se ao facer dobre clic no atallo para executar Tux Paint, non ocorre
|
||||
|
|
@ -435,6 +452,8 @@ Compiling and Installation
|
|||
maiúsculas e minúsculas incorrectas (maiúsculas «Z» no canto de
|
||||
minúsculas «z») ou a falta (ou exceso) de «-» (guións).
|
||||
|
||||
----------------------------------------------------------------------
|
||||
|
||||
Usuarios de Linux/Unix
|
||||
|
||||
Compilación:
|
||||
|
|
@ -449,6 +468,8 @@ Compiling and Installation
|
|||
|
||||
$ make
|
||||
|
||||
-------------------------------------------------------
|
||||
|
||||
Desactivar a compatibilidade de «SVG» (e, polo tanto, as dependencias de
|
||||
«Cairo, libSVG, e svg-cairo»:
|
||||
|
||||
|
|
@ -459,6 +480,8 @@ Compiling and Installation
|
|||
|
||||
$ make SVG_LIB= SVG_CFLAGS=
|
||||
|
||||
-------------------------------------------------------
|
||||
|
||||
Desactivar a compatibilidade de «Pango» (e, polo tanto, as dependencias de
|
||||
«Pango, Cairo, etc.»:
|
||||
|
||||
|
|
@ -470,6 +493,8 @@ Compiling and Installation
|
|||
|
||||
$ make SDL_PANGO_LIB=
|
||||
|
||||
-------------------------------------------------------
|
||||
|
||||
Desactivación do son en tempo de compilación:
|
||||
|
||||
Se non te unha tarxeta de son ou prefire construír o programa sen
|
||||
|
|
@ -478,11 +503,15 @@ Compiling and Installation
|
|||
|
||||
$ make SDL_MIXER_LIB=
|
||||
|
||||
-------------------------------------------------------
|
||||
|
||||
Outras opcións:
|
||||
|
||||
Outras opcións (p. ex.: rutas de instalación) poden ser anuladas;
|
||||
véxaas en «Makefile» para máis detalles.
|
||||
|
||||
-------------------------------------------------------
|
||||
|
||||
Se se producen erros:
|
||||
|
||||
Se recibe algún erro durante o tempo de compilación, asegúrese de
|
||||
|
|
@ -492,6 +521,8 @@ Compiling and Installation
|
|||
correspondentes paquetes «-dev» ou «-devel», se non, non poderá
|
||||
compilar Tux Paint (e outros programas) dende o código fonte.
|
||||
|
||||
-------------------------------------------------------
|
||||
|
||||
Instalar:
|
||||
|
||||
Supoñendo que non se produciron erros graves, agora pode instalar o
|
||||
|
|
@ -572,6 +603,138 @@ Compiling and Installation
|
|||
|
||||
----------------------------------------------------------------------
|
||||
|
||||
Usuarios de macOS
|
||||
|
||||
21 de Setembro de 2021 Mark K. Kim <markuskimius@gmail.com>
|
||||
|
||||
Tux Paint 0.9.22 and earlier required building Tux Paint from the
|
||||
Xcode IDE. Starting with 0.9.23, however, Tux Paint for macOS is built
|
||||
as though it were a Linux application.
|
||||
|
||||
Prerequisites
|
||||
|
||||
Although Tux Paint is built without the Xcode IDE, Xcode itself is
|
||||
still required to build Tux Paint. Download it from the App Store,
|
||||
and launch it once to accept its license agreements. You may also
|
||||
need to install the Xcode command line tools using the command:
|
||||
|
||||
xcode-select --install
|
||||
|
||||
Building Tux Paint also requires various libraries. We install them
|
||||
from MacPorts where possible, source code otherwise. Install
|
||||
MacPorts to the default /opt/local path according to the
|
||||
instructions found on their website: https://www.macports.org/
|
||||
* ImageMagick
|
||||
* cairo
|
||||
* fribidi
|
||||
* lbzip2
|
||||
* libimagequant^*
|
||||
* libpaper
|
||||
* libpng
|
||||
* librsvg
|
||||
* libsdl
|
||||
* libsdl_image
|
||||
* libsdl_mixer
|
||||
* libsdl_pango
|
||||
* libsdl_ttf
|
||||
* pkgconfig
|
||||
* zlib
|
||||
... but you should install any package that is required by the
|
||||
latest version of Tux Paint.
|
||||
|
||||
^* Not available from MacPorts as of this writing, see below.
|
||||
|
||||
libimagequant
|
||||
|
||||
libimagequant is not available from MacPorts as of this writing.
|
||||
It can be installed from the source code as follows. It should be
|
||||
installed to /opt/local (same as MacPorts) for the library to be
|
||||
included in TuxPaint.dmg.
|
||||
|
||||
$ git clone https://github.com/ImageOptim/libimagequant.git
|
||||
$ cd libimagequant
|
||||
$ ./configure --prefix=/opt/local
|
||||
$ make
|
||||
$ sudo make install
|
||||
|
||||
WARNING: 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.
|
||||
|
||||
-------------------------------------------------------
|
||||
|
||||
How to Build
|
||||
|
||||
Simply, run:
|
||||
|
||||
% make
|
||||
% make install
|
||||
|
||||
... to create the TuxPaint.app application bundle that can be run
|
||||
in-place or copied to /Applications. It also creates TuxPaint.dmg
|
||||
for distribution.
|
||||
|
||||
-------------------------------------------------------
|
||||
|
||||
Known Issues
|
||||
|
||||
* 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.
|
||||
|
||||
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.
|
||||
|
||||
-------------------------------------------------------
|
||||
|
||||
Old Versions of macOS
|
||||
|
||||
Some old versions of macOS can be downloaded from Apple's support
|
||||
page: https://support.apple.com/en-us/HT211683
|
||||
|
||||
macOS 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.
|
||||
|
||||
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.
|
||||
|
||||
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:
|
||||
https://support.apple.com/en-mide/HT201372
|
||||
|
||||
It has been found that macOS can be installed onto the bootable
|
||||
media itself, so you can make the flash drive into a bootable
|
||||
installer then install the old macOS onto the same flash drive.
|
||||
|
||||
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:
|
||||
https://developer.apple.com/download/more/
|
||||
|
||||
The list of macOS versions and the last version of Xcode compatible
|
||||
with them are laid out nicely on the Wikipedia page on Xcode:
|
||||
https://en.wikipedia.org/wiki/Xcode#Version_comparison_table
|
||||
|
||||
And because Xcode is being installed manually, you can skip the step
|
||||
to install the Xcode command line tools (do not run "xcode-select
|
||||
--install") but otherwise build Tux Paint using the same steps
|
||||
described in the earlier part of this document.
|
||||
|
||||
----------------------------------------------------------------------
|
||||
|
||||
Debugging
|
||||
|
||||
A depuración (a «STDOUT», por exemplo, á terminal ou a un ficheiro
|
||||
|
|
@ -599,6 +762,8 @@ Uninstalling Tux Paint
|
|||
Tamén é posíbel usar a entrada «TuxPaint (só eliminar)« na sección
|
||||
Engadir/Eliminar programas do Panel de control.
|
||||
|
||||
----------------------------------------------------------------------
|
||||
|
||||
Linux
|
||||
|
||||
Dentro do directorio de orixe de Tux Paint (onde compilou Tux Paint),
|
||||
|
|
|
|||
|
|
@ -63,6 +63,9 @@
|
|||
<li>
|
||||
<a href="#compiling-linux">Usuarios de Linux/Unix</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href="#compiling-macos">Usuarios de macOS</a>
|
||||
</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
|
|
@ -271,6 +274,7 @@
|
|||
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>
|
||||
|
||||
<hr size="1" noshade width="75%" />
|
||||
<h4>
|
||||
<a name="64bit" id="64bit">
|
||||
MinGW 64bit (x86_64) toolchains </a>
|
||||
|
|
@ -368,6 +372,7 @@
|
|||
<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>
|
||||
<hr size="1" noshade width="75%" />
|
||||
<h4>
|
||||
<a name="32bit" id="32bit">
|
||||
MinGW 32bit (i686) toolchains </a>
|
||||
|
|
@ -462,6 +467,8 @@
|
|||
</blockquote>
|
||||
|
||||
|
||||
<hr size="1" noshade width="75%" />
|
||||
|
||||
<h4>
|
||||
<a name="imagemagick" id="imagemagick">ImageMagick</a>
|
||||
</h4>
|
||||
|
|
@ -484,6 +491,8 @@
|
|||
You can make this permanent by adding the above to your the BASH shell configuration file, "<code>~/.bash_profile</code>". </p>
|
||||
</blockquote>
|
||||
|
||||
<hr size="1" noshade width="75%" />
|
||||
|
||||
<h4>Tux Paint</h4>
|
||||
|
||||
<blockquote>
|
||||
|
|
@ -508,6 +517,8 @@
|
|||
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>
|
||||
</blockquote>
|
||||
|
||||
<hr size="1" noshade width="75%" />
|
||||
|
||||
<h4>Building the Tux Paint Windows Installer:</h4>
|
||||
<blockquote>
|
||||
|
||||
|
|
@ -519,6 +530,8 @@
|
|||
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>-win32-installer.exe</code>" file in the same directory. </p>
|
||||
</blockquote>
|
||||
|
||||
<hr size="1" noshade width="75%" />
|
||||
|
||||
<h4>Running the Tux Paint Windows Installer:</h4>
|
||||
<blockquote>
|
||||
<p>
|
||||
|
|
@ -536,6 +549,8 @@
|
|||
Neste punto, pode premer en «Instalar» para instalar Tux Paint. </p>
|
||||
</blockquote>
|
||||
|
||||
<hr size="1" noshade width="75%" />
|
||||
|
||||
<h4>Cambiar os axustes usando o acceso directo:</h4>
|
||||
<blockquote>
|
||||
<p>
|
||||
|
|
@ -572,6 +587,8 @@
|
|||
Cando teña rematado, prema en «Aceptar». </p>
|
||||
</blockquote>
|
||||
|
||||
<hr size="1" noshade width="75%" />
|
||||
|
||||
<h4>Se algo vai mal:</h4>
|
||||
<blockquote>
|
||||
<p>
|
||||
|
|
@ -582,6 +599,8 @@
|
|||
</blockquote>
|
||||
</blockquote>
|
||||
|
||||
<hr size="1" noshade />
|
||||
|
||||
<h3>
|
||||
<a name="compiling-linux" id="compiling-linux">
|
||||
Usuarios de Linux/Unix </a>
|
||||
|
|
@ -602,6 +621,8 @@
|
|||
</blockquote>
|
||||
</blockquote>
|
||||
|
||||
<hr size="1" noshade width="75%" />
|
||||
|
||||
<h4>
|
||||
Desactivar a compatibilidade de «SVG» (e, polo tanto, as dependencias de «Cairo, libSVG, e svg-cairo»: </h4>
|
||||
<blockquote>
|
||||
|
|
@ -614,6 +635,8 @@
|
|||
</blockquote>
|
||||
</blockquote>
|
||||
|
||||
<hr size="1" noshade width="75%" />
|
||||
|
||||
<h4>
|
||||
Desactivar a compatibilidade de «Pango» (e, polo tanto, as dependencias de «Pango, Cairo, etc.»: </h4>
|
||||
<blockquote>
|
||||
|
|
@ -626,6 +649,8 @@
|
|||
</blockquote>
|
||||
</blockquote>
|
||||
|
||||
<hr size="1" noshade width="75%" />
|
||||
|
||||
<h4>Desactivación do son en tempo de compilación:</h4>
|
||||
<blockquote>
|
||||
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>
|
||||
|
|
@ -636,18 +661,24 @@
|
|||
</blockquote>
|
||||
</blockquote>
|
||||
|
||||
<hr size="1" noshade width="75%" />
|
||||
|
||||
<h4>Outras opcións:</h4>
|
||||
<blockquote>
|
||||
<p>
|
||||
Outras opcións (p. ex.: rutas de instalación) poden ser anuladas; véxaas en «<code>Makefile</code>» para máis detalles. </p>
|
||||
</blockquote>
|
||||
|
||||
<hr size="1" noshade width="75%" />
|
||||
|
||||
<h4>Se se producen erros:</h4>
|
||||
<blockquote>
|
||||
<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>
|
||||
</blockquote>
|
||||
|
||||
<hr size="1" noshade width="75%" />
|
||||
|
||||
<h4>Instalar:</h4>
|
||||
<blockquote>
|
||||
<p>
|
||||
|
|
@ -730,6 +761,134 @@
|
|||
</blockquote>
|
||||
</blockquote>
|
||||
</blockquote>
|
||||
|
||||
<hr size="1" noshade />
|
||||
|
||||
<h3>
|
||||
<a name="compiling-macos" id="compiling-macos">
|
||||
Usuarios de macOS </a>
|
||||
</h3>
|
||||
<p style="font-size: small;">
|
||||
<em>
|
||||
21 de Setembro de 2021 Mark K. Kim <<a href="mailto:markuskimius@gmail.com">markuskimius@gmail.com</a>>
|
||||
</em>
|
||||
</p>
|
||||
|
||||
<blockquote>
|
||||
<p>
|
||||
Tux Paint 0.9.22 and earlier required building Tux Paint from the Xcode IDE. Starting with 0.9.23, however, Tux Paint for macOS is built as though it were a Linux application. </p>
|
||||
|
||||
<h4>Prerequisites</h4>
|
||||
<blockquote>
|
||||
<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>libsdl</code></li>
|
||||
<li><code>libsdl_image</code></li>
|
||||
<li><code>libsdl_mixer</code></li>
|
||||
<li><code>libsdl_pango</code></li>
|
||||
<li><code>libsdl_ttf</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>
|
||||
|
||||
<h5>libimagequant</h5>
|
||||
<blockquote>
|
||||
<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>
|
||||
$ git clone https://github.com/ImageOptim/libimagequant.git<br/>
|
||||
$ cd libimagequant<br/>
|
||||
$ ./configure --prefix=/opt/local<br/>
|
||||
$ make<br/>
|
||||
$ sudo make install
|
||||
</code>
|
||||
</blockquote>
|
||||
</p>
|
||||
|
||||
</blockquote>
|
||||
|
||||
<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>
|
||||
</blockquote>
|
||||
|
||||
<hr size="1" noshade width="75%" />
|
||||
|
||||
<h4>How to Build</h4>
|
||||
<blockquote>
|
||||
<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>. It also creates <code>TuxPaint.dmg</code> for distribution. </p>
|
||||
</blockquote>
|
||||
|
||||
<hr size="1" noshade width="75%" />
|
||||
|
||||
<h4>Known Issues</h4>
|
||||
<blockquote>
|
||||
<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. </li>
|
||||
</ul>
|
||||
</blockquote>
|
||||
|
||||
<hr size="1" noshade width="75%" />
|
||||
|
||||
<h4>Old Versions of macOS</h4>
|
||||
<blockquote>
|
||||
<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 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>
|
||||
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>
|
||||
It has been found that macOS can be installed onto the bootable media itself, so you can make the flash drive into a bootable installer then install the old macOS onto the same flash drive. </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>xcode-select --install</code>") but otherwise build Tux Paint using the same steps described in the earlier part of this document. </p>
|
||||
|
||||
</blockquote>
|
||||
|
||||
</blockquote>
|
||||
|
||||
</blockquote>
|
||||
|
||||
<hr size="2" noshade />
|
||||
|
|
@ -769,6 +928,8 @@
|
|||
</blockquote>
|
||||
</blockquote>
|
||||
|
||||
<hr size="1" noshade />
|
||||
|
||||
<h3>
|
||||
<a name="uninstalling-linux" id="uninstalling-linux">
|
||||
Linux </a>
|
||||
|
|
|
|||
|
|
@ -18,6 +18,7 @@
|
|||
| * Compiling and Installation |
|
||||
| * Windows のユーザー |
|
||||
| * Linux または Unix のユーザー |
|
||||
| * macOS のユーザー |
|
||||
| * Debugging |
|
||||
| * Uninstalling Tux Paint |
|
||||
| * Windows |
|
||||
|
|
@ -177,6 +178,8 @@ Compiling and Installation
|
|||
to the "MinGW 32bit (i686) toolchains" section if you need only a
|
||||
32bit build environment.
|
||||
|
||||
-------------------------------------------------------
|
||||
|
||||
MinGW 64bit (x86_64) toolchains
|
||||
|
||||
Within the MSYS2 shell, run the following command to install basic
|
||||
|
|
@ -247,6 +250,8 @@ Compiling and Installation
|
|||
to the "ImageMagick" section if you need only a 64bit build
|
||||
environment.
|
||||
|
||||
-------------------------------------------------------
|
||||
|
||||
MinGW 32bit (i686) toolchains
|
||||
|
||||
Within the MSYS2 shell, run the following command to install basic
|
||||
|
|
@ -313,6 +318,8 @@ Compiling and Installation
|
|||
$ cd SDL-1.2.15
|
||||
$ ./configure --prefix=/mingw32 && make && make install
|
||||
|
||||
-------------------------------------------------------
|
||||
|
||||
ImageMagick
|
||||
|
||||
ImageMagick is a compilation of command line tools to create, edit,
|
||||
|
|
@ -336,6 +343,8 @@ Compiling and Installation
|
|||
You can make this permanent by adding the above to your the BASH
|
||||
shell configuration file, "~/.bash_profile".
|
||||
|
||||
-------------------------------------------------------
|
||||
|
||||
Tux Paint
|
||||
|
||||
You can compile 64bit binaries using MSYS2 64bit shell, and 32bit
|
||||
|
|
@ -362,6 +371,8 @@ Compiling and Installation
|
|||
directory under "win32". You can start them by double-clicking their
|
||||
executable (.exe) files in the "bdist" directory.
|
||||
|
||||
-------------------------------------------------------
|
||||
|
||||
Building the Tux Paint Windows Installer:
|
||||
|
||||
Inno Setup is used to build executable installer for Tux Paint.
|
||||
|
|
@ -373,6 +384,8 @@ Compiling and Installation
|
|||
will find a "tuxpaint-X.Y.Z-win32-installer.exe" file in the same
|
||||
directory.
|
||||
|
||||
-------------------------------------------------------
|
||||
|
||||
Running the Tux Paint Windows Installer:
|
||||
|
||||
Double-click the Tux Paint installer executable (.EXE file) and
|
||||
|
|
@ -392,6 +405,8 @@ Compiling and Installation
|
|||
|
||||
At this point, you can click 'Install' to install Tux Paint!
|
||||
|
||||
-------------------------------------------------------
|
||||
|
||||
Changing the Settings Using the Shortcut:
|
||||
|
||||
To change program settings, right-click on the TuxPaint shortcut and
|
||||
|
|
@ -420,6 +435,8 @@ Compiling and Installation
|
|||
|
||||
When you have finished, click "OK."
|
||||
|
||||
-------------------------------------------------------
|
||||
|
||||
If Something Goes Wrong:
|
||||
|
||||
If, when you double-click on the shortcut to run Tux Paint, nothing
|
||||
|
|
@ -431,6 +448,8 @@ Compiling and Installation
|
|||
just be due to incorrect character-case (capital 'Z' instead of
|
||||
lowercase 'z') or a missing (or extra) '-' (dash).
|
||||
|
||||
----------------------------------------------------------------------
|
||||
|
||||
Linux または Unix のユーザー
|
||||
|
||||
Compiling:
|
||||
|
|
@ -444,6 +463,8 @@ Compiling and Installation
|
|||
|
||||
$ make
|
||||
|
||||
-------------------------------------------------------
|
||||
|
||||
Disabling SVG support (and hence Cairo, libSVG, and svg-cairo dependencies):
|
||||
|
||||
To disable SVG support (e.g., if your system is not currently
|
||||
|
|
@ -453,6 +474,8 @@ Compiling and Installation
|
|||
|
||||
$ make SVG_LIB= SVG_CFLAGS=
|
||||
|
||||
-------------------------------------------------------
|
||||
|
||||
Disabling Pango support (and hence Pango, Cairo, etc. dependencies):
|
||||
|
||||
Prior to version 0.9.18, Tux Paint used the libSDL_ttf library for
|
||||
|
|
@ -463,6 +486,8 @@ Compiling and Installation
|
|||
|
||||
$ make SDL_PANGO_LIB=
|
||||
|
||||
-------------------------------------------------------
|
||||
|
||||
Disabling Sound at Compile-time:
|
||||
|
||||
If you don't have a sound card, or would prefer to build the program
|
||||
|
|
@ -471,11 +496,15 @@ Compiling and Installation
|
|||
|
||||
$ make SDL_MIXER_LIB=
|
||||
|
||||
-------------------------------------------------------
|
||||
|
||||
Other options:
|
||||
|
||||
Various other options (e.g., installation paths) may be overridden;
|
||||
see them in "Makefile" for further details.
|
||||
|
||||
-------------------------------------------------------
|
||||
|
||||
If you get errors:
|
||||
|
||||
If you receive any errors during compile-time, make sure you have
|
||||
|
|
@ -485,6 +514,8 @@ Compiling and Installation
|
|||
packages as well, otherwise you won't be able to compile Tux Paint
|
||||
(and other programs) from source!
|
||||
|
||||
-------------------------------------------------------
|
||||
|
||||
Installng:
|
||||
|
||||
Assuming no fatal errors occured, you can now install the program so
|
||||
|
|
@ -562,6 +593,138 @@ Compiling and Installation
|
|||
|
||||
----------------------------------------------------------------------
|
||||
|
||||
macOS のユーザー
|
||||
|
||||
2021年9月21日 Mark K. Kim <markuskimius@gmail.com>
|
||||
|
||||
Tux Paint 0.9.22 and earlier required building Tux Paint from the
|
||||
Xcode IDE. Starting with 0.9.23, however, Tux Paint for macOS is built
|
||||
as though it were a Linux application.
|
||||
|
||||
Prerequisites
|
||||
|
||||
Although Tux Paint is built without the Xcode IDE, Xcode itself is
|
||||
still required to build Tux Paint. Download it from the App Store,
|
||||
and launch it once to accept its license agreements. You may also
|
||||
need to install the Xcode command line tools using the command:
|
||||
|
||||
xcode-select --install
|
||||
|
||||
Building Tux Paint also requires various libraries. We install them
|
||||
from MacPorts where possible, source code otherwise. Install
|
||||
MacPorts to the default /opt/local path according to the
|
||||
instructions found on their website: https://www.macports.org/
|
||||
* ImageMagick
|
||||
* cairo
|
||||
* fribidi
|
||||
* lbzip2
|
||||
* libimagequant^*
|
||||
* libpaper
|
||||
* libpng
|
||||
* librsvg
|
||||
* libsdl
|
||||
* libsdl_image
|
||||
* libsdl_mixer
|
||||
* libsdl_pango
|
||||
* libsdl_ttf
|
||||
* pkgconfig
|
||||
* zlib
|
||||
... but you should install any package that is required by the
|
||||
latest version of Tux Paint.
|
||||
|
||||
^* Not available from MacPorts as of this writing, see below.
|
||||
|
||||
libimagequant
|
||||
|
||||
libimagequant is not available from MacPorts as of this writing.
|
||||
It can be installed from the source code as follows. It should be
|
||||
installed to /opt/local (same as MacPorts) for the library to be
|
||||
included in TuxPaint.dmg.
|
||||
|
||||
$ git clone https://github.com/ImageOptim/libimagequant.git
|
||||
$ cd libimagequant
|
||||
$ ./configure --prefix=/opt/local
|
||||
$ make
|
||||
$ sudo make install
|
||||
|
||||
WARNING: 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.
|
||||
|
||||
-------------------------------------------------------
|
||||
|
||||
How to Build
|
||||
|
||||
Simply, run:
|
||||
|
||||
% make
|
||||
% make install
|
||||
|
||||
... to create the TuxPaint.app application bundle that can be run
|
||||
in-place or copied to /Applications. It also creates TuxPaint.dmg
|
||||
for distribution.
|
||||
|
||||
-------------------------------------------------------
|
||||
|
||||
Known Issues
|
||||
|
||||
* 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.
|
||||
|
||||
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.
|
||||
|
||||
-------------------------------------------------------
|
||||
|
||||
Old Versions of macOS
|
||||
|
||||
Some old versions of macOS can be downloaded from Apple's support
|
||||
page: https://support.apple.com/en-us/HT211683
|
||||
|
||||
macOS 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.
|
||||
|
||||
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.
|
||||
|
||||
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:
|
||||
https://support.apple.com/en-mide/HT201372
|
||||
|
||||
It has been found that macOS can be installed onto the bootable
|
||||
media itself, so you can make the flash drive into a bootable
|
||||
installer then install the old macOS onto the same flash drive.
|
||||
|
||||
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:
|
||||
https://developer.apple.com/download/more/
|
||||
|
||||
The list of macOS versions and the last version of Xcode compatible
|
||||
with them are laid out nicely on the Wikipedia page on Xcode:
|
||||
https://en.wikipedia.org/wiki/Xcode#Version_comparison_table
|
||||
|
||||
And because Xcode is being installed manually, you can skip the step
|
||||
to install the Xcode command line tools (do not run "xcode-select
|
||||
--install") but otherwise build Tux Paint using the same steps
|
||||
described in the earlier part of this document.
|
||||
|
||||
----------------------------------------------------------------------
|
||||
|
||||
Debugging
|
||||
|
||||
Debugging (to "STDOUT", e.g. to the terminal, or to a "stdout.txt" file,
|
||||
|
|
@ -589,6 +752,8 @@ Uninstalling Tux Paint
|
|||
It is also possible to use the entry "TuxPaint (remove only)" in the
|
||||
Control Panel Add/Remove programs section.
|
||||
|
||||
----------------------------------------------------------------------
|
||||
|
||||
Linux
|
||||
|
||||
Within the Tux Paint source directory (where you compiled Tux Paint),
|
||||
|
|
|
|||
|
|
@ -63,6 +63,9 @@
|
|||
<li>
|
||||
<a href="#compiling-linux">Linux または Unix のユーザー</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href="#compiling-macos">macOS のユーザー</a>
|
||||
</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
|
|
@ -271,6 +274,7 @@
|
|||
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>
|
||||
|
||||
<hr size="1" noshade width="75%" />
|
||||
<h4>
|
||||
<a name="64bit" id="64bit">
|
||||
MinGW 64bit (x86_64) toolchains </a>
|
||||
|
|
@ -368,6 +372,7 @@
|
|||
<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>
|
||||
<hr size="1" noshade width="75%" />
|
||||
<h4>
|
||||
<a name="32bit" id="32bit">
|
||||
MinGW 32bit (i686) toolchains </a>
|
||||
|
|
@ -462,6 +467,8 @@
|
|||
</blockquote>
|
||||
|
||||
|
||||
<hr size="1" noshade width="75%" />
|
||||
|
||||
<h4>
|
||||
<a name="imagemagick" id="imagemagick">ImageMagick</a>
|
||||
</h4>
|
||||
|
|
@ -484,6 +491,8 @@
|
|||
You can make this permanent by adding the above to your the BASH shell configuration file, "<code>~/.bash_profile</code>". </p>
|
||||
</blockquote>
|
||||
|
||||
<hr size="1" noshade width="75%" />
|
||||
|
||||
<h4>Tux Paint</h4>
|
||||
|
||||
<blockquote>
|
||||
|
|
@ -508,6 +517,8 @@
|
|||
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>
|
||||
</blockquote>
|
||||
|
||||
<hr size="1" noshade width="75%" />
|
||||
|
||||
<h4>Building the Tux Paint Windows Installer:</h4>
|
||||
<blockquote>
|
||||
|
||||
|
|
@ -519,6 +530,8 @@
|
|||
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>-win32-installer.exe</code>" file in the same directory. </p>
|
||||
</blockquote>
|
||||
|
||||
<hr size="1" noshade width="75%" />
|
||||
|
||||
<h4>Running the Tux Paint Windows Installer:</h4>
|
||||
<blockquote>
|
||||
<p>
|
||||
|
|
@ -536,6 +549,8 @@
|
|||
At this point, you can click 'Install' to install Tux Paint! </p>
|
||||
</blockquote>
|
||||
|
||||
<hr size="1" noshade width="75%" />
|
||||
|
||||
<h4>Changing the Settings Using the Shortcut:</h4>
|
||||
<blockquote>
|
||||
<p>
|
||||
|
|
@ -572,6 +587,8 @@
|
|||
When you have finished, click "OK." </p>
|
||||
</blockquote>
|
||||
|
||||
<hr size="1" noshade width="75%" />
|
||||
|
||||
<h4>If Something Goes Wrong:</h4>
|
||||
<blockquote>
|
||||
<p>
|
||||
|
|
@ -582,6 +599,8 @@
|
|||
</blockquote>
|
||||
</blockquote>
|
||||
|
||||
<hr size="1" noshade />
|
||||
|
||||
<h3>
|
||||
<a name="compiling-linux" id="compiling-linux">
|
||||
Linux または Unix のユーザー </a>
|
||||
|
|
@ -602,6 +621,8 @@
|
|||
</blockquote>
|
||||
</blockquote>
|
||||
|
||||
<hr size="1" noshade width="75%" />
|
||||
|
||||
<h4>
|
||||
Disabling SVG support (and hence Cairo, libSVG, and svg-cairo dependencies): </h4>
|
||||
<blockquote>
|
||||
|
|
@ -614,6 +635,8 @@
|
|||
</blockquote>
|
||||
</blockquote>
|
||||
|
||||
<hr size="1" noshade width="75%" />
|
||||
|
||||
<h4>
|
||||
Disabling Pango support (and hence Pango, Cairo, etc. dependencies): </h4>
|
||||
<blockquote>
|
||||
|
|
@ -626,6 +649,8 @@
|
|||
</blockquote>
|
||||
</blockquote>
|
||||
|
||||
<hr size="1" noshade width="75%" />
|
||||
|
||||
<h4>Disabling Sound at Compile-time:</h4>
|
||||
<blockquote>
|
||||
If you don't have a sound card, or would prefer to build the program with no sound support (and therefore without a the <code>SDL_mixer</code> dependency), you can run "<code>make</code>" with "<code>SDL_MIXER_LIB=</code>" added: </p>
|
||||
|
|
@ -636,18 +661,24 @@
|
|||
</blockquote>
|
||||
</blockquote>
|
||||
|
||||
<hr size="1" noshade width="75%" />
|
||||
|
||||
<h4>Other options:</h4>
|
||||
<blockquote>
|
||||
<p>
|
||||
Various other options (e.g., installation paths) may be overridden; see them in "<code>Makefile</code>" for further details. </p>
|
||||
</blockquote>
|
||||
|
||||
<hr size="1" noshade width="75%" />
|
||||
|
||||
<h4>If you get errors:</h4>
|
||||
<blockquote>
|
||||
<p>
|
||||
If you receive any errors during compile-time, make sure you have the appropriate libraries installed (see above). If using packaged versions of the libraries (e.g., RPMs under RedHat or DEBs under Debian), be sure to get the corresponding "<code>-dev</code>" or "<code>-devel</code>" packages as well, otherwise you won't be able to compile Tux Paint (and other programs) from source! </p>
|
||||
</blockquote>
|
||||
|
||||
<hr size="1" noshade width="75%" />
|
||||
|
||||
<h4>Installng:</h4>
|
||||
<blockquote>
|
||||
<p>
|
||||
|
|
@ -730,6 +761,134 @@
|
|||
</blockquote>
|
||||
</blockquote>
|
||||
</blockquote>
|
||||
|
||||
<hr size="1" noshade />
|
||||
|
||||
<h3>
|
||||
<a name="compiling-macos" id="compiling-macos">
|
||||
macOS のユーザー </a>
|
||||
</h3>
|
||||
<p style="font-size: small;">
|
||||
<em>
|
||||
2021年9月21日 Mark K. Kim <<a href="mailto:markuskimius@gmail.com">markuskimius@gmail.com</a>>
|
||||
</em>
|
||||
</p>
|
||||
|
||||
<blockquote>
|
||||
<p>
|
||||
Tux Paint 0.9.22 and earlier required building Tux Paint from the Xcode IDE. Starting with 0.9.23, however, Tux Paint for macOS is built as though it were a Linux application. </p>
|
||||
|
||||
<h4>Prerequisites</h4>
|
||||
<blockquote>
|
||||
<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>libsdl</code></li>
|
||||
<li><code>libsdl_image</code></li>
|
||||
<li><code>libsdl_mixer</code></li>
|
||||
<li><code>libsdl_pango</code></li>
|
||||
<li><code>libsdl_ttf</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>
|
||||
|
||||
<h5>libimagequant</h5>
|
||||
<blockquote>
|
||||
<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>
|
||||
$ git clone https://github.com/ImageOptim/libimagequant.git<br/>
|
||||
$ cd libimagequant<br/>
|
||||
$ ./configure --prefix=/opt/local<br/>
|
||||
$ make<br/>
|
||||
$ sudo make install
|
||||
</code>
|
||||
</blockquote>
|
||||
</p>
|
||||
|
||||
</blockquote>
|
||||
|
||||
<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>
|
||||
</blockquote>
|
||||
|
||||
<hr size="1" noshade width="75%" />
|
||||
|
||||
<h4>How to Build</h4>
|
||||
<blockquote>
|
||||
<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>. It also creates <code>TuxPaint.dmg</code> for distribution. </p>
|
||||
</blockquote>
|
||||
|
||||
<hr size="1" noshade width="75%" />
|
||||
|
||||
<h4>Known Issues</h4>
|
||||
<blockquote>
|
||||
<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. </li>
|
||||
</ul>
|
||||
</blockquote>
|
||||
|
||||
<hr size="1" noshade width="75%" />
|
||||
|
||||
<h4>Old Versions of macOS</h4>
|
||||
<blockquote>
|
||||
<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 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>
|
||||
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>
|
||||
It has been found that macOS can be installed onto the bootable media itself, so you can make the flash drive into a bootable installer then install the old macOS onto the same flash drive. </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>xcode-select --install</code>") but otherwise build Tux Paint using the same steps described in the earlier part of this document. </p>
|
||||
|
||||
</blockquote>
|
||||
|
||||
</blockquote>
|
||||
|
||||
</blockquote>
|
||||
|
||||
<hr size="2" noshade />
|
||||
|
|
@ -769,6 +928,8 @@
|
|||
</blockquote>
|
||||
</blockquote>
|
||||
|
||||
<hr size="1" noshade />
|
||||
|
||||
<h3>
|
||||
<a name="uninstalling-linux" id="uninstalling-linux">
|
||||
Linux </a>
|
||||
|
|
|
|||
138
macos/README.txt
138
macos/README.txt
|
|
@ -1,137 +1 @@
|
|||
WHAT IS THIS
|
||||
------------
|
||||
This document describes how to build Tux Paint 0.9.23 or later on macOS.
|
||||
|
||||
Tux Paint 0.9.22 and earlier required building Tux Paint from the Xcode IDE.
|
||||
Starting with 0.9.23, however, Tux Paint for macOS is built as though it were a
|
||||
Linux application.
|
||||
|
||||
|
||||
PREREQUISITES
|
||||
-------------
|
||||
Although Tux Paint is built without the Xcode IDE, Xcode itself is still required
|
||||
to build Tux Paint. Download it from the App Store, and launch it once to
|
||||
accept its license agreements. You may also need to install the Xcode command
|
||||
line tools using the command:
|
||||
|
||||
xcode-select --install
|
||||
|
||||
Building Tux Paint also requires various libraries. We install them from
|
||||
MacPorts where possible, source code otherwise. Install MacPorts to the
|
||||
default /opt/local path according to the instructions found on their website:
|
||||
|
||||
https://www.macports.org/
|
||||
|
||||
As of this writing, the following packages need to be installed:
|
||||
|
||||
ImageMagick
|
||||
cairo
|
||||
fribidi
|
||||
lbzip2
|
||||
libimagequant*
|
||||
libpaper
|
||||
libpng
|
||||
librsvg
|
||||
libsdl
|
||||
libsdl_image
|
||||
libsdl_mixer
|
||||
libsdl_pango
|
||||
libsdl_ttf
|
||||
pkgconfig
|
||||
zlib
|
||||
|
||||
* - Not available from MacPorts as of this writing, see below
|
||||
|
||||
... but you should install any package that is required by the latest version of
|
||||
Tux Paint.
|
||||
|
||||
libimagequant
|
||||
-------------
|
||||
libimagequant is not available from MacPorts as of this writing. It can be
|
||||
installed from the source code as follows. It should be installed to
|
||||
/opt/local (same as MacPorts) for the library to be included in TuxPaint.dmg.
|
||||
|
||||
$ git clone https://github.com/ImageOptim/libimagequant.git
|
||||
$ cd libimagequant
|
||||
$ ./configure --prefix=/opt/local
|
||||
$ make
|
||||
$ sudo make install
|
||||
|
||||
|
||||
*** WARNING ***
|
||||
---------------
|
||||
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.
|
||||
|
||||
|
||||
HOW TO BUILD
|
||||
------------
|
||||
Simply, run:
|
||||
|
||||
% make
|
||||
% make install
|
||||
|
||||
... to create the TuxPaint.app application bundle that can be run in-place or
|
||||
copied to /Applications. It also creates TuxPaint.dmg for distribution.
|
||||
|
||||
|
||||
KNOWN ISSUES
|
||||
------------
|
||||
- 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.
|
||||
|
||||
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.
|
||||
|
||||
|
||||
OLD VERSIONS OF MACOS
|
||||
---------------------
|
||||
Some old versions of macOS can be downloaded from Apple's support page:
|
||||
|
||||
https://support.apple.com/en-us/HT211683
|
||||
|
||||
macOS 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.
|
||||
|
||||
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.
|
||||
|
||||
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:
|
||||
|
||||
https://support.apple.com/en-mide/HT201372
|
||||
|
||||
I found that macOS can be installed onto the bootable media itself, so you can
|
||||
make the flash drive into a bootable installer then install the old macOS onto
|
||||
the same flash drive.
|
||||
|
||||
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:
|
||||
|
||||
https://developer.apple.com/download/more/
|
||||
|
||||
The list of macOS versions and the last version of Xcode compatible with them
|
||||
are laid out nicely on the Wikipedia page on Xcode:
|
||||
|
||||
https://en.wikipedia.org/wiki/Xcode#Version_comparison_table
|
||||
|
||||
And because Xcode is being installed manually, you can skip the step to install the Xcode
|
||||
command line tools (do not run `xcode-select --install`) but otherwise build Tux Paint
|
||||
using the same steps described in the earlier part of this document.
|
||||
|
||||
|
||||
January 9, 2021
|
||||
Mark K. Kim <markuskimius@gmail.com>
|
||||
See INSTALL.txt or INSTALL.html, in "../docs"
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue