diff --git a/docs/en/INSTALL.txt b/docs/en/INSTALL.txt index acd74cc27..071d1b387 100644 --- a/docs/en/INSTALL.txt +++ b/docs/en/INSTALL.txt @@ -5,853 +5,783 @@ Copyright © 2002-2022 by various contributors; see AUTHORS.txt. https://tuxpaint.org/ - January 20, 2022 + March 31, 2022 - ---------------------------------------------------------------------- + +----------------------------------------------------+ + |Table of Contents | + |----------------------------------------------------| + | * Requirements | + | * Simple DirectMedia Layer library (libSDL) | + | * Other Libraries | + | * Compiling and Installation | + | * Windows | + | * Linux/Unix | + | * macOS | + | * Debugging | + | * Uninstalling Tux Paint | + | * Windows | + | * macOS | + | * Linux | + +----------------------------------------------------+ - +----------------------------------------------------+ - |Table of Contents | - |----------------------------------------------------| - | * Requirements | - | * Simple DirectMedia Layer library (libSDL) | - | * Other Libraries | - | * Compiling and Installation | - | * Windows Users | - | * Linux/Unix Users | - | * macOS Users | - | * Debugging | - | * Uninstalling Tux Paint | - | * Windows | - | * macOS | - | * Linux | - +----------------------------------------------------+ + Requirements - ---------------------------------------------------------------------- +Simple DirectMedia Layer library (libSDL) -Requirements + Tux Paint requires the Simple DirectMedia Layer Library (libSDL), an Open + Source multimedia programming library available under the GNU Lesser + General Public License (LGPL). - Simple DirectMedia Layer library (libSDL) + Along with libSDL, Tux Paint depends on a number of other SDL 'helper' + libraries: SDL_Image (for graphics files), SDL_gfx (for some graphical + functions, like rotation), SDL_TTF and (optionally) SDL_Pango (for True + Type Font support) and, optionally, SDL_Mixer (for sound effects). - Tux Paint requires the Simple DirectMedia Layer Library (libSDL), an - Open Source multimedia programming library available under the GNU - Lesser General Public License (LGPL). + Linux/Unix - Along with libSDL, Tux Paint depends on a number of other SDL 'helper' - libraries: SDL_Image (for graphics files), SDL_gfx (for some graphical - functions, like rotation), SDL_TTF and (optionally) SDL_Pango (for - True Type Font support) and, optionally, SDL_Mixer (for sound - effects). + The SDL libraries are available as source-code, or as RPM or + Debian packages for various distributions of Linux. They can be + downloaded from: - Linux/Unix Users: + * libSDL: http://www.libsdl.org/ + * SDL_Image: http://www.libsdl.org/projects/SDL_image/ + * SDL_gfx: + https://www.ferzkopp.net/wordpress/2016/01/02/sdl_gfx-sdl2_gfx/ + (https://sourceforge.net/projects/sdlgfx/) + * SDL_TTF: http://www.libsdl.org/projects/SDL_ttf/ + * SDL_Pango: http://sourceforge.net/projects/sdlpango/ + (optional) + * SDL_Mixer: http://www.libsdl.org/projects/SDL_mixer/ + (optional) - The SDL libraries are available as source-code, or as RPM or Debian - packages for various distributions of Linux. They can be downloaded - from: + They are also typically available along with your Linux + distribution (e.g. on an installation media, or available via + package maintainance software like Debian's "apt"). - * libSDL: http://www.libsdl.org/ - * SDL_Image: http://www.libsdl.org/projects/SDL_image/ - * SDL_gfx: - https://www.ferzkopp.net/wordpress/2016/01/02/sdl_gfx-sdl2_gfx/ - (https://sourceforge.net/projects/sdlgfx/) - * SDL_TTF: http://www.libsdl.org/projects/SDL_ttf/ - * SDL_Pango: http://sourceforge.net/projects/sdlpango/ (optional) - * SDL_Mixer: http://www.libsdl.org/projects/SDL_mixer/ (optional) - - They are also typically available along with your Linux distribution - (e.g. on an installation media, or available via package - maintainance software like Debian's "apt"). - - Note: When installing libraries from packages, be sure to ALSO - install the development versions of the packages. (For example, - install both "SDL-1.2.4.rpm" and "SDL-1.2.4-devel.rpm".) + 💡 Note: When installing libraries from packages, be sure to ALSO + install the development versions of the packages. (For example, + install both "SDL-1.2.4.rpm" and "SDL-1.2.4-devel.rpm".) Other Libraries - Tux Paint also takes advantage of a number of other free, LGPL'd - libraries. Under Linux, just like SDL, they should either already be - installed, or are readily available for installation as part of your - Linux distribution. + Tux Paint also takes advantage of a number of other free, LGPL'd + libraries. Under Linux, just like SDL, they should either already be + installed, or are readily available for installation as part of your Linux + distribution. - libPNG + libPNG - Tux Paint uses PNG (Portable Network Graphics) format for its data - files. SDL_image will require libPNG be installed. + Tux Paint uses PNG (Portable Network Graphics) format for its data + files. SDL_image will require libPNG be installed. - http://www.libpng.org/pub/png/libpng.html + http://www.libpng.org/pub/png/libpng.html - gettext + gettext - Tux Paint uses your system's locale settings along with the - "gettext" library to support various languages (e.g., Spanish). - You'll need the gettext library installed. + Tux Paint uses your system's locale settings along with the + "gettext" library to support various languages (e.g., Spanish). + You'll need the gettext library installed. - http://www.gnu.org/software/gettext/ + http://www.gnu.org/software/gettext/ - libpaper (Linux/Unix only) + libpaper (Linux/Unix only) - As of Tux Paint 0.9.17, Tux Paint can determine your system's - default paper size (e.g., A4 or Letter), or can be told to use a - particular paper size, thanks to "libpaper". + As of Tux Paint 0.9.17, Tux Paint can determine your system's + default paper size (e.g., A4 or Letter), or can be told to use a + particular paper size, thanks to "libpaper". - https://github.com/naota/libpaper + https://github.com/naota/libpaper - FriBiDi + FriBiDi - Tux Paint's "Text" and also "Label" tools support bidirectional - languages, thanks to the "FriBiDi" library. + Tux Paint's "Text" and also "Label" tools support bidirectional + languages, thanks to the "FriBiDi" library. - http://fribidi.org/ + http://fribidi.org/ - SVG graphics support + SVG graphics support - As of Tux Paint 0.9.17, Tux Paint can load SVG (Scalable Vector - Graphics) images as stamps. Two sets of libraries are supported, and - SVG support can be completely disabled (via "make SVG_LIB:=") + As of Tux Paint 0.9.17, Tux Paint can load SVG (Scalable Vector + Graphics) images as stamps. Two sets of libraries are supported, + and SVG support can be completely disabled (via "make SVG_LIB:=") - librsvg-2 & libCairo2 (newer libraries) + librsvg-2 & libCairo2 (newer libraries) + * libRSVG 2: http://librsvg.sourceforge.net/ + * Cairo 2: http://www.cairographics.org/ + * These also depend on the following: + * GdkPixbuf & GLib: http://www.gtk.org/ + * Pango: http://www.pango.org/ - * libRSVG 2: http://librsvg.sourceforge.net/ - * Cairo 2: http://www.cairographics.org/ - * These also depend on the following: - * GdkPixbuf & GLib: http://www.gtk.org/ - * Pango: http://www.pango.org/ + Older SVG libraries + * libcairo1, libsvg1, & libsvg-cairo1: + http://www.cairographics.org/ + * These also depend on the following: + * libxml2: + https://gitlab.gnome.org/GNOME/libxml2 - Older SVG libraries + Animated GIF Export feature - * libcairo1, libsvg1, & libsvg-cairo1: - http://www.cairographics.org/ - * These also depend on the following: - * libxml2: https://gitlab.gnome.org/GNOME/libxml2 + To support export of animated GIFs (slideshows), the + "libimagequant" library (from the "pngquant2" project) is + required. - Animated GIF Export feature + https://github.com/ImageOptim/libimagequant - To support export of animated GIFs (slideshows), the "libimagequant" - library (from the "pngquant2" project) is required. + NetPBM Tools (optional) No longer used, by default - https://github.com/ImageOptim/libimagequant + 📜 Under Linux and Unix, earlier versions of Tux Paint used the + NetPBM tools to assist with printing. (A PNG is generated by Tux + Paint, and converted into a PostScript using the 'pngtopnm' and + 'pnmtops' NetPBM command-line tools.) - NetPBM Tools (optional) No longer used, by default + http://netpbm.sourceforge.net/ - Under Linux and Unix, earlier versions of Tux Paint used the NetPBM - tools to assist with printing. (A PNG is generated by Tux Paint, and - converted into a PostScript using the 'pngtopnm' and 'pnmtops' - NetPBM command-line tools.) + Compiling and Installation - http://netpbm.sourceforge.net/ + Tux Paint is released under the GNU General Public License (GPL) (see + "COPYING.txt" for details), and therefore the 'source code' to the program + is available freely. - ---------------------------------------------------------------------- +Windows -Compiling and Installation + November 3, 2021 Shin-ichi TOYAMA dolphin6k@wmail.plala.or.jp + - Tux Paint is released under the GNU General Public License (GPL) (see - "COPYING.txt" for details), and therefore the 'source code' to the - program is available freely. + Compiling Set-Up - Windows Users + As of February 2005 (starting with Tux Paint 0.9.15), the "Makefile" + includes support for building on a Windows system using MinGW/MSYS + (https://sourceforge.net/projects/msys2/). - November 3, 2021 Shin-ichi TOYAMA dolphin6k@wmail.plala.or.jp - + Many tools and libraries are required to build Tux Paint. The package + management system "pacman" helps you install them automatically solving + complicated dependencies. - Compiling Set-Up + Download the latest MSYS2 environment from + https://sourceforge.net/projects/msys2/files/Base/ and install it where + you'd like (the default is "C:\msys64") - As of February 2005 (starting with Tux Paint 0.9.15), the "Makefile" - includes support for building on a Windows system using MinGW/MSYS - (https://sourceforge.net/projects/msys2/). + Open the MSYS2 shell from the "Start Menu" -> "MSYS2 64bit" -> "MSYS2 + MSYS" and execute following command (press [Enter] or [Return] to accept + the defaults for all questions): - Many tools and libraries are required to build Tux Paint. The - package management system "pacman" helps you install them - automatically solving complicated dependencies. + pacman -Syu - Download the latest MSYS2 environment from - https://sourceforge.net/projects/msys2/files/Base/ and install it - where you'd like (the default is "C:\msys64") + This will update core system and the window will close automatically. + Repeat the steps above one more time to finish the remaining update + process. - Open the MSYS2 shell from the "Start Menu" -> "MSYS2 64bit" -> - "MSYS2 MSYS" and execute following command (press [Enter] or - [Return] to accept the defaults for all questions): + Within the MSYS2 shell, run the following command to install basic + development tools: - pacman -Syu + pacman -S base-devel msys2-devel git - This will update core system and the window will close - automatically. Repeat the steps above one more time to finish the - remaining update process. - - Within the MSYS2 shell, run the following command to install basic - development tools: - - pacman -S base-devel msys2-devel git - - Proceed to the next "MinGW 64bit (x86_64) toolchains" section, or skip - to the "MinGW 32bit (i686) toolchains" section if you need only a - 32bit build environment. + Proceed to the next "MinGW 64bit (x86_64) toolchains" section, or skip 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 - 64bit development tools: + Within the MSYS2 shell, run the following command to install basic 64bit + development tools: - pacman -S mingw-w64-x86_64-toolchain + pacman -S mingw-w64-x86_64-toolchain 64bit (x86_64) dependency libraries for Tux Paint - You can install tools and libraries required for compiling Tux Paint - on MSYS2/MINGW using "pacman" except for SDL_Pango. + You can install tools and libraries required for compiling Tux Paint on + MSYS2/MINGW using "pacman" except for SDL_Pango. - "ntldd" is a small tool which examine windows executable files to - list Dynamic Link Library (.dll) files they depends on. Tux Paint's - packaging process for binary distribution uses it to find required - .dll files. + "ntldd" is a small tool which examine windows executable files to list + Dynamic Link Library (.dll) files they depends on. Tux Paint's packaging + process for binary distribution uses it to find required .dll files. - FLTK is a cross-platform GUI toolkit used by "Tux Paint Config.". - You can skip installing it if you are only building "Tux Paint". + FLTK is a cross-platform GUI toolkit used by "Tux Paint Config.". You can + skip installing it if you are only building "Tux Paint". - $ pacman -S mingw-w64-x86_64-SDL_{image,mixer,ttf,gfx} - $ pacman -S mingw-w64-x86_64-librsvg - $ pacman -S mingw-w64-x86_64-fribidi - $ pacman -S mingw-w64-x86_64-libimagequant - $ pacman -S mingw-w64-x86_64-fltk - $ pacman -S mingw-w64-x86_64-ntldd-git + $ pacman -S mingw-w64-x86_64-SDL_{image,mixer,ttf,gfx} + $ pacman -S mingw-w64-x86_64-librsvg + $ pacman -S mingw-w64-x86_64-fribidi + $ pacman -S mingw-w64-x86_64-libimagequant + $ pacman -S mingw-w64-x86_64-fltk + $ pacman -S mingw-w64-x86_64-ntldd-git - Note: Close the shell before proceeding to the remaining process. + 💡 Note: Close the shell before proceeding to the remaining process. Install SDL_Pango on the 64bit environment - SDL_Pango should be installed manually. + SDL_Pango should be installed manually. - This time, use the MinGW "64bit" shell. Open the shell from the - "Start Menu" -> "MSYS2 64bit" -> "MSYS2 MinGW 64-bit" + This time, use the MinGW "64bit" shell. Open the shell from the "Start + Menu" -> "MSYS2 64bit" -> "MSYS2 MinGW 64-bit" SDL_Pango - At first, you have to prepare source tar-ball and a required patch - in the same directory. + At first, you have to prepare source tar-ball and a required patch in the + same directory. + * Download source tar-ball of SDL_Pango-0.1.2 from SDL_Pango's page on + Sourceforge.net. + * Download a patch file from John Popplewell's "Tux Paint - MinGW/MSYS + build instructions" webpage. (This adds some extra (required) + functionality to SDL_Pango.) - * Download source tar-ball of SDL_Pango-0.1.2 from SDL_Pango's - page on Sourceforge.net. - * Download a patch file from John Popplewell's "Tux Paint - - MinGW/MSYS build instructions" webpage. (This adds some extra - (required) functionality to SDL_Pango.) + Build and install SDL_Pango as follows. - Build and install SDL_Pango as follows. + $ tar zxvf SDL_Pango-0.1.2.tar.gz + $ cd SDL_Pango-0.1.2/ + $ patch -p0 < ../SDL_Pango-configure-extra-api.patch + $ ./configure --prefix=/mingw64 && make && make install - $ tar zxvf SDL_Pango-0.1.2.tar.gz - $ cd SDL_Pango-0.1.2/ - $ patch -p0 < ../SDL_Pango-configure-extra-api.patch - $ ./configure --prefix=/mingw64 && make && make install - - Proceed to the next "MinGW 32bit (i686) toolchains" section, or skip - to the "ImageMagick" section if you need only a 64bit build - environment. + Proceed to the next "MinGW 32bit (i686) toolchains" section, or skip 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 - 32bit development tools: + Within the MSYS2 shell, run the following command to install basic 32bit + development tools: - pacman -S mingw-w64-i686-toolchain + pacman -S mingw-w64-i686-toolchain 32bit (i686) dependency libraries for Tux Paint - You can install tools and libraries required for compiling Tux Paint - on MSYS2/MINGW using "pacman" except for SDL_Pango. + You can install tools and libraries required for compiling Tux Paint on + MSYS2/MINGW using "pacman" except for SDL_Pango. - "ntldd" is a small tool which examine windows executable files to - list Dynamic Link Library (.dll) files they depends on. Tux Paint's - packaging process for binary distribution uses it to find required - .dll files. + "ntldd" is a small tool which examine windows executable files to list + Dynamic Link Library (.dll) files they depends on. Tux Paint's packaging + process for binary distribution uses it to find required .dll files. - FLTK is a cross-platform GUI toolkit used by "Tux Paint Config.". - You can skip installing it if you are only building "Tux Paint". + FLTK is a cross-platform GUI toolkit used by "Tux Paint Config.". You can + skip installing it if you are only building "Tux Paint". - $ pacman -S mingw-w64-i686-SDL_{image,mixer,ttf,gfx} - $ pacman -S mingw-w64-i686-librsvg - $ pacman -S mingw-w64-i686-fribidi - $ pacman -S mingw-w64-i686-libimagequant - $ pacman -S mingw-w64-i686-fltk - $ pacman -S mingw-w64-i686-ntldd-git + $ pacman -S mingw-w64-i686-SDL_{image,mixer,ttf,gfx} + $ pacman -S mingw-w64-i686-librsvg + $ pacman -S mingw-w64-i686-fribidi + $ pacman -S mingw-w64-i686-libimagequant + $ pacman -S mingw-w64-i686-fltk + $ pacman -S mingw-w64-i686-ntldd-git - Note: Close the shell before proceeding to the remaining process. + 💡 Note: Close the shell before proceeding to the remaining process. Install SDL_Pango on the 32bit environment - SDL_Pango should be installed manually. + SDL_Pango should be installed manually. - This time, use the MinGW "32bit" shell. Open the shell from the - "Start Menu" -> "MSYS2 64bit" -> "MSYS2 MinGW 32-bit" + This time, use the MinGW "32bit" shell. Open the shell from the "Start + Menu" -> "MSYS2 64bit" -> "MSYS2 MinGW 32-bit" SDL_Pango - At first, you have to prepare source tar-ball and a required patch - in the same directory. + At first, you have to prepare source tar-ball and a required patch in the + same directory. + * Download source tar-ball of SDL_Pango-0.1.2 from SDL_Pango's page on + Sourceforge.net. + * Download a patch file from John Popplewell's "Tux Paint - MinGW/MSYS + build instructions" webpage. (This adds some extra (required) + functionality to SDL_Pango.) - * Download source tar-ball of SDL_Pango-0.1.2 from SDL_Pango's - page on Sourceforge.net. - * Download a patch file from John Popplewell's "Tux Paint - - MinGW/MSYS build instructions" webpage. (This adds some extra - (required) functionality to SDL_Pango.) + Build and install SDL_Pango as follows. - Build and install SDL_Pango as follows. + $ tar zxvf SDL_Pango-0.1.2.tar.gz + $ cd SDL_Pango-0.1.2/ + $ patch -p0 < ../SDL_Pango-configure-extra-api.patch + $ ./configure --prefix=/mingw32 && make && make install - $ tar zxvf SDL_Pango-0.1.2.tar.gz - $ cd SDL_Pango-0.1.2/ - $ patch -p0 < ../SDL_Pango-configure-extra-api.patch - $ ./configure --prefix=/mingw32 && make && make install + ImageMagick - ------------------------------------------------------- + ImageMagick is a compilation of command line tools to create, edit, + compose, or convert bitmap images supporting quite a large number of image + formats. Tux Paint uses two functions ("convert" and "composite") in it to + generate thumbnails for startar images and templates during the build + process. - ImageMagick + Using official binary release available from "Windows Binary Release" is + recommended, due to the commands installed with "pacman" on MinGW/MSYS not + working as expected! - ImageMagick is a compilation of command line tools to create, edit, - compose, or convert bitmap images supporting quite a large number of - image formats. Tux Paint uses two functions ("convert" and - "composite") in it to generate thumbnails for startar images and - templates during the build process. + Do not forget to enable "Install legacy utilities (e.g. convert)" while + installing it, because Tux Paint's build process uses them. - Using official binary release available from "Windows Binary - Release" is recommended, due to the commands installed with "pacman" - on MinGW/MSYS not working as expected! + Add the path to the directory in which ImageMagick is installed at the top + of your "PATH" environment variable. For example: - Do not forget to enable "Install legacy utilities (e.g. convert)" - while installing it, because Tux Paint's build process uses them. + $ export PATH=/c/Program\ Files/ImageMagick-7.0.10-Q16-HDRI:$PATH - Add the path to the directory in which ImageMagick is installed at - the top of your "PATH" environment variable. For example: + You can make this permanent by adding the above to your the BASH shell + configuration file, "~/.bash_profile". - $ export PATH=/c/Program\ Files/ImageMagick-7.0.10-Q16-HDRI:$PATH + Tux Paint - You can make this permanent by adding the above to your the BASH - shell configuration file, "~/.bash_profile". + You can compile 64bit binaries using MSYS2 64bit shell, and 32bit binaries + using MSYS2 32bit shell, respectively. - ------------------------------------------------------- + * Select "MSYS2 64bit" -> "MSYS2 MinGW 64-bit" from the "Start Menu" to + open the 64bit shell. + * Select "MSYS2 64bit" -> "MSYS2 MinGW 32-bit" from the "Start Menu" to + open the 32bit shell. - Tux Paint + Compile Tux Paint with the following command: - You can compile 64bit binaries using MSYS2 64bit shell, and 32bit - binaries using MSYS2 32bit shell, respectively. + $ make bdist-win32 - * Select "MSYS2 64bit" -> "MSYS2 MinGW 64-bit" from the "Start - Menu" to open the 64bit shell. - * Select "MSYS2 64bit" -> "MSYS2 MinGW 32-bit" from the "Start - Menu" to open the 32bit shell. + 💡 Note: At this point, you will want to build "Tux Paint Config." for + Windows, so it can be included along with "Tux Paint", if you're making an + official (or test) release. The build process will look for it in a + directory named "tuxpaint-config" (with no version number, e.g., + "tuxpaint-config-X.Y.Z"). See "Tux Paint Config."'s INSTALL.txt + documentation for details. - Compile Tux Paint with the following command: + All the files needed for starting Tux Paint (and Tux Paint Config.) are + collected in the directory for binary distribution "bdist" directory under + "win32". You can start them by double-clicking their executable (.exe) + files in the "bdist" directory. - $ make bdist-win32 + Building the Tux Paint Windows Installer - Note: At this point, you will want to build "Tux Paint Config." for - Windows, so it can be included along with "Tux Paint", if you're - making an official (or test) release. The build process will look - for it in a directory named "tuxpaint-config" (with no version - number, e.g., "tuxpaint-config-X.Y.Z"). See "Tux Paint Config."'s - INSTALL.txt documentation for details. + Inno Setup is used to build executable installer for Tux Paint. Therefore + you have to install it in the first place. - All the files needed for starting Tux Paint (and Tux Paint Config.) - are collected in the directory for binary distribution "bdist" - directory under "win32". You can start them by double-clicking their - executable (.exe) files in the "bdist" directory. + Inno Setup officially supports translations for only about 20 languages. + However, one of the great points of Tux Paint is it supports so many + languages. Therefore, the set up script "tuxpaint.iss" to build the + installer is written to use much more translations including unofficial + one which are available on "Inno Setup Translations". You have to download + translation files (.isl) required and put them in "Languages" directory + under the directory in which Inno Setup is installed. - ------------------------------------------------------- + Before building an installer, edit the "tuxpaint.iss" file and enable one + of the lines starting with "#define BuildTarget=", depending on the + architecture of the installer you want to create. - Building the Tux Paint Windows Installer: + Then, you can easily build an executable installer by right-clicking on + the "tuxpaint.iss" icon in the "win32" directory and selecting "Compile" + on the list. It will run for a while, and eventually you will find a + "tuxpaint-X.Y.Z-windows--installer.exe" file in the same directory. - Inno Setup is used to build executable installer for Tux Paint. - Therefore you have to install it in the first place. + Running the Tux Paint Windows Installer - Inno Setup officially supports translations for only about 20 - languages. However, one of the great points of Tux Paint is it - supports so many languages. Therefore, the set up script - "tuxpaint.iss" to build the installer is written to use much more - translations including unofficial one which are available on "Inno - Setup Translations". You have to download translation files (.isl) - required and put them in "Languages" directory under the directory - in which Inno Setup is installed. + Double-click the Tux Paint installer executable (.EXE file) and follow the + instructions. - Before building an installer, edit the "tuxpaint.iss" file and - enable one of the lines starting with "#define BuildTarget=", - depending on the architecture of the installer you want to create. + First, you will be asked to read the license. (It is the GNU General + Public License (GPL), which is also available as "COPYING.txt".) - Then, you can easily build an executable installer by right-clicking - on the "tuxpaint.iss" icon in the "win32" directory and selecting - "Compile" on the list. It will run for a while, and eventually you - will find a "tuxpaint-X.Y.Z-windows--installer.exe" file in - the same directory. + You will then be asked whether you want to install shortcuts to Tux Paint + in your Windows Start Menu and on your Windows Desktop. (Both options are + set by default.) - ------------------------------------------------------- + Then you will be asked where you wish to install Tux Paint. The default + should be suitable, as long as there is space available. Otherwise, pick a + different location. - Running the Tux Paint Windows Installer: + At this point, you can click 'Install' to install Tux Paint! - Double-click the Tux Paint installer executable (.EXE file) and - follow the instructions. + Changing the Settings Using the Shortcut - First, you will be asked to read the license. (It is the GNU General - Public License (GPL), which is also available as "COPYING.txt".) + To change program settings, right-click on the TuxPaint shortcut and + select 'Properties' (at the bottom). - You will then be asked whether you want to install shortcuts to Tux - Paint in your Windows Start Menu and on your Windows Desktop. (Both - options are set by default.) + Make sure the 'Shortcut' tab is selected in the window that appears, and + examine the 'Target:' field. You should see something like this: - Then you will be asked where you wish to install Tux Paint. The - default should be suitable, as long as there is space available. - Otherwise, pick a different location. + "C:\Program Files\TuxPaint\TuxPaint.exe" - At this point, you can click 'Install' to install Tux Paint! + You can now add command-line options which will be enabled when you + double-click the icon. - ------------------------------------------------------- + For example, to make the game run in fullscreen mode, with simple shapes + (no rotation option) and in French, add the options (after + 'TuxPaint.exe'), like so: - Changing the Settings Using the Shortcut: + "C:\Program Files\TuxPaint\TuxPaint.exe" -f -s --lang french - To change program settings, right-click on the TuxPaint shortcut and - select 'Properties' (at the bottom). + (See the main documentation for a full list of available command-line + options.) - Make sure the 'Shortcut' tab is selected in the window that appears, - and examine the 'Target:' field. You should see something like this: + If you make a mistake or it all disappears use [Ctrl] + [Z] to undo or + just hit the [Esc] key and the box will close with no changes made (unless + you pushed the "Apply" button!). - "C:\Program Files\TuxPaint\TuxPaint.exe" + When you have finished, click "OK." - You can now add command-line options which will be enabled when you - double-click the icon. + If Something Goes Wrong - For example, to make the game run in fullscreen mode, with simple - shapes (no rotation option) and in French, add the options (after - 'TuxPaint.exe'), like so: + If, when you double-click on the shortcut to run Tux Paint, nothing + happens, it is probably because some of these command-line options are + wrong. Open an Explorer like before, and look for a file called + "stderr.txt" in the TuxPaint folder. - "C:\Program Files\TuxPaint\TuxPaint.exe" -f -s --lang french + It will contain a description of what was wrong. Usually it will just be + due to incorrect character-case (capital 'Z' instead of lowercase 'z') or + a missing (or extra) '-' (dash). - (See the main documentation for a full list of available - command-line options.) +Linux/Unix - If you make a mistake or it all disappears use [Ctrl] + [Z] to undo - or just hit the [Esc] key and the box will close with no changes - made (unless you pushed the "Apply" button!). + Compiling: - When you have finished, click "OK." + 💡 Note: Tux Paint does not use autoconf/automake, so there is no + "./configure" script to run. Compiling should be straight-forward though, + assuming everything Tux Paint needs is installed. - ------------------------------------------------------- + To compile the program from source, simply run the following command from + a shell prompt (e.g., "$"): - If Something Goes Wrong: + $ make - If, when you double-click on the shortcut to run Tux Paint, nothing - happens, it is probably because some of these command-line options - are wrong. Open an Explorer like before, and look for a file called - "stderr.txt" in the TuxPaint folder. + Disabling SVG support (and hence Cairo, libSVG, and svg-cairo dependencies): - It will contain a description of what was wrong. Usually it will - just be due to incorrect character-case (capital 'Z' instead of - lowercase 'z') or a missing (or extra) '-' (dash). + To disable SVG support (e.g., if your system is not currently supported by + the Cairo library or other SVG-related dependencies), you can run "make" + with "SVG_LIB= SVG_CFLAGS= NOSVGFLAG=NOSVG" added: - ---------------------------------------------------------------------- + $ make SVG_LIB= SVG_CFLAGS= - Linux/Unix Users + Disabling Pango support (and hence Pango, Cairo, etc. dependencies): - Compiling: + 📜 Prior to version 0.9.18, Tux Paint used the libSDL_ttf library for + rendering text using TrueType Fonts. Since 0.9.18, libSDL_Pango is used, + as it has much greater support for internationalization. However, if you + wish to disable the use of SDL_Pango, you may do so running "make" with + "SDL_PANGO_LIB=" added: - Note: Tux Paint does not use autoconf/automake, so there is no - "./configure" script to run. Compiling should be straight-forward - though, assuming everything Tux Paint needs is installed. + $ make SDL_PANGO_LIB= - To compile the program from source, simply run the following command - from a shell prompt (e.g., "$"): + Disabling Sound at Compile-time - $ make + If you don't have a sound card, or would prefer to build the program with + no sound support (and therefore without a the SDL_mixer dependency), you + can run "make" with "SDL_MIXER_LIB=" added: - ------------------------------------------------------- + $ make SDL_MIXER_LIB= - Disabling SVG support (and hence Cairo, libSVG, and svg-cairo dependencies): + Other options - To disable SVG support (e.g., if your system is not currently - supported by the Cairo library or other SVG-related dependencies), - you can run "make" with "SVG_LIB= SVG_CFLAGS= NOSVGFLAG=NOSVG" - added: + Various other options (e.g., installation paths) may be overridden; see + them in "Makefile" for further details. - $ make SVG_LIB= SVG_CFLAGS= + If you get errors - ------------------------------------------------------- + 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 "-dev" or "-devel" packages as well, otherwise you + won't be able to compile Tux Paint (and other programs) from source! - Disabling Pango support (and hence Pango, Cairo, etc. dependencies): + Installng - Prior to version 0.9.18, Tux Paint used the libSDL_ttf library for - rendering text using TrueType Fonts. Since 0.9.18, libSDL_Pango is - used, as it has much greater support for internationalization. - However, if you wish to disable the use of SDL_Pango, you may do so - running "make" with "SDL_PANGO_LIB=" added: + Assuming no fatal errors occured, you can now install the program so that + it can be run by users on the system. By default, this must be done by the + "root" user ('superuser'). Switch to "root" by typing the command: - $ make SDL_PANGO_LIB= + $ su - ------------------------------------------------------- + Enter "root"'s password at the prompt. You should now be "root" (with a + prompt like "#"). To install the program and its data files, type: - Disabling Sound at Compile-time: + # make install - If you don't have a sound card, or would prefer to build the program - with no sound support (and therefore without a the SDL_mixer - dependency), you can run "make" with "SDL_MIXER_LIB=" added: + Finally, you can switch back to your regular user by exiting superuser + mode: - $ make SDL_MIXER_LIB= + # exit - ------------------------------------------------------- + Alternatively, you may be able to simply use the "sudo" command (e.g., on + Ubuntu Linux): - Other options: + $ sudo make install - Various other options (e.g., installation paths) may be overridden; - see them in "Makefile" for further details. + 💡 Note: By default, "tuxpaint", the executable program, is placed in + "/usr/local/bin/". The data files (images, sounds, etc.) are placed in + "/usr/local/share/tuxpaint/". - ------------------------------------------------------- + Changing Where Things Go - If you get errors: + You can change where things will go by setting "Makefile"variables on the + command line. "DESTDIR" is used to place output in a staging area for + package creation. "PREFIX" is the basis of where all other files go, and + is, by default, set to "/usr/local". - 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 "-dev" or "-devel" - packages as well, otherwise you won't be able to compile Tux Paint - (and other programs) from source! + Other variables are: - ------------------------------------------------------- + BIN_PREFIX + Where the "tuxpaint" binary will be installed. (Set to + "$(PREFIX)/bin" by default - e.g., "/usr/local/bin") - Installng: + DATA_PREFIX + Where the data files (sound, graphics, brushes, stamps, fonts) + will go, and where Tux Paint will look for them when it's run. + (Set to "$(PREFIX)/share/tuxpaint") - Assuming no fatal errors occured, you can now install the program so - that it can be run by users on the system. By default, this must be - done by the "root" user ('superuser'). Switch to "root" by typing - the command: + DOC_PREFIX + Where the documentation text files (the "docs" directory) will go. + (Set to "$(PREFIX)/share/doc/tuxpaint") - $ su + MAN_PREFIX + Where the manual page for Tux Paint will go. (Set to + "$(PREFIX)/share/man") - Enter "root"'s password at the prompt. You should now be "root" - (with a prompt like "#"). To install the program and its data files, - type: + ICON_PREFIX — $(PREFIX)/share/pixmaps - # make install + X11_ICON_PREFIX — $(PREFIX)/X11R6/include/X11/pixmaps - Finally, you can switch back to your regular user by exiting - superuser mode: + GNOME_PREFIX — $(PREFIX)/share/gnome/apps/Graphics - # exit + KDE_PREFIX — $(PREFIX)/share/applnk/Graphics + Where the icons and launchers (for GNOME and KDE) will go. - Alternatively, you may be able to simply use the "sudo" command - (e.g., on Ubuntu Linux): + LOCALE_PREFIX + Where the translation files for Tux Paint will go, and where Tux + Paint will look for them. (Set to "$(PREFIX)/share/locale/") + (Final location of a translation file will be under the locale's + directory (e.g., "es" for Spanish), within the "LC_MESSAGES" + subdirectory.) - $ sudo make install + 💡 Note: This list is out of date. See "Makefile" and "Makefile-i18n" for a + complete list. - Note: By default, "tuxpaint", the executable program, is placed in - "/usr/local/bin/". The data files (images, sounds, etc.) are placed - in "/usr/local/share/tuxpaint/". +macOS - Changing Where Things Go + January 20, 2022 Mark Kim - You can change where things will go by setting "Makefile"variables - on the command line. "DESTDIR" is used to place output in a - staging area for package creation. "PREFIX" is the basis of where - all other files go, and is, by default, set to "/usr/local". + 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. - Other variables are: + Prerequisites - BIN_PREFIX - Where the "tuxpaint" binary will be installed. (Set to - "$(PREFIX)/bin" by default - e.g., "/usr/local/bin") + 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: - DATA_PREFIX - Where the data files (sound, graphics, brushes, stamps, - fonts) will go, and where Tux Paint will look for them - when it's run. (Set to "$(PREFIX)/share/tuxpaint") + xcode-select --install - DOC_PREFIX - Where the documentation text files (the "docs" directory) - will go. (Set to "$(PREFIX)/share/doc/tuxpaint") + 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 + * libsdl_gfx + * pkgconfig + * zlib + ... but you should install any package that is required by the latest + version of Tux Paint. - MAN_PREFIX - Where the manual page for Tux Paint will go. (Set to - "$(PREFIX)/share/man") + ^* Not available from MacPorts as of this writing, see below. - ICON_PREFIX — $(PREFIX)/share/pixmaps + libimagequant - X11_ICON_PREFIX — $(PREFIX)/X11R6/include/X11/pixmaps + 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. - GNOME_PREFIX — $(PREFIX)/share/gnome/apps/Graphics + $ sudo port install rust cargo + $ git clone https://github.com/ImageOptim/libimagequant.git + $ cd libimagequant/imagequant-sys + $ cargo build --release # Must use cargo from MacPorts + $ sudo make PREFIX=/opt/local install - KDE_PREFIX — $(PREFIX)/share/applnk/Graphics - Where the icons and launchers (for GNOME and KDE) will go. + 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. - LOCALE_PREFIX - Where the translation files for Tux Paint will go, and - where Tux Paint will look for them. (Set to - "$(PREFIX)/share/locale/") (Final location of a - translation file will be under the locale's directory - (e.g., "es" for Spanish), within the "LC_MESSAGES" - subdirectory.) + How to Build - Note: This list is out of date. See "Makefile" and "Makefile-i18n" - for a complete list. + Simply, run: + + % make + % make install + + ... to create the TuxPaint.app application bundle that can be run in-place + or copied to /Applications. To create the DMG file for distribution, use + 'make TuxPaint.dmg'. + + Additional steps may be required when building for the Apple Silicon. See + "Building for Apple Silicon" below. + + 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. + + Alternatively, Tux Paint and all of its library dependencies may be + compiled with appropriate options to be runnable on older versions of + macOS. These options are already set on Tux Paint, so only its + dependencies (from MacPorts) need to be recompiled. See "Recompiling + MacPorts" below for the instructions. + + 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 for Intel CPU does allow dual booting of multiple versions of the + OS, but it's safer and easier to install the old macOS onto a flash drive. + Wherever you're installing it, the target drive's partitioniong scheme and + partition type must match what the old macOS expects, so use the Disk + Utility to partition and format the flash drive accordingly. + + Dual booting multiple versions of macOS for Apple Silicon has been so far + unsuccessful. Instead of installing an older version of macOS for Apple + Silicon to build Tux Paint to run on the old version of macOS for Apple + Silicon, use the instructions found in the "Recompiling MacPorts" section + to build Tux Paint to run on older versions of macOS for Apple Silicon. + + 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 + + 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. - macOS Users + Recompiling MacPorts - January 20, 2022 Mark Kim + To recompile MacPorts to be usable on older versions of macOS, set the + following options in /opt/local/etc/macports/macports.conf: - 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. + buildfromsource always + macosx_deployment_target 10.10 - Prerequisites + Then uninstall all MacPorts packages: - 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: + $ sudo port -fp uninstall installed - xcode-select --install + Then reinstall all MacPorts packages needed by Tux Paint. Also rebuild + libimagequant using the updated Cargo package from MacPorts. - 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 - * libsdl_gfx - * pkgconfig - * zlib - ... but you should install any package that is required by the - latest version of Tux Paint. + As of this writing, all libraries Tux Paint requires from MacPorts can be + recompiled in this manner to run on macOS 10.10 Yosemite and later on + Intel CPUs, and macOS 11.0 Big Sur and later on Apple Silicon. + Unfortunately, although MacPorts has the option to enable the building of + universal libraries, several libraries Tux Paint require cannot be built + as universal libraries so they can only be built to run natively on the + hardware on which they were built. See "Building a Universal Binary" below + for instructions on how to build Tux Paint as a Universal Binary. - ^* Not available from MacPorts as of this writing, see below. + Building for Apple Silicon - libimagequant + macOS for Applie Silicon requires all native Apple Silicon applications be + signed, even if it is signed "ad-hoc" (anonymously). Because of this, + compilers that produce native Apple Silicon applications sign all produced + binaries and libraries as a part of the compilation process.^* However, + the Tux Paint compilation process modifies the libraries to be modular + (using install_name_tool) so they can be added into the application + bundle, which has the unfortunate side effect of breaking the signature. + This can be addressed by signing the application bundle ad-hoc (example + below) or using your own Apple Developer Identity if you have one. The DMG + file, if needed, must be created after signing the App Bundle so the DMG + file is created with signed App Bundle: - 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. + $ codesign -s - TuxPaint.app + $ make TuxPaint.dmg - $ sudo port install rust cargo - $ git clone https://github.com/ImageOptim/libimagequant.git - $ cd libimagequant/imagequant-sys - $ cargo build --release # Must use cargo from MacPorts - $ sudo make PREFIX=/opt/local install + ^* For more information on the code signing requirements on the Apple + Silicon, see + https://developer.apple.com/documentation/macos-release-notes/macos-big-sur-11_0_1-universal-apps-release-notes#:~:text=New%20in%20macOS,pass%20through%20Gatekeeper. - 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. + If you get an error that the application bundle is already signed, remove + it before signing:: - ------------------------------------------------------- + $ codesign --remove-signature TuxPaint.app - How to Build + If you plan to combine the Apple Silicon bundle with the Intel CPU bundle + to produce the Universal bundle, the code signing must be done after they + are combined. See "Building a Universal Binary" below. - Simply, run: - - % make - % make install + Building a Universal Binary - ... to create the TuxPaint.app application bundle that can be run - in-place or copied to /Applications. To create the DMG file for - distribution, use 'make TuxPaint.dmg'. + To build Tux Paint as a Universal Binary, compile Tux Paint for the Intel + CPU and the Apple Silicon separately first. Then rename the app bundle for + the Intel CPU to TuxPaint-x86_64.app, and the bundle for the Apple Silicon + to TuxPaint-arm64.app, copy the app bundle from the Intel machine to the + Apple Silicon machine, then use the provided build-universal.sh script to + combine the two application bundles as below. The produced bundle must be + signed (see "Building for Apple Silicon" above for more details). The DMG + file, if required, must be built after the signing: - Additional steps may be required when building for the Apple - Silicon. See "Building for Apple Silicon" below. - - ------------------------------------------------------- - - 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. - - Alternatively, Tux Paint and all of its library dependencies may - be compiled with appropriate options to be runnable on older - versions of macOS. These options are already set on Tux Paint, - so only its dependencies (from MacPorts) need to be recompiled. - See "Recompiling MacPorts" below for the instructions. - - ------------------------------------------------------- - - 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 for Intel CPU does allow dual booting of multiple versions of - the OS, but it's safer and easier to install the old macOS onto a - flash drive. Wherever you're installing it, the target drive's - partitioniong scheme and partition type must match what the old - macOS expects, so use the Disk Utility to partition and format the - flash drive accordingly. - - Dual booting multiple versions of macOS for Apple Silicon has been - so far unsuccessful. Instead of installing an older version of macOS - for Apple Silicon to build Tux Paint to run on the old version of - macOS for Apple Silicon, use the instructions found in the - "Recompiling MacPorts" section to build Tux Paint to run on older - versions of macOS for Apple Silicon. - - 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 - - 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/ + $ macos/build-universal.sh + $ codesign -s - TuxPaint.app + $ make TuxPaint.dmg - 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 + Debugging - 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 output — to "STDOUT" on Linux and Unix, to a "stdout.txt" file + on Windows, and to the file "/tmp/tuxpaint.log" on macOS — can be enabled + by setting "DEBUG" (and, if verbose logging is wanted, "VERBOSE") #defines + in "src/debug.h" and (re)compiling Tux Paint. - Recompiling MacPorts + Uninstalling Tux Paint - To recompile MacPorts to be usable on older versions of macOS, set - the following options in /opt/local/etc/macports/macports.conf: +Windows - buildfromsource always - macosx_deployment_target 10.10 + Using the Uninstaller - Then uninstall all MacPorts packages: + If you installed the Start Menu shortcuts (the default), then go to the + TuxPaint folder and select "Uninstall". A box will be displayed that will + confirm that you are about to uninstall Tux Paint and, if you are certain + that you want to permanently remove Tux Paint, click on the 'Uninstall' + button. - $ sudo port -fp uninstall installed + When it has finished, click on the close button. - Then reinstall all MacPorts packages needed by Tux Paint. Also - rebuild libimagequant using the updated Cargo package from MacPorts. + Using the Control Panel - As of this writing, all libraries Tux Paint requires from MacPorts - can be recompiled in this manner to run on macOS 10.10 Yosemite and - later on Intel CPUs, and macOS 11.0 Big Sur and later on Apple - Silicon. Unfortunately, although MacPorts has the option to enable - the building of universal libraries, several libraries Tux Paint - require cannot be built as universal libraries so they can only be - built to run natively on the hardware on which they were built. See - "Building a Universal Binary" below for instructions on how to build - Tux Paint as a Universal Binary. + It is also possible to use the entry "TuxPaint (remove only)" in the + Control Panel Add/Remove programs section. - Building for Apple Silicon +macOS - macOS for Applie Silicon requires all native Apple Silicon - applications be signed, even if it is signed "ad-hoc" (anonymously). - Because of this, compilers that produce native Apple Silicon - applications sign all produced binaries and libraries as a part of - the compilation process.^* However, the Tux Paint compilation - process modifies the libraries to be modular (using - install_name_tool) so they can be added into the application bundle, - which has the unfortunate side effect of breaking the signature. - This can be addressed by signing the application bundle ad-hoc - (example below) or using your own Apple Developer Identity if you - have one. The DMG file, if needed, must be created after signing the - App Bundle so the DMG file is created with signed App Bundle: + Delete "TuxPaint.app" from the "Applications" folder. Data files, + including the configuration files, stamps, and saved pictures, may be + found in "Library/Application Support/TuxPaint" (all users) and + "/Users/USERNAME/Library/Application Support/TuxPaint" (individual users). - $ codesign -s - TuxPaint.app - $ make TuxPaint.dmg +Linux - ^* For more information on the code signing requirements on the - Apple Silicon, see - https://developer.apple.com/documentation/macos-release-notes/macos-big-sur-11_0_1-universal-apps-release-notes#:~:text=New%20in%20macOS,pass%20through%20Gatekeeper. - - If you get an error that the application bundle is already signed, - remove it before signing:: - - $ codesign --remove-signature TuxPaint.app - - If you plan to combine the Apple Silicon bundle with the Intel CPU - bundle to produce the Universal bundle, the code signing must be - done after they are combined. See "Building a Universal Binary" - below. - - Building a Universal Binary - - To build Tux Paint as a Universal Binary, compile Tux Paint for the - Intel CPU and the Apple Silicon separately first. Then rename the - app bundle for the Intel CPU to TuxPaint-x86_64.app, and the bundle - for the Apple Silicon to TuxPaint-arm64.app, copy the app bundle - from the Intel machine to the Apple Silicon machine, then use the - provided build-universal.sh script to combine the two application - bundles as below. The produced bundle must be signed (see "Building - for Apple Silicon" above for more details). The DMG file, if - required, must be built after the signing: - - $ macos/build-universal.sh - $ codesign -s - TuxPaint.app - $ make TuxPaint.dmg - - ---------------------------------------------------------------------- - -Debugging - - Debugging output — to "STDOUT" on Linux and Unix, to a "stdout.txt" file - on Windows, and to the file "/tmp/tuxpaint.log" on macOS — can be - enabled by setting "DEBUG" (and, if verbose logging is wanted, - "VERBOSE") #defines in "src/debug.h" and (re)compiling Tux Paint. - - ---------------------------------------------------------------------- - -Uninstalling Tux Paint - - Windows - - Using the Uninstaller - - If you installed the Start Menu shortcuts (the default), then go to - the TuxPaint folder and select "Uninstall". A box will be displayed - that will confirm that you are about to uninstall Tux Paint and, if - you are certain that you want to permanently remove Tux Paint, click - on the 'Uninstall' button. - - When it has finished, click on the close button. - - Using the Control Panel - - It is also possible to use the entry "TuxPaint (remove only)" in the - Control Panel Add/Remove programs section. - - ---------------------------------------------------------------------- - - macOS - - Delete "TuxPaint.app" from the "Applications" folder. Data files, - including the configuration files, stamps, and saved pictures, may be - found in "Library/Application Support/TuxPaint" (all users) and - "/Users/USERNAME/Library/Application Support/TuxPaint" (individual - users). - - ---------------------------------------------------------------------- - - Linux - - Within the Tux Paint source directory (where you compiled Tux Paint), - you can use the "make uninstall" target to uninstall Tux Paint. By - default, this must be done by the "root" user ('superuser'), but if - you installed Tux Paint somewhere else (e.g., using a "PREFIX=..." - setting to "make" and "make install"), you may not, and will want to - provide those same settings here. (See the installation instructions - above for further information.) + Within the Tux Paint source directory (where you compiled Tux Paint), you + can use the "make uninstall" target to uninstall Tux Paint. By default, + this must be done by the "root" user ('superuser'), but if you installed + Tux Paint somewhere else (e.g., using a "PREFIX=..." setting to "make" and + "make install"), you may not, and will want to provide those same settings + here. (See the installation instructions above for further information.) diff --git a/docs/en/html/EXTENDING.html b/docs/en/html/EXTENDING.html index 88a71e745..62a88d281 100644 --- a/docs/en/html/EXTENDING.html +++ b/docs/en/html/EXTENDING.html @@ -21,15 +21,17 @@ } div.keeptogether { page-break-inside: avoid; } section h1 { font-size: 2em; } - h1, h2, h3, h4 { font-family: sans; } + h1, h2, h3, h4, h5 { font-family: sans; } h1 { color: #800; page-break-before: always; break-before: always; } h2 { color: #440; page-break-after: avoid; break-after: avoid; } h3 { color: #080; page-break-after: avoid; break-after: avoid; } h4 { color: #008; page-break-after: avoid; break-after: avoid; } + h5 { color: #808; page-break-after: avoid; break-after: avoid; } h1 + p { page-break-inside: avoid; } h2 + p { page-break-inside: avoid; } h3 + p { page-break-inside: avoid; } h4 + p { page-break-inside: avoid; } + h5 + p { page-break-inside: avoid; } dt { font-size: large; color: #404; diff --git a/docs/en/html/INSTALL.html b/docs/en/html/INSTALL.html index 3ef929244..79d7d8028 100644 --- a/docs/en/html/INSTALL.html +++ b/docs/en/html/INSTALL.html @@ -5,249 +5,312 @@ Tux Paint Installation Documentation + -
-

- Tux Paint
- version 0.9.28
- Installation Documentation

+
+
+
+

+ Tux Paint
+ version 0.9.28
+ Installation Documentation

-

- Copyright © 2002-2022 by various contributors; see AUTHORS.txt.
- https://tuxpaint.org/ -

+

+ Copyright © 2002-2022 by various contributors; see AUTHORS.txt.
+ https://tuxpaint.org/ +

-

- January 20, 2022

-
+

+ March 31, 2022

+
+ -
+ + + + -
+ Table of Contents
- - - + + + +
- Table of Contents
+ +
+ - - - - - - +
+
+

+ + Requirements +

+
-
+
+
+

+ + Simple DirectMedia Layer library (libSDL) +

+
-

- - Requirements -

-
- -

- - Simple DirectMedia Layer library (libSDL) -

-

Tux Paint requires the Simple DirectMedia Layer Library (libSDL), an Open Source multimedia programming library available under the GNU Lesser General Public License (LGPL).

Along with libSDL, Tux Paint depends on a number of other SDL 'helper' libraries: SDL_Image (for graphics files), SDL_gfx (for some graphical functions, like rotation), SDL_TTF and (optionally) SDL_Pango (for True Type Font support) and, optionally, SDL_Mixer (for sound effects).

-

Linux/Unix Users:

-
-

- The SDL libraries are available as source-code, or as RPM or Debian packages for various distributions of Linux. They can be downloaded from:

- +
+
Linux/Unix
+
+

+ The SDL libraries are available as source-code, or as RPM or Debian packages for various distributions of Linux. They can be downloaded from:

+ -

- They are also typically available along with your Linux distribution (e.g. on an installation media, or available via package maintainance software like Debian's "apt").

+

+ They are also typically available along with your Linux distribution (e.g. on an installation media, or available via package maintainance software like Debian's "apt").

-

- Note: When installing libraries from packages, be sure to ALSO install the development versions of the packages. (For example, install both "SDL-1.2.4.rpm" and "SDL-1.2.4-devel.rpm".)

-
-
+

+ 💡 Note: When installing libraries from packages, be sure to ALSO install the development versions of the packages. (For example, install both "SDL-1.2.4.rpm" and "SDL-1.2.4-devel.rpm".)

+ + +
+ +
+
+

+ + Other Libraries +

+
-

- - Other Libraries -

-

Tux Paint also takes advantage of a number of other free, LGPL'd libraries. Under Linux, just like SDL, they should either already be installed, or are readily available for installation as part of your Linux distribution.

-

libPNG

-
-

- Tux Paint uses PNG (Portable Network Graphics) format for its data files. SDL_image will require libPNG be installed.

+
+
libPNG
+
+

+ Tux Paint uses PNG (Portable Network Graphics) format for its data files. SDL_image will require libPNG be installed.

-

- http://www.libpng.org/pub/png/libpng.html -

-
+

+ http://www.libpng.org/pub/png/libpng.html +

+ -

gettext

-
-

- Tux Paint uses your system's locale settings along with the "gettext" library to support various languages (e.g., Spanish). You'll need the gettext library installed.

+
gettext
+
+

+ Tux Paint uses your system's locale settings along with the "gettext" library to support various languages (e.g., Spanish). You'll need the gettext library installed.

-

- http://www.gnu.org/software/gettext/ -

-
+

+ http://www.gnu.org/software/gettext/ +

+ -

libpaper (Linux/Unix only)

-
-

- As of Tux Paint 0.9.17, Tux Paint can determine your system's default paper size (e.g., A4 or Letter), or can be told to use a particular paper size, thanks to "libpaper".

+
libpaper (Linux/Unix only)
+
+

+ As of Tux Paint 0.9.17, Tux Paint can determine your system's default paper size (e.g., A4 or Letter), or can be told to use a particular paper size, thanks to "libpaper".

-

- https://github.com/naota/libpaper -

-
+

+ https://github.com/naota/libpaper +

+ -

FriBiDi

-
-

- Tux Paint's "Text" and also "Label" tools support bidirectional languages, thanks to the "FriBiDi" library.

+
FriBiDi
+
+

+ Tux Paint's "Text" and also "Label" tools support bidirectional languages, thanks to the "FriBiDi" library.

-

- http://fribidi.org/ -

-
+

+ http://fribidi.org/ +

+ -

SVG graphics support

-
-

- As of Tux Paint 0.9.17, Tux Paint can load SVG (Scalable Vector Graphics) images as stamps. Two sets of libraries are supported, and SVG support can be completely disabled (via "make SVG_LIB:=")

+
SVG graphics support
+
+

+ As of Tux Paint 0.9.17, Tux Paint can load SVG (Scalable Vector Graphics) images as stamps. Two sets of libraries are supported, and SVG support can be completely disabled (via "make SVG_LIB:=")

-
librsvg-2 & libCairo2 (newer libraries)
- +
+
librsvg-2 & libCairo2 (newer libraries)
+
+ +
-
Older SVG libraries
- -
+
Older SVG libraries
+
+ +
+ + -

Animated GIF Export feature

-
-

- To support export of animated GIFs (slideshows), the "libimagequant" library (from the "pngquant2" project) is required.

+
Animated GIF Export feature
+
+

+ To support export of animated GIFs (slideshows), the "libimagequant" library (from the "pngquant2" project) is required.

-

- https://github.com/ImageOptim/libimagequant -

-
+

+ https://github.com/ImageOptim/libimagequant +

+ -

NetPBM Tools (optional) No longer used, by default

-
-

- Under Linux and Unix, earlier versions of Tux Paint used the NetPBM tools to assist with printing. (A PNG is generated by Tux Paint, and converted into a PostScript using the 'pngtopnm' and 'pnmtops' NetPBM command-line tools.)

+
NetPBM Tools (optional) No longer used, by default
+
+

+ 📜 Under Linux and Unix, earlier versions of Tux Paint used the NetPBM tools to assist with printing. (A PNG is generated by Tux Paint, and converted into a PostScript using the 'pngtopnm' and 'pnmtops' NetPBM command-line tools.)

-

- http://netpbm.sourceforge.net/ -

-
-
- +

+ http://netpbm.sourceforge.net/ +

+ + +
+
-
+
+
+

+ + Compiling and Installation +

+
-

- - Compiling and Installation -

-

Tux Paint is released under the GNU General Public License (GPL) (see "COPYING.txt" for details), and therefore the 'source code' to the program is available freely.

-

- - Windows Users -

-

- - November 3, 2021 Shin-ichi TOYAMA dolphin6k@wmail.plala.or.jp <dolphin6k@wmail.plala.or.jp> - -

-
-

Compiling Set-Up

-
+
+
+

+ + Windows +

+ +

+ + November 3, 2021 Shin-ichi TOYAMA dolphin6k@wmail.plala.or.jp <dolphin6k@wmail.plala.or.jp> + +

+
+ +
+
+

Compiling Set-Up

+
+

As of February 2005 (starting with Tux Paint 0.9.15), the "Makefile" includes support for building on a Windows system using MinGW/MSYS (https://sourceforge.net/projects/msys2/).

@@ -276,183 +339,194 @@

-
+

+ + Proceed to the next "MinGW 64bit (x86_64) toolchains" section, or skip to the "MinGW 32bit (i686) toolchains" section if you need only a 32bit build environment. +

-

- - Proceed to the next "MinGW 64bit (x86_64) toolchains" section, or skip 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 64bit development tools:

- - pacman -S mingw-w64-x86_64-toolchain - -
-

- -
- -

- 64bit (x86_64) dependency libraries for Tux Paint

- -
-

- You can install tools and libraries required for compiling Tux Paint on MSYS2/MINGW using "pacman" except for SDL_Pango.

-

- "ntldd" is a small tool which examine windows executable files to list Dynamic Link Library (.dll) files they depends on. Tux Paint's packaging process for binary distribution uses it to find required .dll files.

-

- FLTK is a cross-platform GUI toolkit used by "Tux Paint Config.". You can skip installing it if you are only building "Tux Paint".

-

-

- - $ pacman -S mingw-w64-x86_64-SDL_{image,mixer,ttf,gfx}
- $ pacman -S mingw-w64-x86_64-librsvg
- $ pacman -S mingw-w64-x86_64-fribidi
- $ pacman -S mingw-w64-x86_64-libimagequant
- $ pacman -S mingw-w64-x86_64-fltk
- $ pacman -S mingw-w64-x86_64-ntldd-git - -
-

-

- Note: Close the shell before proceeding to the remaining process.

- -
- -

- Install SDL_Pango on the 64bit environment

- -
-

- SDL_Pango should be installed manually.

-

- This time, use the MinGW "64bit" shell. Open the shell from the "Start Menu" -> "MSYS2 64bit" -> "MSYS2 MinGW 64-bit"

- -
SDL_Pango
- -
- -

- At first, you have to prepare source tar-ball and a required patch in the same directory.

- -

- Build and install SDL_Pango as follows.

- - $ tar zxvf SDL_Pango-0.1.2.tar.gz
- $ cd SDL_Pango-0.1.2/
- $ patch -p0 < ../SDL_Pango-configure-extra-api.patch
- $ ./configure --prefix=/mingw64 && make && make install - -
-

-
- -
- -

- - Proceed to the next "MinGW 32bit (i686) toolchains" section, or skip 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 32bit development tools:

- - pacman -S mingw-w64-i686-toolchain - -
-

- -
- -

- 32bit (i686) dependency libraries for Tux Paint

- -
-

- You can install tools and libraries required for compiling Tux Paint on MSYS2/MINGW using "pacman" except for SDL_Pango.

-

- "ntldd" is a small tool which examine windows executable files to list Dynamic Link Library (.dll) files they depends on. Tux Paint's packaging process for binary distribution uses it to find required .dll files.

-

- FLTK is a cross-platform GUI toolkit used by "Tux Paint Config.". You can skip installing it if you are only building "Tux Paint".

-

-

- - $ pacman -S mingw-w64-i686-SDL_{image,mixer,ttf,gfx}
- $ pacman -S mingw-w64-i686-librsvg
- $ pacman -S mingw-w64-i686-fribidi
- $ pacman -S mingw-w64-i686-libimagequant
- $ pacman -S mingw-w64-i686-fltk
- $ pacman -S mingw-w64-i686-ntldd-git - -
-

-

- Note: Close the shell before proceeding to the remaining process.

- -
- -

- Install SDL_Pango on the 32bit environment

- -
-

- SDL_Pango should be installed manually.

-

- This time, use the MinGW "32bit" shell. Open the shell from the "Start Menu" -> "MSYS2 64bit" -> "MSYS2 MinGW 32-bit"

- -
SDL_Pango
- -
+
+
+

+ + MinGW 64bit (x86_64) toolchains +

+

- At first, you have to prepare source tar-ball and a required patch in the same directory.

- -

- Build and install SDL_Pango as follows.

+ Within the MSYS2 shell, run the following command to install basic 64bit development tools:
- $ tar zxvf SDL_Pango-0.1.2.tar.gz
- $ cd SDL_Pango-0.1.2/
- $ patch -p0 < ../SDL_Pango-configure-extra-api.patch
- $ ./configure --prefix=/mingw32 && make && make install + pacman -S mingw-w64-x86_64-toolchain

-
+
-
+
+
+

+ 64bit (x86_64) dependency libraries for Tux Paint

+
- -
+

+ You can install tools and libraries required for compiling Tux Paint on MSYS2/MINGW using "pacman" except for SDL_Pango.

+

+ "ntldd" is a small tool which examine windows executable files to list Dynamic Link Library (.dll) files they depends on. Tux Paint's packaging process for binary distribution uses it to find required .dll files.

+

+ FLTK is a cross-platform GUI toolkit used by "Tux Paint Config.". You can skip installing it if you are only building "Tux Paint".

+

+

+ + $ pacman -S mingw-w64-x86_64-SDL_{image,mixer,ttf,gfx}
+ $ pacman -S mingw-w64-x86_64-librsvg
+ $ pacman -S mingw-w64-x86_64-fribidi
+ $ pacman -S mingw-w64-x86_64-libimagequant
+ $ pacman -S mingw-w64-x86_64-fltk
+ $ pacman -S mingw-w64-x86_64-ntldd-git + +
+

+

+ 💡 Note: Close the shell before proceeding to the remaining process.

+
-

- ImageMagick -

+
+
+

+ Install SDL_Pango on the 64bit environment

+
+ +

+ SDL_Pango should be installed manually.

+

+ This time, use the MinGW "64bit" shell. Open the shell from the "Start Menu" -> "MSYS2 64bit" -> "MSYS2 MinGW 64-bit"

+ +
+
+
SDL_Pango
+
+ +

+ At first, you have to prepare source tar-ball and a required patch in the same directory.

+

+

+ Build and install SDL_Pango as follows.

+ + $ tar zxvf SDL_Pango-0.1.2.tar.gz
+ $ cd SDL_Pango-0.1.2/
+ $ patch -p0 < ../SDL_Pango-configure-extra-api.patch
+ $ ./configure --prefix=/mingw64 && make && make install + +
+

+
+ +

+ + Proceed to the next "MinGW 32bit (i686) toolchains" section, or skip 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 32bit development tools:

+ + pacman -S mingw-w64-i686-toolchain + +
+

+
+ +
+
+

+ 32bit (i686) dependency libraries for Tux Paint

+
+ +

+ You can install tools and libraries required for compiling Tux Paint on MSYS2/MINGW using "pacman" except for SDL_Pango.

+

+ "ntldd" is a small tool which examine windows executable files to list Dynamic Link Library (.dll) files they depends on. Tux Paint's packaging process for binary distribution uses it to find required .dll files.

+

+ FLTK is a cross-platform GUI toolkit used by "Tux Paint Config.". You can skip installing it if you are only building "Tux Paint".

+

+

+ + $ pacman -S mingw-w64-i686-SDL_{image,mixer,ttf,gfx}
+ $ pacman -S mingw-w64-i686-librsvg
+ $ pacman -S mingw-w64-i686-fribidi
+ $ pacman -S mingw-w64-i686-libimagequant
+ $ pacman -S mingw-w64-i686-fltk
+ $ pacman -S mingw-w64-i686-ntldd-git + +
+

+

+ 💡 Note: Close the shell before proceeding to the remaining process.

+
+ +
+
+

+ Install SDL_Pango on the 32bit environment

+
+ +

+ SDL_Pango should be installed manually.

+

+ This time, use the MinGW "32bit" shell. Open the shell from the "Start Menu" -> "MSYS2 64bit" -> "MSYS2 MinGW 32-bit"

+ +
+
+
SDL_Pango
+
+ +

+ At first, you have to prepare source tar-ball and a required patch in the same directory.

+

+

+ Build and install SDL_Pango as follows.

+ + $ tar zxvf SDL_Pango-0.1.2.tar.gz
+ $ cd SDL_Pango-0.1.2/
+ $ patch -p0 < ../SDL_Pango-configure-extra-api.patch
+ $ ./configure --prefix=/mingw32 && make && make install + +
+

+
+ + +
+ +
+ +
+
+

+ ImageMagick +

+
-

ImageMagick is a compilation of command line tools to create, edit, compose, or convert bitmap images supporting quite a large number of image formats. Tux Paint uses two functions ("convert" and "composite") in it to generate thumbnails for startar images and templates during the build process.

@@ -468,13 +542,13 @@

You can make this permanent by adding the above to your the BASH shell configuration file, "~/.bash_profile".

-
+
-
+
+
+

Tux Paint

+
-

Tux Paint

- -

You can compile 64bit binaries using MSYS2 64bit shell, and 32bit binaries using MSYS2 32bit shell, respectively.

    @@ -490,16 +564,17 @@

-

- Note: At this point, you will want to build "Tux Paint Config." for Windows, so it can be included along with "Tux Paint", if you're making an official (or test) release. The build process will look for it in a directory named "tuxpaint-config" (with no version number, e.g., "tuxpaint-config-X.Y.Z"). See "Tux Paint Config."'s INSTALL.txt documentation for details.

+

+ 💡 Note: At this point, you will want to build "Tux Paint Config." for Windows, so it can be included along with "Tux Paint", if you're making an official (or test) release. The build process will look for it in a directory named "tuxpaint-config" (with no version number, e.g., "tuxpaint-config-X.Y.Z"). See "Tux Paint Config."'s INSTALL.txt documentation for details.

All the files needed for starting Tux Paint (and Tux Paint Config.) are collected in the directory for binary distribution "bdist" directory under "win32". You can start them by double-clicking their executable (.exe) files in the "bdist" directory.

- +
-
- -

Building the Tux Paint Windows Installer:

-
+
+
+

+ Building the Tux Paint Windows Installer

+

Inno Setup is used to build executable installer for Tux Paint. Therefore you have to install it in the first place.

@@ -509,14 +584,17 @@ Before building an installer, edit the "tuxpaint.iss" file and enable one of the lines starting with "#define BuildTarget=", depending on the architecture of the installer you want to create.

Then, you can easily build an executable installer by right-clicking on the "tuxpaint.iss" icon in the "win32" directory and selecting "Compile" on the list. It will run for a while, and eventually you will find a "tuxpaint-X.Y.Z-windows-<arch>-installer.exe" file in the same directory.

-
+ -
+
+
+

+ Running the Tux Paint Windows Installer

+
-

Running the Tux Paint Windows Installer:

-

- Double-click the Tux Paint installer executable (.EXE file) and follow the instructions. + Double-click the Tux Paint installer executable (.EXE file) and follow the instructions.

+

First, you will be asked to read the license. (It is the GNU General Public License (GPL), which is also available as "COPYING.txt".)

@@ -528,12 +606,14 @@

At this point, you can click 'Install' to install Tux Paint!

-
+
-
+
+
+

+ Changing the Settings Using the Shortcut

+
-

Changing the Settings Using the Shortcut:

-

To change program settings, right-click on the TuxPaint shortcut and select 'Properties' (at the bottom).

@@ -566,31 +646,38 @@

When you have finished, click "OK."

-
+
-
+
+
+

+ If Something Goes Wrong

+
-

If Something Goes Wrong:

-

If, when you double-click on the shortcut to run Tux Paint, nothing happens, it is probably because some of these command-line options are wrong. Open an Explorer like before, and look for a file called "stderr.txt" in the TuxPaint folder.

It will contain a description of what was wrong. Usually it will just be due to incorrect character-case (capital 'Z' instead of lowercase 'z') or a missing (or extra) '-' (dash).

-
- +
+ -
+
+
+

+ + Linux/Unix +

+
-

- - Linux/Unix Users -

-
-

Compiling:

-
-

- Note: Tux Paint does not use autoconf/automake, so there is no "./configure" script to run. Compiling should be straight-forward though, assuming everything Tux Paint needs is installed.

+
+
+

+ Compiling:

+
+ +

+ 💡 Note: Tux Paint does not use autoconf/automake, so there is no "./configure" script to run. Compiling should be straight-forward though, assuming everything Tux Paint needs is installed.

To compile the program from source, simply run the following command from a shell prompt (e.g., "$"):

@@ -600,13 +687,14 @@ $ make
-
+
-
+
+
+

+ Disabling SVG support (and hence Cairo, libSVG, and svg-cairo dependencies):

+
-

- Disabling SVG support (and hence Cairo, libSVG, and svg-cairo dependencies):

-

To disable SVG support (e.g., if your system is not currently supported by the Cairo library or other SVG-related dependencies), you can run "make" with "SVG_LIB= SVG_CFLAGS= NOSVGFLAG=NOSVG" added:

@@ -614,54 +702,64 @@ $ make SVG_LIB= SVG_CFLAGS=
-
+
-
+
+
+

+ Disabling Pango support (and hence Pango, Cairo, etc. dependencies):

+
-

- Disabling Pango support (and hence Pango, Cairo, etc. dependencies):

-
-

- Prior to version 0.9.18, Tux Paint used the libSDL_ttf library for rendering text using TrueType Fonts. Since 0.9.18, libSDL_Pango is used, as it has much greater support for internationalization. However, if you wish to disable the use of SDL_Pango, you may do so running "make" with "SDL_PANGO_LIB=" added:

+

+ 📜 Prior to version 0.9.18, Tux Paint used the libSDL_ttf library for rendering text using TrueType Fonts. Since 0.9.18, libSDL_Pango is used, as it has much greater support for internationalization. However, if you wish to disable the use of SDL_Pango, you may do so running "make" with "SDL_PANGO_LIB=" added:

$ make SDL_PANGO_LIB=
-
+
-
+
+
+

+ Disabling Sound at Compile-time

+
-

Disabling Sound at Compile-time:

-
- If you don't have a sound card, or would prefer to build the program with no sound support (and therefore without a the SDL_mixer dependency), you can run "make" with "SDL_MIXER_LIB=" added:

+

+ If you don't have a sound card, or would prefer to build the program with no sound support (and therefore without a the SDL_mixer dependency), you can run "make" with "SDL_MIXER_LIB=" added:

$ make SDL_MIXER_LIB=
-
+
-
+
+
+

+ Other options

+
-

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 get errors:

-

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 "-dev" or "-devel" packages as well, otherwise you won't be able to compile Tux Paint (and other programs) from source!

-
+
-
+
+
+

+ Installng

+
-

Installng:

-

Assuming no fatal errors occured, you can now install the program so that it can be run by users on the system. By default, this must be done by the "root" user ('superuser'). Switch to "root" by typing the command:

@@ -698,11 +796,15 @@
-

- Note: By default, "tuxpaint", the executable program, is placed in "/usr/local/bin/". The data files (images, sounds, etc.) are placed in "/usr/local/share/tuxpaint/".

+

+ 💡 Note: By default, "tuxpaint", the executable program, is placed in "/usr/local/bin/". The data files (images, sounds, etc.) are placed in "/usr/local/share/tuxpaint/".

+ +
+
+

+ Changing Where Things Go

+
-
Changing Where Things Go
-

You can change where things will go by setting "Makefile"variables on the command line. "DESTDIR" is used to place output in a staging area for package creation. "PREFIX" is the basis of where all other files go, and is, by default, set to "/usr/local".

@@ -737,30 +839,34 @@ Where the translation files for Tux Paint will go, and where Tux Paint will look for them. (Set to "$(PREFIX)/share/locale/") (Final location of a translation file will be under the locale's directory (e.g., "es" for Spanish), within the "LC_MESSAGES" subdirectory.) -

- Note: This list is out of date. See "Makefile" and "Makefile-i18n" for a complete list.

-
- - +

+ 💡 Note: This list is out of date. See "Makefile" and "Makefile-i18n" for a complete list.

+
+
+ -
+
+
+

+ + macOS +

+

+ + January 20, 2022 Mark Kim <markuskimius@gmail.com> + +

+
-

- - macOS Users -

-

- - January 20, 2022 Mark 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

-
+
+
+

+ 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:

@@ -792,8 +898,13 @@
* Not available from MacPorts as of this writing, see below.

-
libimagequant
-
+
+
+

+ 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.

@@ -805,17 +916,18 @@

- -
+

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

+
-

How to Build

-

Simply, run:

@@ -827,12 +939,14 @@

Additional steps may be required when building for the Apple Silicon. See "Building for Apple Silicon" below.

-
+
-
+
+
+

+ Known Issues

+
-

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.
    @@ -841,12 +955,14 @@
    Alternatively, Tux Paint and all of its library dependencies may be compiled with appropriate options to be runnable on older versions of macOS. These options are already set on Tux Paint, so only its dependencies (from MacPorts) need to be recompiled. See "Recompiling MacPorts" below for the instructions.
-
+
-
+
+
+

+ Old Versions 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

@@ -870,11 +986,14 @@

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.

+
- +
+
+

+ Recompiling MacPorts

+
-

Recompiling MacPorts

-

To recompile MacPorts to be usable on older versions of macOS, set the following options in /opt/local/etc/macports/macports.conf:

@@ -897,18 +1016,21 @@

As of this writing, all libraries Tux Paint requires from MacPorts can be recompiled in this manner to run on macOS 10.10 Yosemite and later on Intel CPUs, and macOS 11.0 Big Sur and later on Apple Silicon. Unfortunately, although MacPorts has the option to enable the building of universal libraries, several libraries Tux Paint require cannot be built as universal libraries so they can only be built to run natively on the hardware on which they were built. See "Building a Universal Binary" below for instructions on how to build Tux Paint as a Universal Binary.

-
+
+ +
+
+

+ Building for Apple Silicon

+
-

Building for Apple Silicon

-

macOS for Applie Silicon requires all native Apple Silicon applications be signed, even if it is signed "ad-hoc" (anonymously). Because of this, compilers that produce native Apple Silicon applications sign all produced binaries and libraries as a part of the compilation process.* However, the Tux Paint compilation process modifies the libraries to be modular (using install_name_tool) so they can be added into the application bundle, which has the unfortunate side effect of breaking the signature. This can be addressed by signing the application bundle ad-hoc (example below) or using your own Apple Developer Identity if you have one. The DMG file, if needed, must be created after signing the App Bundle so the DMG file is created with signed App Bundle:

$ codesign -s - TuxPaint.app
$ make TuxPaint.dmg
- * For more information on the code signing requirements on the Apple Silicon, see https://developer.apple.com/documentation/macos-release-notes/macos-big-sur-11_0_1-universal-apps-release-notes#:~:text=New%20in%20macOS,pass%20through%20Gatekeeper. -

+ * For more information on the code signing requirements on the Apple Silicon, see https://developer.apple.com/documentation/macos-release-notes/macos-big-sur-11_0_1-universal-apps-release-notes#:~:text=New%20in%20macOS,pass%20through%20Gatekeeper.

If you get an error that the application bundle is already signed, remove it before signing::

$ codesign --remove-signature TuxPaint.app @@ -916,10 +1038,14 @@

If you plan to combine the Apple Silicon bundle with the Intel CPU bundle to produce the Universal bundle, the code signing must be done after they are combined. See "Building a Universal Binary" below.

-
+
+ +
+
+

+ Building a Universal Binary

+
-

Building a Universal Binary

-

To build Tux Paint as a Universal Binary, compile Tux Paint for the Intel CPU and the Apple Silicon separately first. Then rename the app bundle for the Intel CPU to TuxPaint-x86_64.app, and the bundle for the Apple Silicon to TuxPaint-arm64.app, copy the app bundle from the Intel machine to the Apple Silicon machine, then use the provided build-universal.sh script to combine the two application bundles as below. The produced bundle must be signed (see "Building for Apple Silicon" above for more details). The DMG file, if required, must be built after the signing:

@@ -929,71 +1055,87 @@

-
+
- + - + -
+
+
+

+ + Debugging +

+
-

- - Debugging -

-
- Debugging output — to "STDOUT" on Linux and Unix, to a "stdout.txt" file on Windows, and to the file "/tmp/tuxpaint.log" on macOS — can be enabled by setting "DEBUG" (and, if verbose logging is wanted, "VERBOSE") #defines in "src/debug.h" and (re)compiling Tux Paint.
+

+ ⚙ Debugging output — to "STDOUT" on Linux and Unix, to a "stdout.txt" file on Windows, and to the file "/tmp/tuxpaint.log" on macOS — can be enabled by setting "DEBUG" (and, if verbose logging is wanted, "VERBOSE") #defines in "src/debug.h" and (re)compiling Tux Paint.

+
-
+
+
+

+ + Uninstalling Tux Paint +

+
+ +
+
+

+ + Windows +

+
+ +
+
+

+ Using the Uninstaller

+
-

- - Uninstalling Tux Paint

- -
-

- - Windows -

-
-

Using the Uninstaller

-

If you installed the Start Menu shortcuts (the default), then go to the TuxPaint folder and select "Uninstall". A box will be displayed that will confirm that you are about to uninstall Tux Paint and, if you are certain that you want to permanently remove Tux Paint, click on the 'Uninstall' button.

When it has finished, click on the close button.

-
+
+ +
+
+

+ Using the Control Panel

+
-

Using the Control Panel

-

It is also possible to use the entry "TuxPaint (remove only)" in the Control Panel Add/Remove programs section.

-
- +
+
-
+
+
+

+ + macOS +

+
-

- - macOS -

- -

Delete "TuxPaint.app" from the "Applications" folder. Data files, including the configuration files, stamps, and saved pictures, may be found in "Library/Application Support/TuxPaint" (all users) and "/Users/USERNAME/Library/Application Support/TuxPaint" (individual users).

-
+
-
+
+
+

+ + Linux +

+
-

- - Linux -

-

Within the Tux Paint source directory (where you compiled Tux Paint), you can use the "make uninstall" target to uninstall Tux Paint. By default, this must be done by the "root" user ('superuser'), but if you installed Tux Paint somewhere else (e.g., using a "PREFIX=..." setting to "make" and "make install"), you may not, and will want to provide those same settings here. (See the installation instructions above for further information.)

-
-
+
+
diff --git a/docs/en/html/OPTIONS.html b/docs/en/html/OPTIONS.html index fd057f1a4..d1e147791 100644 --- a/docs/en/html/OPTIONS.html +++ b/docs/en/html/OPTIONS.html @@ -21,15 +21,17 @@ } div.keeptogether { page-break-inside: avoid; } section h1 { font-size: 2em; } - h1, h2, h3, h4 { font-family: sans; } + h1, h2, h3, h4, h5 { font-family: sans; } h1 { color: #800; page-break-before: always; break-before: always; } h2 { color: #440; page-break-after: avoid; break-after: avoid; } h3 { color: #080; page-break-after: avoid; break-after: avoid; } h4 { color: #008; page-break-after: avoid; break-after: avoid; } + h5 { color: #808; page-break-after: avoid; break-after: avoid; } h1 + p { page-break-inside: avoid; } h2 + p { page-break-inside: avoid; } h3 + p { page-break-inside: avoid; } h4 + p { page-break-inside: avoid; } + h5 + p { page-break-inside: avoid; } dt { font-size: large; color: #404; diff --git a/docs/en/html/PNG.html b/docs/en/html/PNG.html index b41dcb299..adaf06534 100644 --- a/docs/en/html/PNG.html +++ b/docs/en/html/PNG.html @@ -21,15 +21,17 @@ } div.keeptogether { page-break-inside: avoid; } section h1 { font-size: 2em; } - h1, h2, h3, h4 { font-family: sans; } + h1, h2, h3, h4, h5 { font-family: sans; } h1 { color: #800; page-break-before: always; break-before: always; } h2 { color: #440; page-break-after: avoid; break-after: avoid; } h3 { color: #080; page-break-after: avoid; break-after: avoid; } h4 { color: #008; page-break-after: avoid; break-after: avoid; } + h5 { color: #808; page-break-after: avoid; break-after: avoid; } h1 + p { page-break-inside: avoid; } h2 + p { page-break-inside: avoid; } h3 + p { page-break-inside: avoid; } h4 + p { page-break-inside: avoid; } + h5 + p { page-break-inside: avoid; } dt { font-size: large; color: #404; diff --git a/docs/en/html/README.html b/docs/en/html/README.html index 57af7d625..93bccdc4c 100644 --- a/docs/en/html/README.html +++ b/docs/en/html/README.html @@ -21,15 +21,17 @@ } div.keeptogether { page-break-inside: avoid; } section h1 { font-size: 2em; } - h1, h2, h3, h4 { font-family: sans; } + h1, h2, h3, h4, h5 { font-family: sans; } h1 { color: #800; page-break-before: always; break-before: always; } h2 { color: #440; page-break-after: avoid; break-after: avoid; } h3 { color: #080; page-break-after: avoid; break-after: avoid; } h4 { color: #008; page-break-after: avoid; break-after: avoid; } + h5 { color: #808; page-break-after: avoid; break-after: avoid; } h1 + p { page-break-inside: avoid; } h2 + p { page-break-inside: avoid; } h3 + p { page-break-inside: avoid; } h4 + p { page-break-inside: avoid; } + h5 + p { page-break-inside: avoid; } dt { font-size: large; color: #404; diff --git a/docs/en/html/SIGNALS.html b/docs/en/html/SIGNALS.html index 1183c3a0e..da2e1f2cb 100644 --- a/docs/en/html/SIGNALS.html +++ b/docs/en/html/SIGNALS.html @@ -21,15 +21,17 @@ } div.keeptogether { page-break-inside: avoid; } section h1 { font-size: 2em; } - h1, h2, h3, h4 { font-family: sans; } + h1, h2, h3, h4, h5 { font-family: sans; } h1 { color: #800; page-break-before: always; break-before: always; } h2 { color: #440; page-break-after: avoid; break-after: avoid; } h3 { color: #080; page-break-after: avoid; break-after: avoid; } h4 { color: #008; page-break-after: avoid; break-after: avoid; } + h5 { color: #808; page-break-after: avoid; break-after: avoid; } h1 + p { page-break-inside: avoid; } h2 + p { page-break-inside: avoid; } h3 + p { page-break-inside: avoid; } h4 + p { page-break-inside: avoid; } + h5 + p { page-break-inside: avoid; } dt { font-size: large; color: #404; diff --git a/docs/en/html/SVG.html b/docs/en/html/SVG.html index 2f69561c6..9c495fad0 100644 --- a/docs/en/html/SVG.html +++ b/docs/en/html/SVG.html @@ -21,15 +21,17 @@ } div.keeptogether { page-break-inside: avoid; } section h1 { font-size: 2em; } - h1, h2, h3, h4 { font-family: sans; } + h1, h2, h3, h4, h5 { font-family: sans; } h1 { color: #800; page-break-before: always; break-before: always; } h2 { color: #440; page-break-after: avoid; break-after: avoid; } h3 { color: #080; page-break-after: avoid; break-after: avoid; } h4 { color: #008; page-break-after: avoid; break-after: avoid; } + h5 { color: #808; page-break-after: avoid; break-after: avoid; } h1 + p { page-break-inside: avoid; } h2 + p { page-break-inside: avoid; } h3 + p { page-break-inside: avoid; } h4 + p { page-break-inside: avoid; } + h5 + p { page-break-inside: avoid; } dt { font-size: large; color: #404; diff --git a/docs/es_ES.UTF-8/INSTALL.txt b/docs/es_ES.UTF-8/INSTALL.txt index ffa5c4201..bd532b2fc 100644 --- a/docs/es_ES.UTF-8/INSTALL.txt +++ b/docs/es_ES.UTF-8/INSTALL.txt @@ -5,853 +5,783 @@ Copyright © 2002-2022 by various contributors; see AUTHORS.txt. https://tuxpaint.org/ - enero 20, 2022 + marzo 31, 2022 - ---------------------------------------------------------------------- + +----------------------------------------------------+ + |Table of Contents | + |----------------------------------------------------| + | * Requirements | + | * Simple DirectMedia Layer library (libSDL) | + | * Other Libraries | + | * Compiling and Installation | + | * Windows | + | * Linux/Unix | + | * macOS | + | * Debugging | + | * Uninstalling Tux Paint | + | * Windows | + | * macOS | + | * Linux | + +----------------------------------------------------+ - +----------------------------------------------------+ - |Table of Contents | - |----------------------------------------------------| - | * Requirements | - | * Simple DirectMedia Layer library (libSDL) | - | * Other Libraries | - | * Compiling and Installation | - | * Windows Users | - | * Linux/Unix Users | - | * macOS Users | - | * Debugging | - | * Uninstalling Tux Paint | - | * Windows | - | * macOS | - | * Linux | - +----------------------------------------------------+ + Requirements - ---------------------------------------------------------------------- +Simple DirectMedia Layer library (libSDL) -Requirements + Tux Paint requires the Simple DirectMedia Layer Library (libSDL), an Open + Source multimedia programming library available under the GNU Lesser + General Public License (LGPL). - Simple DirectMedia Layer library (libSDL) + Along with libSDL, Tux Paint depends on a number of other SDL 'helper' + libraries: SDL_Image (for graphics files), SDL_gfx (for some graphical + functions, like rotation), SDL_TTF and (optionally) SDL_Pango (for True + Type Font support) and, optionally, SDL_Mixer (for sound effects). - Tux Paint requires the Simple DirectMedia Layer Library (libSDL), an - Open Source multimedia programming library available under the GNU - Lesser General Public License (LGPL). + Linux/Unix - Along with libSDL, Tux Paint depends on a number of other SDL 'helper' - libraries: SDL_Image (for graphics files), SDL_gfx (for some graphical - functions, like rotation), SDL_TTF and (optionally) SDL_Pango (for - True Type Font support) and, optionally, SDL_Mixer (for sound - effects). + The SDL libraries are available as source-code, or as RPM or + Debian packages for various distributions of Linux. They can be + downloaded from: - Linux/Unix Users: + * libSDL: http://www.libsdl.org/ + * SDL_Image: http://www.libsdl.org/projects/SDL_image/ + * SDL_gfx: + https://www.ferzkopp.net/wordpress/2016/01/02/sdl_gfx-sdl2_gfx/ + (https://sourceforge.net/projects/sdlgfx/) + * SDL_TTF: http://www.libsdl.org/projects/SDL_ttf/ + * SDL_Pango: http://sourceforge.net/projects/sdlpango/ + (optional) + * SDL_Mixer: http://www.libsdl.org/projects/SDL_mixer/ + (optional) - The SDL libraries are available as source-code, or as RPM or Debian - packages for various distributions of Linux. They can be downloaded - from: + They are also typically available along with your Linux + distribution (e.g. on an installation media, or available via + package maintainance software like Debian's "apt"). - * libSDL: http://www.libsdl.org/ - * SDL_Image: http://www.libsdl.org/projects/SDL_image/ - * SDL_gfx: - https://www.ferzkopp.net/wordpress/2016/01/02/sdl_gfx-sdl2_gfx/ - (https://sourceforge.net/projects/sdlgfx/) - * SDL_TTF: http://www.libsdl.org/projects/SDL_ttf/ - * SDL_Pango: http://sourceforge.net/projects/sdlpango/ (optional) - * SDL_Mixer: http://www.libsdl.org/projects/SDL_mixer/ (optional) - - They are also typically available along with your Linux distribution - (e.g. on an installation media, or available via package - maintainance software like Debian's "apt"). - - Note: When installing libraries from packages, be sure to ALSO - install the development versions of the packages. (For example, - install both "SDL-1.2.4.rpm" and "SDL-1.2.4-devel.rpm".) + 💡 Note: When installing libraries from packages, be sure to ALSO + install the development versions of the packages. (For example, + install both "SDL-1.2.4.rpm" and "SDL-1.2.4-devel.rpm".) Other Libraries - Tux Paint also takes advantage of a number of other free, LGPL'd - libraries. Under Linux, just like SDL, they should either already be - installed, or are readily available for installation as part of your - Linux distribution. + Tux Paint also takes advantage of a number of other free, LGPL'd + libraries. Under Linux, just like SDL, they should either already be + installed, or are readily available for installation as part of your Linux + distribution. - libPNG + libPNG - Tux Paint uses PNG (Portable Network Graphics) format for its data - files. SDL_image will require libPNG be installed. + Tux Paint uses PNG (Portable Network Graphics) format for its data + files. SDL_image will require libPNG be installed. - http://www.libpng.org/pub/png/libpng.html + http://www.libpng.org/pub/png/libpng.html - gettext + gettext - Tux Paint uses your system's locale settings along with the - "gettext" library to support various languages (e.g., Spanish). - You'll need the gettext library installed. + Tux Paint uses your system's locale settings along with the + "gettext" library to support various languages (e.g., Spanish). + You'll need the gettext library installed. - http://www.gnu.org/software/gettext/ + http://www.gnu.org/software/gettext/ - libpaper (Linux/Unix only) + libpaper (Linux/Unix only) - As of Tux Paint 0.9.17, Tux Paint can determine your system's - default paper size (e.g., A4 or Letter), or can be told to use a - particular paper size, thanks to "libpaper". + As of Tux Paint 0.9.17, Tux Paint can determine your system's + default paper size (e.g., A4 or Letter), or can be told to use a + particular paper size, thanks to "libpaper". - https://github.com/naota/libpaper + https://github.com/naota/libpaper - FriBiDi + FriBiDi - Tux Paint's "Text" and also "Label" tools support bidirectional - languages, thanks to the "FriBiDi" library. + Tux Paint's "Text" and also "Label" tools support bidirectional + languages, thanks to the "FriBiDi" library. - http://fribidi.org/ + http://fribidi.org/ - SVG graphics support + SVG graphics support - As of Tux Paint 0.9.17, Tux Paint can load SVG (Scalable Vector - Graphics) images as stamps. Two sets of libraries are supported, and - SVG support can be completely disabled (via "make SVG_LIB:=") + As of Tux Paint 0.9.17, Tux Paint can load SVG (Scalable Vector + Graphics) images as stamps. Two sets of libraries are supported, + and SVG support can be completely disabled (via "make SVG_LIB:=") - librsvg-2 & libCairo2 (newer libraries) + librsvg-2 & libCairo2 (newer libraries) + * libRSVG 2: http://librsvg.sourceforge.net/ + * Cairo 2: http://www.cairographics.org/ + * These also depend on the following: + * GdkPixbuf & GLib: http://www.gtk.org/ + * Pango: http://www.pango.org/ - * libRSVG 2: http://librsvg.sourceforge.net/ - * Cairo 2: http://www.cairographics.org/ - * These also depend on the following: - * GdkPixbuf & GLib: http://www.gtk.org/ - * Pango: http://www.pango.org/ + Older SVG libraries + * libcairo1, libsvg1, & libsvg-cairo1: + http://www.cairographics.org/ + * These also depend on the following: + * libxml2: + https://gitlab.gnome.org/GNOME/libxml2 - Older SVG libraries + Animated GIF Export feature - * libcairo1, libsvg1, & libsvg-cairo1: - http://www.cairographics.org/ - * These also depend on the following: - * libxml2: https://gitlab.gnome.org/GNOME/libxml2 + To support export of animated GIFs (slideshows), the + "libimagequant" library (from the "pngquant2" project) is + required. - Animated GIF Export feature + https://github.com/ImageOptim/libimagequant - To support export of animated GIFs (slideshows), the "libimagequant" - library (from the "pngquant2" project) is required. + NetPBM Tools (optional) No longer used, by default - https://github.com/ImageOptim/libimagequant + 📜 Under Linux and Unix, earlier versions of Tux Paint used the + NetPBM tools to assist with printing. (A PNG is generated by Tux + Paint, and converted into a PostScript using the 'pngtopnm' and + 'pnmtops' NetPBM command-line tools.) - NetPBM Tools (optional) No longer used, by default + http://netpbm.sourceforge.net/ - Under Linux and Unix, earlier versions of Tux Paint used the NetPBM - tools to assist with printing. (A PNG is generated by Tux Paint, and - converted into a PostScript using the 'pngtopnm' and 'pnmtops' - NetPBM command-line tools.) + Compiling and Installation - http://netpbm.sourceforge.net/ + Tux Paint is released under the GNU General Public License (GPL) (see + "COPYING.txt" for details), and therefore the 'source code' to the program + is available freely. - ---------------------------------------------------------------------- +Windows -Compiling and Installation + noviembre 3, 2021 Shin-ichi TOYAMA dolphin6k@wmail.plala.or.jp + - Tux Paint is released under the GNU General Public License (GPL) (see - "COPYING.txt" for details), and therefore the 'source code' to the - program is available freely. + Compiling Set-Up - Windows Users + As of February 2005 (starting with Tux Paint 0.9.15), the "Makefile" + includes support for building on a Windows system using MinGW/MSYS + (https://sourceforge.net/projects/msys2/). - noviembre 3, 2021 Shin-ichi TOYAMA dolphin6k@wmail.plala.or.jp - + Many tools and libraries are required to build Tux Paint. The package + management system "pacman" helps you install them automatically solving + complicated dependencies. - Compiling Set-Up + Download the latest MSYS2 environment from + https://sourceforge.net/projects/msys2/files/Base/ and install it where + you'd like (the default is "C:\msys64") - As of February 2005 (starting with Tux Paint 0.9.15), the "Makefile" - includes support for building on a Windows system using MinGW/MSYS - (https://sourceforge.net/projects/msys2/). + Open the MSYS2 shell from the "Start Menu" -> "MSYS2 64bit" -> "MSYS2 + MSYS" and execute following command (press [Enter] or [Return] to accept + the defaults for all questions): - Many tools and libraries are required to build Tux Paint. The - package management system "pacman" helps you install them - automatically solving complicated dependencies. + pacman -Syu - Download the latest MSYS2 environment from - https://sourceforge.net/projects/msys2/files/Base/ and install it - where you'd like (the default is "C:\msys64") + This will update core system and the window will close automatically. + Repeat the steps above one more time to finish the remaining update + process. - Open the MSYS2 shell from the "Start Menu" -> "MSYS2 64bit" -> - "MSYS2 MSYS" and execute following command (press [Enter] or - [Return] to accept the defaults for all questions): + Within the MSYS2 shell, run the following command to install basic + development tools: - pacman -Syu + pacman -S base-devel msys2-devel git - This will update core system and the window will close - automatically. Repeat the steps above one more time to finish the - remaining update process. - - Within the MSYS2 shell, run the following command to install basic - development tools: - - pacman -S base-devel msys2-devel git - - Proceed to the next "MinGW 64bit (x86_64) toolchains" section, or skip - to the "MinGW 32bit (i686) toolchains" section if you need only a - 32bit build environment. + Proceed to the next "MinGW 64bit (x86_64) toolchains" section, or skip 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 - 64bit development tools: + Within the MSYS2 shell, run the following command to install basic 64bit + development tools: - pacman -S mingw-w64-x86_64-toolchain + pacman -S mingw-w64-x86_64-toolchain 64bit (x86_64) dependency libraries for Tux Paint - You can install tools and libraries required for compiling Tux Paint - on MSYS2/MINGW using "pacman" except for SDL_Pango. + You can install tools and libraries required for compiling Tux Paint on + MSYS2/MINGW using "pacman" except for SDL_Pango. - "ntldd" is a small tool which examine windows executable files to - list Dynamic Link Library (.dll) files they depends on. Tux Paint's - packaging process for binary distribution uses it to find required - .dll files. + "ntldd" is a small tool which examine windows executable files to list + Dynamic Link Library (.dll) files they depends on. Tux Paint's packaging + process for binary distribution uses it to find required .dll files. - FLTK is a cross-platform GUI toolkit used by "Tux Paint Config.". - You can skip installing it if you are only building "Tux Paint". + FLTK is a cross-platform GUI toolkit used by "Tux Paint Config.". You can + skip installing it if you are only building "Tux Paint". - $ pacman -S mingw-w64-x86_64-SDL_{image,mixer,ttf,gfx} - $ pacman -S mingw-w64-x86_64-librsvg - $ pacman -S mingw-w64-x86_64-fribidi - $ pacman -S mingw-w64-x86_64-libimagequant - $ pacman -S mingw-w64-x86_64-fltk - $ pacman -S mingw-w64-x86_64-ntldd-git + $ pacman -S mingw-w64-x86_64-SDL_{image,mixer,ttf,gfx} + $ pacman -S mingw-w64-x86_64-librsvg + $ pacman -S mingw-w64-x86_64-fribidi + $ pacman -S mingw-w64-x86_64-libimagequant + $ pacman -S mingw-w64-x86_64-fltk + $ pacman -S mingw-w64-x86_64-ntldd-git - Note: Close the shell before proceeding to the remaining process. + 💡 Note: Close the shell before proceeding to the remaining process. Install SDL_Pango on the 64bit environment - SDL_Pango should be installed manually. + SDL_Pango should be installed manually. - This time, use the MinGW "64bit" shell. Open the shell from the - "Start Menu" -> "MSYS2 64bit" -> "MSYS2 MinGW 64-bit" + This time, use the MinGW "64bit" shell. Open the shell from the "Start + Menu" -> "MSYS2 64bit" -> "MSYS2 MinGW 64-bit" SDL_Pango - At first, you have to prepare source tar-ball and a required patch - in the same directory. + At first, you have to prepare source tar-ball and a required patch in the + same directory. + * Download source tar-ball of SDL_Pango-0.1.2 from SDL_Pango's page on + Sourceforge.net. + * Download a patch file from John Popplewell's "Tux Paint - MinGW/MSYS + build instructions" webpage. (This adds some extra (required) + functionality to SDL_Pango.) - * Download source tar-ball of SDL_Pango-0.1.2 from SDL_Pango's - page on Sourceforge.net. - * Download a patch file from John Popplewell's "Tux Paint - - MinGW/MSYS build instructions" webpage. (This adds some extra - (required) functionality to SDL_Pango.) + Build and install SDL_Pango as follows. - Build and install SDL_Pango as follows. + $ tar zxvf SDL_Pango-0.1.2.tar.gz + $ cd SDL_Pango-0.1.2/ + $ patch -p0 < ../SDL_Pango-configure-extra-api.patch + $ ./configure --prefix=/mingw64 && make && make install - $ tar zxvf SDL_Pango-0.1.2.tar.gz - $ cd SDL_Pango-0.1.2/ - $ patch -p0 < ../SDL_Pango-configure-extra-api.patch - $ ./configure --prefix=/mingw64 && make && make install - - Proceed to the next "MinGW 32bit (i686) toolchains" section, or skip - to the "ImageMagick" section if you need only a 64bit build - environment. + Proceed to the next "MinGW 32bit (i686) toolchains" section, or skip 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 - 32bit development tools: + Within the MSYS2 shell, run the following command to install basic 32bit + development tools: - pacman -S mingw-w64-i686-toolchain + pacman -S mingw-w64-i686-toolchain 32bit (i686) dependency libraries for Tux Paint - You can install tools and libraries required for compiling Tux Paint - on MSYS2/MINGW using "pacman" except for SDL_Pango. + You can install tools and libraries required for compiling Tux Paint on + MSYS2/MINGW using "pacman" except for SDL_Pango. - "ntldd" is a small tool which examine windows executable files to - list Dynamic Link Library (.dll) files they depends on. Tux Paint's - packaging process for binary distribution uses it to find required - .dll files. + "ntldd" is a small tool which examine windows executable files to list + Dynamic Link Library (.dll) files they depends on. Tux Paint's packaging + process for binary distribution uses it to find required .dll files. - FLTK is a cross-platform GUI toolkit used by "Tux Paint Config.". - You can skip installing it if you are only building "Tux Paint". + FLTK is a cross-platform GUI toolkit used by "Tux Paint Config.". You can + skip installing it if you are only building "Tux Paint". - $ pacman -S mingw-w64-i686-SDL_{image,mixer,ttf,gfx} - $ pacman -S mingw-w64-i686-librsvg - $ pacman -S mingw-w64-i686-fribidi - $ pacman -S mingw-w64-i686-libimagequant - $ pacman -S mingw-w64-i686-fltk - $ pacman -S mingw-w64-i686-ntldd-git + $ pacman -S mingw-w64-i686-SDL_{image,mixer,ttf,gfx} + $ pacman -S mingw-w64-i686-librsvg + $ pacman -S mingw-w64-i686-fribidi + $ pacman -S mingw-w64-i686-libimagequant + $ pacman -S mingw-w64-i686-fltk + $ pacman -S mingw-w64-i686-ntldd-git - Note: Close the shell before proceeding to the remaining process. + 💡 Note: Close the shell before proceeding to the remaining process. Install SDL_Pango on the 32bit environment - SDL_Pango should be installed manually. + SDL_Pango should be installed manually. - This time, use the MinGW "32bit" shell. Open the shell from the - "Start Menu" -> "MSYS2 64bit" -> "MSYS2 MinGW 32-bit" + This time, use the MinGW "32bit" shell. Open the shell from the "Start + Menu" -> "MSYS2 64bit" -> "MSYS2 MinGW 32-bit" SDL_Pango - At first, you have to prepare source tar-ball and a required patch - in the same directory. + At first, you have to prepare source tar-ball and a required patch in the + same directory. + * Download source tar-ball of SDL_Pango-0.1.2 from SDL_Pango's page on + Sourceforge.net. + * Download a patch file from John Popplewell's "Tux Paint - MinGW/MSYS + build instructions" webpage. (This adds some extra (required) + functionality to SDL_Pango.) - * Download source tar-ball of SDL_Pango-0.1.2 from SDL_Pango's - page on Sourceforge.net. - * Download a patch file from John Popplewell's "Tux Paint - - MinGW/MSYS build instructions" webpage. (This adds some extra - (required) functionality to SDL_Pango.) + Build and install SDL_Pango as follows. - Build and install SDL_Pango as follows. + $ tar zxvf SDL_Pango-0.1.2.tar.gz + $ cd SDL_Pango-0.1.2/ + $ patch -p0 < ../SDL_Pango-configure-extra-api.patch + $ ./configure --prefix=/mingw32 && make && make install - $ tar zxvf SDL_Pango-0.1.2.tar.gz - $ cd SDL_Pango-0.1.2/ - $ patch -p0 < ../SDL_Pango-configure-extra-api.patch - $ ./configure --prefix=/mingw32 && make && make install + ImageMagick - ------------------------------------------------------- + ImageMagick is a compilation of command line tools to create, edit, + compose, or convert bitmap images supporting quite a large number of image + formats. Tux Paint uses two functions ("convert" and "composite") in it to + generate thumbnails for startar images and templates during the build + process. - ImageMagick + Using official binary release available from "Windows Binary Release" is + recommended, due to the commands installed with "pacman" on MinGW/MSYS not + working as expected! - ImageMagick is a compilation of command line tools to create, edit, - compose, or convert bitmap images supporting quite a large number of - image formats. Tux Paint uses two functions ("convert" and - "composite") in it to generate thumbnails for startar images and - templates during the build process. + Do not forget to enable "Install legacy utilities (e.g. convert)" while + installing it, because Tux Paint's build process uses them. - Using official binary release available from "Windows Binary - Release" is recommended, due to the commands installed with "pacman" - on MinGW/MSYS not working as expected! + Add the path to the directory in which ImageMagick is installed at the top + of your "PATH" environment variable. For example: - Do not forget to enable "Install legacy utilities (e.g. convert)" - while installing it, because Tux Paint's build process uses them. + $ export PATH=/c/Program\ Files/ImageMagick-7.0.10-Q16-HDRI:$PATH - Add the path to the directory in which ImageMagick is installed at - the top of your "PATH" environment variable. For example: + You can make this permanent by adding the above to your the BASH shell + configuration file, "~/.bash_profile". - $ export PATH=/c/Program\ Files/ImageMagick-7.0.10-Q16-HDRI:$PATH + Tux Paint - You can make this permanent by adding the above to your the BASH - shell configuration file, "~/.bash_profile". + You can compile 64bit binaries using MSYS2 64bit shell, and 32bit binaries + using MSYS2 32bit shell, respectively. - ------------------------------------------------------- + * Select "MSYS2 64bit" -> "MSYS2 MinGW 64-bit" from the "Start Menu" to + open the 64bit shell. + * Select "MSYS2 64bit" -> "MSYS2 MinGW 32-bit" from the "Start Menu" to + open the 32bit shell. - Tux Paint + Compile Tux Paint with the following command: - You can compile 64bit binaries using MSYS2 64bit shell, and 32bit - binaries using MSYS2 32bit shell, respectively. + $ make bdist-win32 - * Select "MSYS2 64bit" -> "MSYS2 MinGW 64-bit" from the "Start - Menu" to open the 64bit shell. - * Select "MSYS2 64bit" -> "MSYS2 MinGW 32-bit" from the "Start - Menu" to open the 32bit shell. + 💡 Note: At this point, you will want to build "Tux Paint Config." for + Windows, so it can be included along with "Tux Paint", if you're making an + official (or test) release. The build process will look for it in a + directory named "tuxpaint-config" (with no version number, e.g., + "tuxpaint-config-X.Y.Z"). See "Tux Paint Config."'s INSTALL.txt + documentation for details. - Compile Tux Paint with the following command: + All the files needed for starting Tux Paint (and Tux Paint Config.) are + collected in the directory for binary distribution "bdist" directory under + "win32". You can start them by double-clicking their executable (.exe) + files in the "bdist" directory. - $ make bdist-win32 + Building the Tux Paint Windows Installer - Note: At this point, you will want to build "Tux Paint Config." for - Windows, so it can be included along with "Tux Paint", if you're - making an official (or test) release. The build process will look - for it in a directory named "tuxpaint-config" (with no version - number, e.g., "tuxpaint-config-X.Y.Z"). See "Tux Paint Config."'s - INSTALL.txt documentation for details. + Inno Setup is used to build executable installer for Tux Paint. Therefore + you have to install it in the first place. - All the files needed for starting Tux Paint (and Tux Paint Config.) - are collected in the directory for binary distribution "bdist" - directory under "win32". You can start them by double-clicking their - executable (.exe) files in the "bdist" directory. + Inno Setup officially supports translations for only about 20 languages. + However, one of the great points of Tux Paint is it supports so many + languages. Therefore, the set up script "tuxpaint.iss" to build the + installer is written to use much more translations including unofficial + one which are available on "Inno Setup Translations". You have to download + translation files (.isl) required and put them in "Languages" directory + under the directory in which Inno Setup is installed. - ------------------------------------------------------- + Before building an installer, edit the "tuxpaint.iss" file and enable one + of the lines starting with "#define BuildTarget=", depending on the + architecture of the installer you want to create. - Building the Tux Paint Windows Installer: + Then, you can easily build an executable installer by right-clicking on + the "tuxpaint.iss" icon in the "win32" directory and selecting "Compile" + on the list. It will run for a while, and eventually you will find a + "tuxpaint-X.Y.Z-windows--installer.exe" file in the same directory. - Inno Setup is used to build executable installer for Tux Paint. - Therefore you have to install it in the first place. + Running the Tux Paint Windows Installer - Inno Setup officially supports translations for only about 20 - languages. However, one of the great points of Tux Paint is it - supports so many languages. Therefore, the set up script - "tuxpaint.iss" to build the installer is written to use much more - translations including unofficial one which are available on "Inno - Setup Translations". You have to download translation files (.isl) - required and put them in "Languages" directory under the directory - in which Inno Setup is installed. + Double-click the Tux Paint installer executable (.EXE file) and follow the + instructions. - Before building an installer, edit the "tuxpaint.iss" file and - enable one of the lines starting with "#define BuildTarget=", - depending on the architecture of the installer you want to create. + First, you will be asked to read the license. (It is the GNU General + Public License (GPL), which is also available as "COPYING.txt".) - Then, you can easily build an executable installer by right-clicking - on the "tuxpaint.iss" icon in the "win32" directory and selecting - "Compile" on the list. It will run for a while, and eventually you - will find a "tuxpaint-X.Y.Z-windows--installer.exe" file in - the same directory. + You will then be asked whether you want to install shortcuts to Tux Paint + in your Windows Start Menu and on your Windows Desktop. (Both options are + set by default.) - ------------------------------------------------------- + Then you will be asked where you wish to install Tux Paint. The default + should be suitable, as long as there is space available. Otherwise, pick a + different location. - Running the Tux Paint Windows Installer: + At this point, you can click 'Install' to install Tux Paint! - Double-click the Tux Paint installer executable (.EXE file) and - follow the instructions. + Changing the Settings Using the Shortcut - First, you will be asked to read the license. (It is the GNU General - Public License (GPL), which is also available as "COPYING.txt".) + To change program settings, right-click on the TuxPaint shortcut and + select 'Properties' (at the bottom). - You will then be asked whether you want to install shortcuts to Tux - Paint in your Windows Start Menu and on your Windows Desktop. (Both - options are set by default.) + Make sure the 'Shortcut' tab is selected in the window that appears, and + examine the 'Target:' field. You should see something like this: - Then you will be asked where you wish to install Tux Paint. The - default should be suitable, as long as there is space available. - Otherwise, pick a different location. + "C:\Program Files\TuxPaint\TuxPaint.exe" - At this point, you can click 'Install' to install Tux Paint! + You can now add command-line options which will be enabled when you + double-click the icon. - ------------------------------------------------------- + For example, to make the game run in fullscreen mode, with simple shapes + (no rotation option) and in French, add the options (after + 'TuxPaint.exe'), like so: - Changing the Settings Using the Shortcut: + "C:\Program Files\TuxPaint\TuxPaint.exe" -f -s --lang french - To change program settings, right-click on the TuxPaint shortcut and - select 'Properties' (at the bottom). + (See the main documentation for a full list of available command-line + options.) - Make sure the 'Shortcut' tab is selected in the window that appears, - and examine the 'Target:' field. You should see something like this: + If you make a mistake or it all disappears use [Ctrl] + [Z] to undo or + just hit the [Esc] key and the box will close with no changes made (unless + you pushed the "Apply" button!). - "C:\Program Files\TuxPaint\TuxPaint.exe" + When you have finished, click "OK." - You can now add command-line options which will be enabled when you - double-click the icon. + If Something Goes Wrong - For example, to make the game run in fullscreen mode, with simple - shapes (no rotation option) and in French, add the options (after - 'TuxPaint.exe'), like so: + If, when you double-click on the shortcut to run Tux Paint, nothing + happens, it is probably because some of these command-line options are + wrong. Open an Explorer like before, and look for a file called + "stderr.txt" in the TuxPaint folder. - "C:\Program Files\TuxPaint\TuxPaint.exe" -f -s --lang french + It will contain a description of what was wrong. Usually it will just be + due to incorrect character-case (capital 'Z' instead of lowercase 'z') or + a missing (or extra) '-' (dash). - (See the main documentation for a full list of available - command-line options.) +Linux/Unix - If you make a mistake or it all disappears use [Ctrl] + [Z] to undo - or just hit the [Esc] key and the box will close with no changes - made (unless you pushed the "Apply" button!). + Compiling: - When you have finished, click "OK." + 💡 Note: Tux Paint does not use autoconf/automake, so there is no + "./configure" script to run. Compiling should be straight-forward though, + assuming everything Tux Paint needs is installed. - ------------------------------------------------------- + To compile the program from source, simply run the following command from + a shell prompt (e.g., "$"): - If Something Goes Wrong: + $ make - If, when you double-click on the shortcut to run Tux Paint, nothing - happens, it is probably because some of these command-line options - are wrong. Open an Explorer like before, and look for a file called - "stderr.txt" in the TuxPaint folder. + Disabling SVG support (and hence Cairo, libSVG, and svg-cairo dependencies): - It will contain a description of what was wrong. Usually it will - just be due to incorrect character-case (capital 'Z' instead of - lowercase 'z') or a missing (or extra) '-' (dash). + To disable SVG support (e.g., if your system is not currently supported by + the Cairo library or other SVG-related dependencies), you can run "make" + with "SVG_LIB= SVG_CFLAGS= NOSVGFLAG=NOSVG" added: - ---------------------------------------------------------------------- + $ make SVG_LIB= SVG_CFLAGS= - Linux/Unix Users + Disabling Pango support (and hence Pango, Cairo, etc. dependencies): - Compiling: + 📜 Prior to version 0.9.18, Tux Paint used the libSDL_ttf library for + rendering text using TrueType Fonts. Since 0.9.18, libSDL_Pango is used, + as it has much greater support for internationalization. However, if you + wish to disable the use of SDL_Pango, you may do so running "make" with + "SDL_PANGO_LIB=" added: - Note: Tux Paint does not use autoconf/automake, so there is no - "./configure" script to run. Compiling should be straight-forward - though, assuming everything Tux Paint needs is installed. + $ make SDL_PANGO_LIB= - To compile the program from source, simply run the following command - from a shell prompt (e.g., "$"): + Disabling Sound at Compile-time - $ make + If you don't have a sound card, or would prefer to build the program with + no sound support (and therefore without a the SDL_mixer dependency), you + can run "make" with "SDL_MIXER_LIB=" added: - ------------------------------------------------------- + $ make SDL_MIXER_LIB= - Disabling SVG support (and hence Cairo, libSVG, and svg-cairo dependencies): + Other options - To disable SVG support (e.g., if your system is not currently - supported by the Cairo library or other SVG-related dependencies), - you can run "make" with "SVG_LIB= SVG_CFLAGS= NOSVGFLAG=NOSVG" - added: + Various other options (e.g., installation paths) may be overridden; see + them in "Makefile" for further details. - $ make SVG_LIB= SVG_CFLAGS= + If you get errors - ------------------------------------------------------- + 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 "-dev" or "-devel" packages as well, otherwise you + won't be able to compile Tux Paint (and other programs) from source! - Disabling Pango support (and hence Pango, Cairo, etc. dependencies): + Installng - Prior to version 0.9.18, Tux Paint used the libSDL_ttf library for - rendering text using TrueType Fonts. Since 0.9.18, libSDL_Pango is - used, as it has much greater support for internationalization. - However, if you wish to disable the use of SDL_Pango, you may do so - running "make" with "SDL_PANGO_LIB=" added: + Assuming no fatal errors occured, you can now install the program so that + it can be run by users on the system. By default, this must be done by the + "root" user ('superuser'). Switch to "root" by typing the command: - $ make SDL_PANGO_LIB= + $ su - ------------------------------------------------------- + Enter "root"'s password at the prompt. You should now be "root" (with a + prompt like "#"). To install the program and its data files, type: - Disabling Sound at Compile-time: + # make install - If you don't have a sound card, or would prefer to build the program - with no sound support (and therefore without a the SDL_mixer - dependency), you can run "make" with "SDL_MIXER_LIB=" added: + Finally, you can switch back to your regular user by exiting superuser + mode: - $ make SDL_MIXER_LIB= + # exit - ------------------------------------------------------- + Alternatively, you may be able to simply use the "sudo" command (e.g., on + Ubuntu Linux): - Other options: + $ sudo make install - Various other options (e.g., installation paths) may be overridden; - see them in "Makefile" for further details. + 💡 Note: By default, "tuxpaint", the executable program, is placed in + "/usr/local/bin/". The data files (images, sounds, etc.) are placed in + "/usr/local/share/tuxpaint/". - ------------------------------------------------------- + Changing Where Things Go - If you get errors: + You can change where things will go by setting "Makefile"variables on the + command line. "DESTDIR" is used to place output in a staging area for + package creation. "PREFIX" is the basis of where all other files go, and + is, by default, set to "/usr/local". - 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 "-dev" or "-devel" - packages as well, otherwise you won't be able to compile Tux Paint - (and other programs) from source! + Other variables are: - ------------------------------------------------------- + BIN_PREFIX + Where the "tuxpaint" binary will be installed. (Set to + "$(PREFIX)/bin" by default - e.g., "/usr/local/bin") - Installng: + DATA_PREFIX + Where the data files (sound, graphics, brushes, stamps, fonts) + will go, and where Tux Paint will look for them when it's run. + (Set to "$(PREFIX)/share/tuxpaint") - Assuming no fatal errors occured, you can now install the program so - that it can be run by users on the system. By default, this must be - done by the "root" user ('superuser'). Switch to "root" by typing - the command: + DOC_PREFIX + Where the documentation text files (the "docs" directory) will go. + (Set to "$(PREFIX)/share/doc/tuxpaint") - $ su + MAN_PREFIX + Where the manual page for Tux Paint will go. (Set to + "$(PREFIX)/share/man") - Enter "root"'s password at the prompt. You should now be "root" - (with a prompt like "#"). To install the program and its data files, - type: + ICON_PREFIX — $(PREFIX)/share/pixmaps - # make install + X11_ICON_PREFIX — $(PREFIX)/X11R6/include/X11/pixmaps - Finally, you can switch back to your regular user by exiting - superuser mode: + GNOME_PREFIX — $(PREFIX)/share/gnome/apps/Graphics - # exit + KDE_PREFIX — $(PREFIX)/share/applnk/Graphics + Where the icons and launchers (for GNOME and KDE) will go. - Alternatively, you may be able to simply use the "sudo" command - (e.g., on Ubuntu Linux): + LOCALE_PREFIX + Where the translation files for Tux Paint will go, and where Tux + Paint will look for them. (Set to "$(PREFIX)/share/locale/") + (Final location of a translation file will be under the locale's + directory (e.g., "es" for Spanish), within the "LC_MESSAGES" + subdirectory.) - $ sudo make install + 💡 Note: This list is out of date. See "Makefile" and "Makefile-i18n" for a + complete list. - Note: By default, "tuxpaint", the executable program, is placed in - "/usr/local/bin/". The data files (images, sounds, etc.) are placed - in "/usr/local/share/tuxpaint/". +macOS - Changing Where Things Go + enero 20, 2022 Mark Kim - You can change where things will go by setting "Makefile"variables - on the command line. "DESTDIR" is used to place output in a - staging area for package creation. "PREFIX" is the basis of where - all other files go, and is, by default, set to "/usr/local". + 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. - Other variables are: + Prerequisites - BIN_PREFIX - Where the "tuxpaint" binary will be installed. (Set to - "$(PREFIX)/bin" by default - e.g., "/usr/local/bin") + 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: - DATA_PREFIX - Where the data files (sound, graphics, brushes, stamps, - fonts) will go, and where Tux Paint will look for them - when it's run. (Set to "$(PREFIX)/share/tuxpaint") + xcode-select --install - DOC_PREFIX - Where the documentation text files (the "docs" directory) - will go. (Set to "$(PREFIX)/share/doc/tuxpaint") + 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 + * libsdl_gfx + * pkgconfig + * zlib + ... but you should install any package that is required by the latest + version of Tux Paint. - MAN_PREFIX - Where the manual page for Tux Paint will go. (Set to - "$(PREFIX)/share/man") + ^* Not available from MacPorts as of this writing, see below. - ICON_PREFIX — $(PREFIX)/share/pixmaps + libimagequant - X11_ICON_PREFIX — $(PREFIX)/X11R6/include/X11/pixmaps + 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. - GNOME_PREFIX — $(PREFIX)/share/gnome/apps/Graphics + $ sudo port install rust cargo + $ git clone https://github.com/ImageOptim/libimagequant.git + $ cd libimagequant/imagequant-sys + $ cargo build --release # Must use cargo from MacPorts + $ sudo make PREFIX=/opt/local install - KDE_PREFIX — $(PREFIX)/share/applnk/Graphics - Where the icons and launchers (for GNOME and KDE) will go. + 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. - LOCALE_PREFIX - Where the translation files for Tux Paint will go, and - where Tux Paint will look for them. (Set to - "$(PREFIX)/share/locale/") (Final location of a - translation file will be under the locale's directory - (e.g., "es" for Spanish), within the "LC_MESSAGES" - subdirectory.) + How to Build - Note: This list is out of date. See "Makefile" and "Makefile-i18n" - for a complete list. + Simply, run: + + % make + % make install + + ... to create the TuxPaint.app application bundle that can be run in-place + or copied to /Applications. To create the DMG file for distribution, use + 'make TuxPaint.dmg'. + + Additional steps may be required when building for the Apple Silicon. See + "Building for Apple Silicon" below. + + 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. + + Alternatively, Tux Paint and all of its library dependencies may be + compiled with appropriate options to be runnable on older versions of + macOS. These options are already set on Tux Paint, so only its + dependencies (from MacPorts) need to be recompiled. See "Recompiling + MacPorts" below for the instructions. + + 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 for Intel CPU does allow dual booting of multiple versions of the + OS, but it's safer and easier to install the old macOS onto a flash drive. + Wherever you're installing it, the target drive's partitioniong scheme and + partition type must match what the old macOS expects, so use the Disk + Utility to partition and format the flash drive accordingly. + + Dual booting multiple versions of macOS for Apple Silicon has been so far + unsuccessful. Instead of installing an older version of macOS for Apple + Silicon to build Tux Paint to run on the old version of macOS for Apple + Silicon, use the instructions found in the "Recompiling MacPorts" section + to build Tux Paint to run on older versions of macOS for Apple Silicon. + + 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 + + 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. - macOS Users + Recompiling MacPorts - enero 20, 2022 Mark Kim + To recompile MacPorts to be usable on older versions of macOS, set the + following options in /opt/local/etc/macports/macports.conf: - 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. + buildfromsource always + macosx_deployment_target 10.10 - Prerequisites + Then uninstall all MacPorts packages: - 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: + $ sudo port -fp uninstall installed - xcode-select --install + Then reinstall all MacPorts packages needed by Tux Paint. Also rebuild + libimagequant using the updated Cargo package from MacPorts. - 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 - * libsdl_gfx - * pkgconfig - * zlib - ... but you should install any package that is required by the - latest version of Tux Paint. + As of this writing, all libraries Tux Paint requires from MacPorts can be + recompiled in this manner to run on macOS 10.10 Yosemite and later on + Intel CPUs, and macOS 11.0 Big Sur and later on Apple Silicon. + Unfortunately, although MacPorts has the option to enable the building of + universal libraries, several libraries Tux Paint require cannot be built + as universal libraries so they can only be built to run natively on the + hardware on which they were built. See "Building a Universal Binary" below + for instructions on how to build Tux Paint as a Universal Binary. - ^* Not available from MacPorts as of this writing, see below. + Building for Apple Silicon - libimagequant + macOS for Applie Silicon requires all native Apple Silicon applications be + signed, even if it is signed "ad-hoc" (anonymously). Because of this, + compilers that produce native Apple Silicon applications sign all produced + binaries and libraries as a part of the compilation process.^* However, + the Tux Paint compilation process modifies the libraries to be modular + (using install_name_tool) so they can be added into the application + bundle, which has the unfortunate side effect of breaking the signature. + This can be addressed by signing the application bundle ad-hoc (example + below) or using your own Apple Developer Identity if you have one. The DMG + file, if needed, must be created after signing the App Bundle so the DMG + file is created with signed App Bundle: - 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. + $ codesign -s - TuxPaint.app + $ make TuxPaint.dmg - $ sudo port install rust cargo - $ git clone https://github.com/ImageOptim/libimagequant.git - $ cd libimagequant/imagequant-sys - $ cargo build --release # Must use cargo from MacPorts - $ sudo make PREFIX=/opt/local install + ^* For more information on the code signing requirements on the Apple + Silicon, see + https://developer.apple.com/documentation/macos-release-notes/macos-big-sur-11_0_1-universal-apps-release-notes#:~:text=New%20in%20macOS,pass%20through%20Gatekeeper. - 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. + If you get an error that the application bundle is already signed, remove + it before signing:: - ------------------------------------------------------- + $ codesign --remove-signature TuxPaint.app - How to Build + If you plan to combine the Apple Silicon bundle with the Intel CPU bundle + to produce the Universal bundle, the code signing must be done after they + are combined. See "Building a Universal Binary" below. - Simply, run: - - % make - % make install + Building a Universal Binary - ... to create the TuxPaint.app application bundle that can be run - in-place or copied to /Applications. To create the DMG file for - distribution, use 'make TuxPaint.dmg'. + To build Tux Paint as a Universal Binary, compile Tux Paint for the Intel + CPU and the Apple Silicon separately first. Then rename the app bundle for + the Intel CPU to TuxPaint-x86_64.app, and the bundle for the Apple Silicon + to TuxPaint-arm64.app, copy the app bundle from the Intel machine to the + Apple Silicon machine, then use the provided build-universal.sh script to + combine the two application bundles as below. The produced bundle must be + signed (see "Building for Apple Silicon" above for more details). The DMG + file, if required, must be built after the signing: - Additional steps may be required when building for the Apple - Silicon. See "Building for Apple Silicon" below. - - ------------------------------------------------------- - - 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. - - Alternatively, Tux Paint and all of its library dependencies may - be compiled with appropriate options to be runnable on older - versions of macOS. These options are already set on Tux Paint, - so only its dependencies (from MacPorts) need to be recompiled. - See "Recompiling MacPorts" below for the instructions. - - ------------------------------------------------------- - - 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 for Intel CPU does allow dual booting of multiple versions of - the OS, but it's safer and easier to install the old macOS onto a - flash drive. Wherever you're installing it, the target drive's - partitioniong scheme and partition type must match what the old - macOS expects, so use the Disk Utility to partition and format the - flash drive accordingly. - - Dual booting multiple versions of macOS for Apple Silicon has been - so far unsuccessful. Instead of installing an older version of macOS - for Apple Silicon to build Tux Paint to run on the old version of - macOS for Apple Silicon, use the instructions found in the - "Recompiling MacPorts" section to build Tux Paint to run on older - versions of macOS for Apple Silicon. - - 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 - - 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/ + $ macos/build-universal.sh + $ codesign -s - TuxPaint.app + $ make TuxPaint.dmg - 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 + Debugging - 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 output — to "STDOUT" on Linux and Unix, to a "stdout.txt" file + on Windows, and to the file "/tmp/tuxpaint.log" on macOS — can be enabled + by setting "DEBUG" (and, if verbose logging is wanted, "VERBOSE") #defines + in "src/debug.h" and (re)compiling Tux Paint. - Recompiling MacPorts + Uninstalling Tux Paint - To recompile MacPorts to be usable on older versions of macOS, set - the following options in /opt/local/etc/macports/macports.conf: +Windows - buildfromsource always - macosx_deployment_target 10.10 + Using the Uninstaller - Then uninstall all MacPorts packages: + If you installed the Start Menu shortcuts (the default), then go to the + TuxPaint folder and select "Uninstall". A box will be displayed that will + confirm that you are about to uninstall Tux Paint and, if you are certain + that you want to permanently remove Tux Paint, click on the 'Uninstall' + button. - $ sudo port -fp uninstall installed + When it has finished, click on the close button. - Then reinstall all MacPorts packages needed by Tux Paint. Also - rebuild libimagequant using the updated Cargo package from MacPorts. + Using the Control Panel - As of this writing, all libraries Tux Paint requires from MacPorts - can be recompiled in this manner to run on macOS 10.10 Yosemite and - later on Intel CPUs, and macOS 11.0 Big Sur and later on Apple - Silicon. Unfortunately, although MacPorts has the option to enable - the building of universal libraries, several libraries Tux Paint - require cannot be built as universal libraries so they can only be - built to run natively on the hardware on which they were built. See - "Building a Universal Binary" below for instructions on how to build - Tux Paint as a Universal Binary. + It is also possible to use the entry "TuxPaint (remove only)" in the + Control Panel Add/Remove programs section. - Building for Apple Silicon +macOS - macOS for Applie Silicon requires all native Apple Silicon - applications be signed, even if it is signed "ad-hoc" (anonymously). - Because of this, compilers that produce native Apple Silicon - applications sign all produced binaries and libraries as a part of - the compilation process.^* However, the Tux Paint compilation - process modifies the libraries to be modular (using - install_name_tool) so they can be added into the application bundle, - which has the unfortunate side effect of breaking the signature. - This can be addressed by signing the application bundle ad-hoc - (example below) or using your own Apple Developer Identity if you - have one. The DMG file, if needed, must be created after signing the - App Bundle so the DMG file is created with signed App Bundle: + Delete "TuxPaint.app" from the "Applications" folder. Data files, + including the configuration files, stamps, and saved pictures, may be + found in "Library/Application Support/TuxPaint" (all users) and + "/Users/USERNAME/Library/Application Support/TuxPaint" (individual users). - $ codesign -s - TuxPaint.app - $ make TuxPaint.dmg +Linux - ^* For more information on the code signing requirements on the - Apple Silicon, see - https://developer.apple.com/documentation/macos-release-notes/macos-big-sur-11_0_1-universal-apps-release-notes#:~:text=New%20in%20macOS,pass%20through%20Gatekeeper. - - If you get an error that the application bundle is already signed, - remove it before signing:: - - $ codesign --remove-signature TuxPaint.app - - If you plan to combine the Apple Silicon bundle with the Intel CPU - bundle to produce the Universal bundle, the code signing must be - done after they are combined. See "Building a Universal Binary" - below. - - Building a Universal Binary - - To build Tux Paint as a Universal Binary, compile Tux Paint for the - Intel CPU and the Apple Silicon separately first. Then rename the - app bundle for the Intel CPU to TuxPaint-x86_64.app, and the bundle - for the Apple Silicon to TuxPaint-arm64.app, copy the app bundle - from the Intel machine to the Apple Silicon machine, then use the - provided build-universal.sh script to combine the two application - bundles as below. The produced bundle must be signed (see "Building - for Apple Silicon" above for more details). The DMG file, if - required, must be built after the signing: - - $ macos/build-universal.sh - $ codesign -s - TuxPaint.app - $ make TuxPaint.dmg - - ---------------------------------------------------------------------- - -Debugging - - Debugging output — to "STDOUT" on Linux and Unix, to a "stdout.txt" file - on Windows, and to the file "/tmp/tuxpaint.log" on macOS — can be - enabled by setting "DEBUG" (and, if verbose logging is wanted, - "VERBOSE") #defines in "src/debug.h" and (re)compiling Tux Paint. - - ---------------------------------------------------------------------- - -Uninstalling Tux Paint - - Windows - - Using the Uninstaller - - If you installed the Start Menu shortcuts (the default), then go to - the TuxPaint folder and select "Uninstall". A box will be displayed - that will confirm that you are about to uninstall Tux Paint and, if - you are certain that you want to permanently remove Tux Paint, click - on the 'Uninstall' button. - - When it has finished, click on the close button. - - Using the Control Panel - - It is also possible to use the entry "TuxPaint (remove only)" in the - Control Panel Add/Remove programs section. - - ---------------------------------------------------------------------- - - macOS - - Delete "TuxPaint.app" from the "Applications" folder. Data files, - including the configuration files, stamps, and saved pictures, may be - found in "Library/Application Support/TuxPaint" (all users) and - "/Users/USERNAME/Library/Application Support/TuxPaint" (individual - users). - - ---------------------------------------------------------------------- - - Linux - - Within the Tux Paint source directory (where you compiled Tux Paint), - you can use the "make uninstall" target to uninstall Tux Paint. By - default, this must be done by the "root" user ('superuser'), but if - you installed Tux Paint somewhere else (e.g., using a "PREFIX=..." - setting to "make" and "make install"), you may not, and will want to - provide those same settings here. (See the installation instructions - above for further information.) + Within the Tux Paint source directory (where you compiled Tux Paint), you + can use the "make uninstall" target to uninstall Tux Paint. By default, + this must be done by the "root" user ('superuser'), but if you installed + Tux Paint somewhere else (e.g., using a "PREFIX=..." setting to "make" and + "make install"), you may not, and will want to provide those same settings + here. (See the installation instructions above for further information.) diff --git a/docs/es_ES.UTF-8/html/EXTENDING.html b/docs/es_ES.UTF-8/html/EXTENDING.html index e4f13cc15..8731eb4c9 100644 --- a/docs/es_ES.UTF-8/html/EXTENDING.html +++ b/docs/es_ES.UTF-8/html/EXTENDING.html @@ -21,15 +21,17 @@ } div.keeptogether { page-break-inside: avoid; } section h1 { font-size: 2em; } - h1, h2, h3, h4 { font-family: sans; } + h1, h2, h3, h4, h5 { font-family: sans; } h1 { color: #800; page-break-before: always; break-before: always; } h2 { color: #440; page-break-after: avoid; break-after: avoid; } h3 { color: #080; page-break-after: avoid; break-after: avoid; } h4 { color: #008; page-break-after: avoid; break-after: avoid; } + h5 { color: #808; page-break-after: avoid; break-after: avoid; } h1 + p { page-break-inside: avoid; } h2 + p { page-break-inside: avoid; } h3 + p { page-break-inside: avoid; } h4 + p { page-break-inside: avoid; } + h5 + p { page-break-inside: avoid; } dt { font-size: large; color: #404; diff --git a/docs/es_ES.UTF-8/html/INSTALL.html b/docs/es_ES.UTF-8/html/INSTALL.html index de2dc9fd2..3a5238e5a 100644 --- a/docs/es_ES.UTF-8/html/INSTALL.html +++ b/docs/es_ES.UTF-8/html/INSTALL.html @@ -5,249 +5,312 @@ Tux Paint Installation Documentation + -
-

- Tux Paint
- versión 0.9.28
- Installation Documentation

+
+
+
+

+ Tux Paint
+ versión 0.9.28
+ Installation Documentation

-

- Copyright © 2002-2022 by various contributors; see AUTHORS.txt.
- https://tuxpaint.org/ -

+

+ Copyright © 2002-2022 by various contributors; see AUTHORS.txt.
+ https://tuxpaint.org/ +

-

- enero 20, 2022

-
+

+ marzo 31, 2022

+
+ -
+ + + + -
+ Table of Contents
- - - + + + +
- Table of Contents
+ +
+ - - - - - - +
+
+

+ + Requirements +

+
-
+
+
+

+ + Simple DirectMedia Layer library (libSDL) +

+
-

- - Requirements -

-
- -

- - Simple DirectMedia Layer library (libSDL) -

-

Tux Paint requires the Simple DirectMedia Layer Library (libSDL), an Open Source multimedia programming library available under the GNU Lesser General Public License (LGPL).

Along with libSDL, Tux Paint depends on a number of other SDL 'helper' libraries: SDL_Image (for graphics files), SDL_gfx (for some graphical functions, like rotation), SDL_TTF and (optionally) SDL_Pango (for True Type Font support) and, optionally, SDL_Mixer (for sound effects).

-

Linux/Unix Users:

-
-

- The SDL libraries are available as source-code, or as RPM or Debian packages for various distributions of Linux. They can be downloaded from:

- +
+
Linux/Unix
+
+

+ The SDL libraries are available as source-code, or as RPM or Debian packages for various distributions of Linux. They can be downloaded from:

+ -

- They are also typically available along with your Linux distribution (e.g. on an installation media, or available via package maintainance software like Debian's "apt").

+

+ They are also typically available along with your Linux distribution (e.g. on an installation media, or available via package maintainance software like Debian's "apt").

-

- Note: When installing libraries from packages, be sure to ALSO install the development versions of the packages. (For example, install both "SDL-1.2.4.rpm" and "SDL-1.2.4-devel.rpm".)

-
-
+

+ 💡 Note: When installing libraries from packages, be sure to ALSO install the development versions of the packages. (For example, install both "SDL-1.2.4.rpm" and "SDL-1.2.4-devel.rpm".)

+ + +
+ +
+
+

+ + Other Libraries +

+
-

- - Other Libraries -

-

Tux Paint also takes advantage of a number of other free, LGPL'd libraries. Under Linux, just like SDL, they should either already be installed, or are readily available for installation as part of your Linux distribution.

-

libPNG

-
-

- Tux Paint uses PNG (Portable Network Graphics) format for its data files. SDL_image will require libPNG be installed.

+
+
libPNG
+
+

+ Tux Paint uses PNG (Portable Network Graphics) format for its data files. SDL_image will require libPNG be installed.

-

- http://www.libpng.org/pub/png/libpng.html -

-
+

+ http://www.libpng.org/pub/png/libpng.html +

+ -

gettext

-
-

- Tux Paint uses your system's locale settings along with the "gettext" library to support various languages (e.g., Spanish). You'll need the gettext library installed.

+
gettext
+
+

+ Tux Paint uses your system's locale settings along with the "gettext" library to support various languages (e.g., Spanish). You'll need the gettext library installed.

-

- http://www.gnu.org/software/gettext/ -

-
+

+ http://www.gnu.org/software/gettext/ +

+ -

libpaper (Linux/Unix only)

-
-

- As of Tux Paint 0.9.17, Tux Paint can determine your system's default paper size (e.g., A4 or Letter), or can be told to use a particular paper size, thanks to "libpaper".

+
libpaper (Linux/Unix only)
+
+

+ As of Tux Paint 0.9.17, Tux Paint can determine your system's default paper size (e.g., A4 or Letter), or can be told to use a particular paper size, thanks to "libpaper".

-

- https://github.com/naota/libpaper -

-
+

+ https://github.com/naota/libpaper +

+ -

FriBiDi

-
-

- Tux Paint's "Text" and also "Label" tools support bidirectional languages, thanks to the "FriBiDi" library.

+
FriBiDi
+
+

+ Tux Paint's "Text" and also "Label" tools support bidirectional languages, thanks to the "FriBiDi" library.

-

- http://fribidi.org/ -

-
+

+ http://fribidi.org/ +

+ -

SVG graphics support

-
-

- As of Tux Paint 0.9.17, Tux Paint can load SVG (Scalable Vector Graphics) images as stamps. Two sets of libraries are supported, and SVG support can be completely disabled (via "make SVG_LIB:=")

+
SVG graphics support
+
+

+ As of Tux Paint 0.9.17, Tux Paint can load SVG (Scalable Vector Graphics) images as stamps. Two sets of libraries are supported, and SVG support can be completely disabled (via "make SVG_LIB:=")

-
librsvg-2 & libCairo2 (newer libraries)
- +
+
librsvg-2 & libCairo2 (newer libraries)
+
+ +
-
Older SVG libraries
- -
+
Older SVG libraries
+
+ +
+ + -

Animated GIF Export feature

-
-

- To support export of animated GIFs (slideshows), the "libimagequant" library (from the "pngquant2" project) is required.

+
Animated GIF Export feature
+
+

+ To support export of animated GIFs (slideshows), the "libimagequant" library (from the "pngquant2" project) is required.

-

- https://github.com/ImageOptim/libimagequant -

-
+

+ https://github.com/ImageOptim/libimagequant +

+ -

NetPBM Tools (optional) No longer used, by default

-
-

- Under Linux and Unix, earlier versions of Tux Paint used the NetPBM tools to assist with printing. (A PNG is generated by Tux Paint, and converted into a PostScript using the 'pngtopnm' and 'pnmtops' NetPBM command-line tools.)

+
NetPBM Tools (optional) No longer used, by default
+
+

+ 📜 Under Linux and Unix, earlier versions of Tux Paint used the NetPBM tools to assist with printing. (A PNG is generated by Tux Paint, and converted into a PostScript using the 'pngtopnm' and 'pnmtops' NetPBM command-line tools.)

-

- http://netpbm.sourceforge.net/ -

-
-
- +

+ http://netpbm.sourceforge.net/ +

+ + +
+
-
+
+
+

+ + Compiling and Installation +

+
-

- - Compiling and Installation -

-

Tux Paint is released under the GNU General Public License (GPL) (see "COPYING.txt" for details), and therefore the 'source code' to the program is available freely.

-

- - Windows Users -

-

- - noviembre 3, 2021 Shin-ichi TOYAMA dolphin6k@wmail.plala.or.jp <dolphin6k@wmail.plala.or.jp> - -

-
-

Compiling Set-Up

-
+
+
+

+ + Windows +

+ +

+ + noviembre 3, 2021 Shin-ichi TOYAMA dolphin6k@wmail.plala.or.jp <dolphin6k@wmail.plala.or.jp> + +

+
+ +
+
+

Compiling Set-Up

+
+

As of February 2005 (starting with Tux Paint 0.9.15), the "Makefile" includes support for building on a Windows system using MinGW/MSYS (https://sourceforge.net/projects/msys2/).

@@ -276,183 +339,194 @@

-
+

+ + Proceed to the next "MinGW 64bit (x86_64) toolchains" section, or skip to the "MinGW 32bit (i686) toolchains" section if you need only a 32bit build environment. +

-

- - Proceed to the next "MinGW 64bit (x86_64) toolchains" section, or skip 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 64bit development tools:

- - pacman -S mingw-w64-x86_64-toolchain - -
-

- -
- -

- 64bit (x86_64) dependency libraries for Tux Paint

- -
-

- You can install tools and libraries required for compiling Tux Paint on MSYS2/MINGW using "pacman" except for SDL_Pango.

-

- "ntldd" is a small tool which examine windows executable files to list Dynamic Link Library (.dll) files they depends on. Tux Paint's packaging process for binary distribution uses it to find required .dll files.

-

- FLTK is a cross-platform GUI toolkit used by "Tux Paint Config.". You can skip installing it if you are only building "Tux Paint".

-

-

- - $ pacman -S mingw-w64-x86_64-SDL_{image,mixer,ttf,gfx}
- $ pacman -S mingw-w64-x86_64-librsvg
- $ pacman -S mingw-w64-x86_64-fribidi
- $ pacman -S mingw-w64-x86_64-libimagequant
- $ pacman -S mingw-w64-x86_64-fltk
- $ pacman -S mingw-w64-x86_64-ntldd-git - -
-

-

- Note: Close the shell before proceeding to the remaining process.

- -
- -

- Install SDL_Pango on the 64bit environment

- -
-

- SDL_Pango should be installed manually.

-

- This time, use the MinGW "64bit" shell. Open the shell from the "Start Menu" -> "MSYS2 64bit" -> "MSYS2 MinGW 64-bit"

- -
SDL_Pango
- -
- -

- At first, you have to prepare source tar-ball and a required patch in the same directory.

- -

- Build and install SDL_Pango as follows.

- - $ tar zxvf SDL_Pango-0.1.2.tar.gz
- $ cd SDL_Pango-0.1.2/
- $ patch -p0 < ../SDL_Pango-configure-extra-api.patch
- $ ./configure --prefix=/mingw64 && make && make install - -
-

-
- -
- -

- - Proceed to the next "MinGW 32bit (i686) toolchains" section, or skip 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 32bit development tools:

- - pacman -S mingw-w64-i686-toolchain - -
-

- -
- -

- 32bit (i686) dependency libraries for Tux Paint

- -
-

- You can install tools and libraries required for compiling Tux Paint on MSYS2/MINGW using "pacman" except for SDL_Pango.

-

- "ntldd" is a small tool which examine windows executable files to list Dynamic Link Library (.dll) files they depends on. Tux Paint's packaging process for binary distribution uses it to find required .dll files.

-

- FLTK is a cross-platform GUI toolkit used by "Tux Paint Config.". You can skip installing it if you are only building "Tux Paint".

-

-

- - $ pacman -S mingw-w64-i686-SDL_{image,mixer,ttf,gfx}
- $ pacman -S mingw-w64-i686-librsvg
- $ pacman -S mingw-w64-i686-fribidi
- $ pacman -S mingw-w64-i686-libimagequant
- $ pacman -S mingw-w64-i686-fltk
- $ pacman -S mingw-w64-i686-ntldd-git - -
-

-

- Note: Close the shell before proceeding to the remaining process.

- -
- -

- Install SDL_Pango on the 32bit environment

- -
-

- SDL_Pango should be installed manually.

-

- This time, use the MinGW "32bit" shell. Open the shell from the "Start Menu" -> "MSYS2 64bit" -> "MSYS2 MinGW 32-bit"

- -
SDL_Pango
- -
+
+
+

+ + MinGW 64bit (x86_64) toolchains +

+

- At first, you have to prepare source tar-ball and a required patch in the same directory.

- -

- Build and install SDL_Pango as follows.

+ Within the MSYS2 shell, run the following command to install basic 64bit development tools:
- $ tar zxvf SDL_Pango-0.1.2.tar.gz
- $ cd SDL_Pango-0.1.2/
- $ patch -p0 < ../SDL_Pango-configure-extra-api.patch
- $ ./configure --prefix=/mingw32 && make && make install + pacman -S mingw-w64-x86_64-toolchain

-
+
-
+
+
+

+ 64bit (x86_64) dependency libraries for Tux Paint

+
- -
+

+ You can install tools and libraries required for compiling Tux Paint on MSYS2/MINGW using "pacman" except for SDL_Pango.

+

+ "ntldd" is a small tool which examine windows executable files to list Dynamic Link Library (.dll) files they depends on. Tux Paint's packaging process for binary distribution uses it to find required .dll files.

+

+ FLTK is a cross-platform GUI toolkit used by "Tux Paint Config.". You can skip installing it if you are only building "Tux Paint".

+

+

+ + $ pacman -S mingw-w64-x86_64-SDL_{image,mixer,ttf,gfx}
+ $ pacman -S mingw-w64-x86_64-librsvg
+ $ pacman -S mingw-w64-x86_64-fribidi
+ $ pacman -S mingw-w64-x86_64-libimagequant
+ $ pacman -S mingw-w64-x86_64-fltk
+ $ pacman -S mingw-w64-x86_64-ntldd-git + +
+

+

+ 💡 Note: Close the shell before proceeding to the remaining process.

+
-

- ImageMagick -

+
+
+

+ Install SDL_Pango on the 64bit environment

+
+ +

+ SDL_Pango should be installed manually.

+

+ This time, use the MinGW "64bit" shell. Open the shell from the "Start Menu" -> "MSYS2 64bit" -> "MSYS2 MinGW 64-bit"

+ +
+
+
SDL_Pango
+
+ +

+ At first, you have to prepare source tar-ball and a required patch in the same directory.

+

+

+ Build and install SDL_Pango as follows.

+ + $ tar zxvf SDL_Pango-0.1.2.tar.gz
+ $ cd SDL_Pango-0.1.2/
+ $ patch -p0 < ../SDL_Pango-configure-extra-api.patch
+ $ ./configure --prefix=/mingw64 && make && make install + +
+

+
+ +

+ + Proceed to the next "MinGW 32bit (i686) toolchains" section, or skip 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 32bit development tools:

+ + pacman -S mingw-w64-i686-toolchain + +
+

+
+ +
+
+

+ 32bit (i686) dependency libraries for Tux Paint

+
+ +

+ You can install tools and libraries required for compiling Tux Paint on MSYS2/MINGW using "pacman" except for SDL_Pango.

+

+ "ntldd" is a small tool which examine windows executable files to list Dynamic Link Library (.dll) files they depends on. Tux Paint's packaging process for binary distribution uses it to find required .dll files.

+

+ FLTK is a cross-platform GUI toolkit used by "Tux Paint Config.". You can skip installing it if you are only building "Tux Paint".

+

+

+ + $ pacman -S mingw-w64-i686-SDL_{image,mixer,ttf,gfx}
+ $ pacman -S mingw-w64-i686-librsvg
+ $ pacman -S mingw-w64-i686-fribidi
+ $ pacman -S mingw-w64-i686-libimagequant
+ $ pacman -S mingw-w64-i686-fltk
+ $ pacman -S mingw-w64-i686-ntldd-git + +
+

+

+ 💡 Note: Close the shell before proceeding to the remaining process.

+
+ +
+
+

+ Install SDL_Pango on the 32bit environment

+
+ +

+ SDL_Pango should be installed manually.

+

+ This time, use the MinGW "32bit" shell. Open the shell from the "Start Menu" -> "MSYS2 64bit" -> "MSYS2 MinGW 32-bit"

+ +
+
+
SDL_Pango
+
+ +

+ At first, you have to prepare source tar-ball and a required patch in the same directory.

+

+

+ Build and install SDL_Pango as follows.

+ + $ tar zxvf SDL_Pango-0.1.2.tar.gz
+ $ cd SDL_Pango-0.1.2/
+ $ patch -p0 < ../SDL_Pango-configure-extra-api.patch
+ $ ./configure --prefix=/mingw32 && make && make install + +
+

+
+ + +
+ +
+ +
+
+

+ ImageMagick +

+
-

ImageMagick is a compilation of command line tools to create, edit, compose, or convert bitmap images supporting quite a large number of image formats. Tux Paint uses two functions ("convert" and "composite") in it to generate thumbnails for startar images and templates during the build process.

@@ -468,13 +542,13 @@

You can make this permanent by adding the above to your the BASH shell configuration file, "~/.bash_profile".

-
+
-
+
+
+

Tux Paint

+
-

Tux Paint

- -

You can compile 64bit binaries using MSYS2 64bit shell, and 32bit binaries using MSYS2 32bit shell, respectively.

    @@ -490,16 +564,17 @@

-

- Note: At this point, you will want to build "Tux Paint Config." for Windows, so it can be included along with "Tux Paint", if you're making an official (or test) release. The build process will look for it in a directory named "tuxpaint-config" (with no version number, e.g., "tuxpaint-config-X.Y.Z"). See "Tux Paint Config."'s INSTALL.txt documentation for details.

+

+ 💡 Note: At this point, you will want to build "Tux Paint Config." for Windows, so it can be included along with "Tux Paint", if you're making an official (or test) release. The build process will look for it in a directory named "tuxpaint-config" (with no version number, e.g., "tuxpaint-config-X.Y.Z"). See "Tux Paint Config."'s INSTALL.txt documentation for details.

All the files needed for starting Tux Paint (and Tux Paint Config.) are collected in the directory for binary distribution "bdist" directory under "win32". You can start them by double-clicking their executable (.exe) files in the "bdist" directory.

- +
-
- -

Building the Tux Paint Windows Installer:

-
+
+
+

+ Building the Tux Paint Windows Installer

+

Inno Setup is used to build executable installer for Tux Paint. Therefore you have to install it in the first place.

@@ -509,14 +584,17 @@ Before building an installer, edit the "tuxpaint.iss" file and enable one of the lines starting with "#define BuildTarget=", depending on the architecture of the installer you want to create.

Then, you can easily build an executable installer by right-clicking on the "tuxpaint.iss" icon in the "win32" directory and selecting "Compile" on the list. It will run for a while, and eventually you will find a "tuxpaint-X.Y.Z-windows-<arch>-installer.exe" file in the same directory.

-
+ -
+
+
+

+ Running the Tux Paint Windows Installer

+
-

Running the Tux Paint Windows Installer:

-

- Double-click the Tux Paint installer executable (.EXE file) and follow the instructions. + Double-click the Tux Paint installer executable (.EXE file) and follow the instructions.

+

First, you will be asked to read the license. (It is the GNU General Public License (GPL), which is also available as "COPYING.txt".)

@@ -528,12 +606,14 @@

At this point, you can click 'Install' to install Tux Paint!

-
+
-
+
+
+

+ Changing the Settings Using the Shortcut

+
-

Changing the Settings Using the Shortcut:

-

To change program settings, right-click on the TuxPaint shortcut and select 'Properties' (at the bottom).

@@ -566,31 +646,38 @@

When you have finished, click "OK."

-
+
-
+
+
+

+ If Something Goes Wrong

+
-

If Something Goes Wrong:

-

If, when you double-click on the shortcut to run Tux Paint, nothing happens, it is probably because some of these command-line options are wrong. Open an Explorer like before, and look for a file called "stderr.txt" in the TuxPaint folder.

It will contain a description of what was wrong. Usually it will just be due to incorrect character-case (capital 'Z' instead of lowercase 'z') or a missing (or extra) '-' (dash).

-
- +
+ -
+
+
+

+ + Linux/Unix +

+
-

- - Linux/Unix Users -

-
-

Compiling:

-
-

- Note: Tux Paint does not use autoconf/automake, so there is no "./configure" script to run. Compiling should be straight-forward though, assuming everything Tux Paint needs is installed.

+
+
+

+ Compiling:

+
+ +

+ 💡 Note: Tux Paint does not use autoconf/automake, so there is no "./configure" script to run. Compiling should be straight-forward though, assuming everything Tux Paint needs is installed.

To compile the program from source, simply run the following command from a shell prompt (e.g., "$"):

@@ -600,13 +687,14 @@ $ make
-
+
-
+
+
+

+ Disabling SVG support (and hence Cairo, libSVG, and svg-cairo dependencies):

+
-

- Disabling SVG support (and hence Cairo, libSVG, and svg-cairo dependencies):

-

To disable SVG support (e.g., if your system is not currently supported by the Cairo library or other SVG-related dependencies), you can run "make" with "SVG_LIB= SVG_CFLAGS= NOSVGFLAG=NOSVG" added:

@@ -614,54 +702,64 @@ $ make SVG_LIB= SVG_CFLAGS=
-
+
-
+
+
+

+ Disabling Pango support (and hence Pango, Cairo, etc. dependencies):

+
-

- Disabling Pango support (and hence Pango, Cairo, etc. dependencies):

-
-

- Prior to version 0.9.18, Tux Paint used the libSDL_ttf library for rendering text using TrueType Fonts. Since 0.9.18, libSDL_Pango is used, as it has much greater support for internationalization. However, if you wish to disable the use of SDL_Pango, you may do so running "make" with "SDL_PANGO_LIB=" added:

+

+ 📜 Prior to version 0.9.18, Tux Paint used the libSDL_ttf library for rendering text using TrueType Fonts. Since 0.9.18, libSDL_Pango is used, as it has much greater support for internationalization. However, if you wish to disable the use of SDL_Pango, you may do so running "make" with "SDL_PANGO_LIB=" added:

$ make SDL_PANGO_LIB=
-
+
-
+
+
+

+ Disabling Sound at Compile-time

+
-

Disabling Sound at Compile-time:

-
- If you don't have a sound card, or would prefer to build the program with no sound support (and therefore without a the SDL_mixer dependency), you can run "make" with "SDL_MIXER_LIB=" added:

+

+ If you don't have a sound card, or would prefer to build the program with no sound support (and therefore without a the SDL_mixer dependency), you can run "make" with "SDL_MIXER_LIB=" added:

$ make SDL_MIXER_LIB=
-
+
-
+
+
+

+ Other options

+
-

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 get errors:

-

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 "-dev" or "-devel" packages as well, otherwise you won't be able to compile Tux Paint (and other programs) from source!

-
+
-
+
+
+

+ Installng

+
-

Installng:

-

Assuming no fatal errors occured, you can now install the program so that it can be run by users on the system. By default, this must be done by the "root" user ('superuser'). Switch to "root" by typing the command:

@@ -698,11 +796,15 @@
-

- Note: By default, "tuxpaint", the executable program, is placed in "/usr/local/bin/". The data files (images, sounds, etc.) are placed in "/usr/local/share/tuxpaint/".

+

+ 💡 Note: By default, "tuxpaint", the executable program, is placed in "/usr/local/bin/". The data files (images, sounds, etc.) are placed in "/usr/local/share/tuxpaint/".

+ +
+
+

+ Changing Where Things Go

+
-
Changing Where Things Go
-

You can change where things will go by setting "Makefile"variables on the command line. "DESTDIR" is used to place output in a staging area for package creation. "PREFIX" is the basis of where all other files go, and is, by default, set to "/usr/local".

@@ -737,30 +839,34 @@ Where the translation files for Tux Paint will go, and where Tux Paint will look for them. (Set to "$(PREFIX)/share/locale/") (Final location of a translation file will be under the locale's directory (e.g., "es" for Spanish), within the "LC_MESSAGES" subdirectory.) -

- Note: This list is out of date. See "Makefile" and "Makefile-i18n" for a complete list.

-
- - +

+ 💡 Note: This list is out of date. See "Makefile" and "Makefile-i18n" for a complete list.

+
+
+ -
+
+
+

+ + macOS +

+

+ + enero 20, 2022 Mark Kim <markuskimius@gmail.com> + +

+
-

- - macOS Users -

-

- - enero 20, 2022 Mark 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

-
+
+
+

+ 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:

@@ -792,8 +898,13 @@
* Not available from MacPorts as of this writing, see below.

-
libimagequant
-
+
+
+

+ 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.

@@ -805,17 +916,18 @@

- -
+

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

+
-

How to Build

-

Simply, run:

@@ -827,12 +939,14 @@

Additional steps may be required when building for the Apple Silicon. See "Building for Apple Silicon" below.

-
+
-
+
+
+

+ Known Issues

+
-

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.
    @@ -841,12 +955,14 @@
    Alternatively, Tux Paint and all of its library dependencies may be compiled with appropriate options to be runnable on older versions of macOS. These options are already set on Tux Paint, so only its dependencies (from MacPorts) need to be recompiled. See "Recompiling MacPorts" below for the instructions.
-
+
-
+
+
+

+ Old Versions 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

@@ -870,11 +986,14 @@

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.

+
- +
+
+

+ Recompiling MacPorts

+
-

Recompiling MacPorts

-

To recompile MacPorts to be usable on older versions of macOS, set the following options in /opt/local/etc/macports/macports.conf:

@@ -897,18 +1016,21 @@

As of this writing, all libraries Tux Paint requires from MacPorts can be recompiled in this manner to run on macOS 10.10 Yosemite and later on Intel CPUs, and macOS 11.0 Big Sur and later on Apple Silicon. Unfortunately, although MacPorts has the option to enable the building of universal libraries, several libraries Tux Paint require cannot be built as universal libraries so they can only be built to run natively on the hardware on which they were built. See "Building a Universal Binary" below for instructions on how to build Tux Paint as a Universal Binary.

-
+
+ +
+
+

+ Building for Apple Silicon

+
-

Building for Apple Silicon

-

macOS for Applie Silicon requires all native Apple Silicon applications be signed, even if it is signed "ad-hoc" (anonymously). Because of this, compilers that produce native Apple Silicon applications sign all produced binaries and libraries as a part of the compilation process.* However, the Tux Paint compilation process modifies the libraries to be modular (using install_name_tool) so they can be added into the application bundle, which has the unfortunate side effect of breaking the signature. This can be addressed by signing the application bundle ad-hoc (example below) or using your own Apple Developer Identity if you have one. The DMG file, if needed, must be created after signing the App Bundle so the DMG file is created with signed App Bundle:

$ codesign -s - TuxPaint.app
$ make TuxPaint.dmg
- * For more information on the code signing requirements on the Apple Silicon, see https://developer.apple.com/documentation/macos-release-notes/macos-big-sur-11_0_1-universal-apps-release-notes#:~:text=New%20in%20macOS,pass%20through%20Gatekeeper. -

+ * For more information on the code signing requirements on the Apple Silicon, see https://developer.apple.com/documentation/macos-release-notes/macos-big-sur-11_0_1-universal-apps-release-notes#:~:text=New%20in%20macOS,pass%20through%20Gatekeeper.

If you get an error that the application bundle is already signed, remove it before signing::

$ codesign --remove-signature TuxPaint.app @@ -916,10 +1038,14 @@

If you plan to combine the Apple Silicon bundle with the Intel CPU bundle to produce the Universal bundle, the code signing must be done after they are combined. See "Building a Universal Binary" below.

-
+
+ +
+
+

+ Building a Universal Binary

+
-

Building a Universal Binary

-

To build Tux Paint as a Universal Binary, compile Tux Paint for the Intel CPU and the Apple Silicon separately first. Then rename the app bundle for the Intel CPU to TuxPaint-x86_64.app, and the bundle for the Apple Silicon to TuxPaint-arm64.app, copy the app bundle from the Intel machine to the Apple Silicon machine, then use the provided build-universal.sh script to combine the two application bundles as below. The produced bundle must be signed (see "Building for Apple Silicon" above for more details). The DMG file, if required, must be built after the signing:

@@ -929,71 +1055,87 @@

-
+
- + - + -
+
+
+

+ + Debugging +

+
-

- - Debugging -

-
- Debugging output — to "STDOUT" on Linux and Unix, to a "stdout.txt" file on Windows, and to the file "/tmp/tuxpaint.log" on macOS — can be enabled by setting "DEBUG" (and, if verbose logging is wanted, "VERBOSE") #defines in "src/debug.h" and (re)compiling Tux Paint.
+

+ ⚙ Debugging output — to "STDOUT" on Linux and Unix, to a "stdout.txt" file on Windows, and to the file "/tmp/tuxpaint.log" on macOS — can be enabled by setting "DEBUG" (and, if verbose logging is wanted, "VERBOSE") #defines in "src/debug.h" and (re)compiling Tux Paint.

+
-
+
+
+

+ + Uninstalling Tux Paint +

+
+ +
+
+

+ + Windows +

+
+ +
+
+

+ Using the Uninstaller

+
-

- - Uninstalling Tux Paint

- -
-

- - Windows -

-
-

Using the Uninstaller

-

If you installed the Start Menu shortcuts (the default), then go to the TuxPaint folder and select "Uninstall". A box will be displayed that will confirm that you are about to uninstall Tux Paint and, if you are certain that you want to permanently remove Tux Paint, click on the 'Uninstall' button.

When it has finished, click on the close button.

-
+
+ +
+
+

+ Using the Control Panel

+
-

Using the Control Panel

-

It is also possible to use the entry "TuxPaint (remove only)" in the Control Panel Add/Remove programs section.

-
- +
+
-
+
+
+

+ + macOS +

+
-

- - macOS -

- -

Delete "TuxPaint.app" from the "Applications" folder. Data files, including the configuration files, stamps, and saved pictures, may be found in "Library/Application Support/TuxPaint" (all users) and "/Users/USERNAME/Library/Application Support/TuxPaint" (individual users).

-
+
-
+
+
+

+ + Linux +

+
-

- - Linux -

-

Within the Tux Paint source directory (where you compiled Tux Paint), you can use the "make uninstall" target to uninstall Tux Paint. By default, this must be done by the "root" user ('superuser'), but if you installed Tux Paint somewhere else (e.g., using a "PREFIX=..." setting to "make" and "make install"), you may not, and will want to provide those same settings here. (See the installation instructions above for further information.)

-
-
+
+
diff --git a/docs/es_ES.UTF-8/html/OPTIONS.html b/docs/es_ES.UTF-8/html/OPTIONS.html index f89ac82b8..58bb00c4a 100644 --- a/docs/es_ES.UTF-8/html/OPTIONS.html +++ b/docs/es_ES.UTF-8/html/OPTIONS.html @@ -21,15 +21,17 @@ } div.keeptogether { page-break-inside: avoid; } section h1 { font-size: 2em; } - h1, h2, h3, h4 { font-family: sans; } + h1, h2, h3, h4, h5 { font-family: sans; } h1 { color: #800; page-break-before: always; break-before: always; } h2 { color: #440; page-break-after: avoid; break-after: avoid; } h3 { color: #080; page-break-after: avoid; break-after: avoid; } h4 { color: #008; page-break-after: avoid; break-after: avoid; } + h5 { color: #808; page-break-after: avoid; break-after: avoid; } h1 + p { page-break-inside: avoid; } h2 + p { page-break-inside: avoid; } h3 + p { page-break-inside: avoid; } h4 + p { page-break-inside: avoid; } + h5 + p { page-break-inside: avoid; } dt { font-size: large; color: #404; diff --git a/docs/es_ES.UTF-8/html/PNG.html b/docs/es_ES.UTF-8/html/PNG.html index c56e9a538..cad9a5cc8 100644 --- a/docs/es_ES.UTF-8/html/PNG.html +++ b/docs/es_ES.UTF-8/html/PNG.html @@ -21,15 +21,17 @@ } div.keeptogether { page-break-inside: avoid; } section h1 { font-size: 2em; } - h1, h2, h3, h4 { font-family: sans; } + h1, h2, h3, h4, h5 { font-family: sans; } h1 { color: #800; page-break-before: always; break-before: always; } h2 { color: #440; page-break-after: avoid; break-after: avoid; } h3 { color: #080; page-break-after: avoid; break-after: avoid; } h4 { color: #008; page-break-after: avoid; break-after: avoid; } + h5 { color: #808; page-break-after: avoid; break-after: avoid; } h1 + p { page-break-inside: avoid; } h2 + p { page-break-inside: avoid; } h3 + p { page-break-inside: avoid; } h4 + p { page-break-inside: avoid; } + h5 + p { page-break-inside: avoid; } dt { font-size: large; color: #404; diff --git a/docs/es_ES.UTF-8/html/README.html b/docs/es_ES.UTF-8/html/README.html index 66023a6e8..250b85949 100644 --- a/docs/es_ES.UTF-8/html/README.html +++ b/docs/es_ES.UTF-8/html/README.html @@ -21,15 +21,17 @@ } div.keeptogether { page-break-inside: avoid; } section h1 { font-size: 2em; } - h1, h2, h3, h4 { font-family: sans; } + h1, h2, h3, h4, h5 { font-family: sans; } h1 { color: #800; page-break-before: always; break-before: always; } h2 { color: #440; page-break-after: avoid; break-after: avoid; } h3 { color: #080; page-break-after: avoid; break-after: avoid; } h4 { color: #008; page-break-after: avoid; break-after: avoid; } + h5 { color: #808; page-break-after: avoid; break-after: avoid; } h1 + p { page-break-inside: avoid; } h2 + p { page-break-inside: avoid; } h3 + p { page-break-inside: avoid; } h4 + p { page-break-inside: avoid; } + h5 + p { page-break-inside: avoid; } dt { font-size: large; color: #404; diff --git a/docs/es_ES.UTF-8/html/SIGNALS.html b/docs/es_ES.UTF-8/html/SIGNALS.html index 7d7b58b16..ccd3fea36 100644 --- a/docs/es_ES.UTF-8/html/SIGNALS.html +++ b/docs/es_ES.UTF-8/html/SIGNALS.html @@ -21,15 +21,17 @@ } div.keeptogether { page-break-inside: avoid; } section h1 { font-size: 2em; } - h1, h2, h3, h4 { font-family: sans; } + h1, h2, h3, h4, h5 { font-family: sans; } h1 { color: #800; page-break-before: always; break-before: always; } h2 { color: #440; page-break-after: avoid; break-after: avoid; } h3 { color: #080; page-break-after: avoid; break-after: avoid; } h4 { color: #008; page-break-after: avoid; break-after: avoid; } + h5 { color: #808; page-break-after: avoid; break-after: avoid; } h1 + p { page-break-inside: avoid; } h2 + p { page-break-inside: avoid; } h3 + p { page-break-inside: avoid; } h4 + p { page-break-inside: avoid; } + h5 + p { page-break-inside: avoid; } dt { font-size: large; color: #404; diff --git a/docs/es_ES.UTF-8/html/SVG.html b/docs/es_ES.UTF-8/html/SVG.html index 1e7cff4da..97e5862cc 100644 --- a/docs/es_ES.UTF-8/html/SVG.html +++ b/docs/es_ES.UTF-8/html/SVG.html @@ -21,15 +21,17 @@ } div.keeptogether { page-break-inside: avoid; } section h1 { font-size: 2em; } - h1, h2, h3, h4 { font-family: sans; } + h1, h2, h3, h4, h5 { font-family: sans; } h1 { color: #800; page-break-before: always; break-before: always; } h2 { color: #440; page-break-after: avoid; break-after: avoid; } h3 { color: #080; page-break-after: avoid; break-after: avoid; } h4 { color: #008; page-break-after: avoid; break-after: avoid; } + h5 { color: #808; page-break-after: avoid; break-after: avoid; } h1 + p { page-break-inside: avoid; } h2 + p { page-break-inside: avoid; } h3 + p { page-break-inside: avoid; } h4 + p { page-break-inside: avoid; } + h5 + p { page-break-inside: avoid; } dt { font-size: large; color: #404; diff --git a/docs/fr_FR.UTF-8/INSTALL.txt b/docs/fr_FR.UTF-8/INSTALL.txt index b98122ac6..45b1d8c05 100644 --- a/docs/fr_FR.UTF-8/INSTALL.txt +++ b/docs/fr_FR.UTF-8/INSTALL.txt @@ -5,890 +5,812 @@ Copyright © 2002-2022 by divers contributeurs; see AUTHORS.txt. https://tuxpaint.org/ - janvier 20, 2022 + mars 31, 2022 - ---------------------------------------------------------------------- + +--------------------------------------------------------+ + |Table des matières | + |--------------------------------------------------------| + | * Exigences | + | * Biliothèque Simple DirectMedia Layer (libSDL) | + | * Autres bibliothèques | + | * Compilation et installation | + | * Windows | + | * Linux/Unix | + | * macOS | + | * Débogage | + | * Désinstallation de Tux Paint | + | * Windows | + | * macOS | + | * Linux | + +--------------------------------------------------------+ - +--------------------------------------------------------+ - |Table des matières | - |--------------------------------------------------------| - | * Exigences | - | * Biliothèque Simple DirectMedia Layer (libSDL) | - | * Autres bibliothèques | - | * Compilation et installation | - | * Utilisateurs de Windows | - | * Utilisateurs de Linux/Unix | - | * Utilisateurs de macOS | - | * Débogage | - | * Désinstallation de Tux Paint | - | * Windows | - | * macOS | - | * Linux | - +--------------------------------------------------------+ + Exigences - ---------------------------------------------------------------------- +Biliothèque Simple DirectMedia Layer (libSDL) -Exigences + Tux Paint nécessite la bibliothèque de couches DirectMedia simple + (libSDL), une bibliothèque de programmation multimédia Open Source + disponible sous la Licence publique générale limitée GNU (LGPL). - Biliothèque Simple DirectMedia Layer (libSDL) + Avec libSDL, Tux Paint dépend d'un certain nombre d'autres bibliothèques + 'd'aide' SDL : SDL_Image (pour les fichiers graphiques), SDL_gfx (pour + certaines fonctions graphiques, comme la rotation), SDL_TTF et (en option) + SDL_Pango (pour la prise en charge des polices True Type) et, + éventuellement, SDL_Mixer (pour les effets sonores). - Tux Paint nécessite la bibliothèque de couches DirectMedia simple - (libSDL), une bibliothèque de programmation multimédia Open Source - disponible sous la Licence publique générale limitée GNU (LGPL). + Linux/Unix - Avec libSDL, Tux Paint dépend d'un certain nombre d'autres - bibliothèques 'd'aide' SDL : SDL_Image (pour les fichiers graphiques), - SDL_gfx (pour certaines fonctions graphiques, comme la rotation), - SDL_TTF et (en option) SDL_Pango (pour la prise en charge des polices - True Type) et, éventuellement, SDL_Mixer (pour les effets sonores). + Les bibliothèques SDL sont disponibles en tant que code source, ou + en tant que paquets RPM ou Debian pour diverses distributions de + Linux. Ils peuvent être téléchargés à partir de : - Utilisateurs de Linux/Unix : + * libSDL: http://www.libsdl.org/ + * SDL_Image: http://www.libsdl.org/projects/SDL_image/ + * SDL_gfx: + https://www.ferzkopp.net/wordpress/2016/01/02/sdl_gfx-sdl2_gfx/ + (https://sourceforge.net/projects/sdlgfx/) + * SDL_TTF: http://www.libsdl.org/projects/SDL_ttf/ + * SDL_Pango: http://sourceforge.net/projects/sdlpango/ + (optionnel) + * SDL_Mixer: http://www.libsdl.org/projects/SDL_mixer/ + (optionnel) - Les bibliothèques SDL sont disponibles en tant que code source, ou - en tant que paquets RPM ou Debian pour diverses distributions de - Linux. Ils peuvent être téléchargés à partir de : + Elles sont aussi parmi les paquets inclus dans votre distribution + (par ex. sur le media d'installation, ou via la maintenance de vos + logiciels comme la commande apt de Debian). - * libSDL: http://www.libsdl.org/ - * SDL_Image: http://www.libsdl.org/projects/SDL_image/ - * SDL_gfx: - https://www.ferzkopp.net/wordpress/2016/01/02/sdl_gfx-sdl2_gfx/ - (https://sourceforge.net/projects/sdlgfx/) - * SDL_TTF: http://www.libsdl.org/projects/SDL_ttf/ - * SDL_Pango: http://sourceforge.net/projects/sdlpango/ (optionnel) - * SDL_Mixer: http://www.libsdl.org/projects/SDL_mixer/ (optionnel) - - Elles sont aussi parmi les paquets inclus dans votre distribution - (par ex. sur le media d'installation, ou via la maintenance de vos - logiciels comme la commande apt de Debian). - - Remarque ;lors de l'installation à partir de packages, assurez-vous - d'installer AUSSI les versions de développement des paquets (Par ex. - installez les deux "SDL-1.2.4.rpm" et "SDL-1.2.4-devel.rpm".) + 💡 Note: When installing libraries from packages, be sure to ALSO + install the development versions of the packages. (For example, + install both "SDL-1.2.4.rpm" and "SDL-1.2.4-devel.rpm".) Autres bibliothèques - Tux Paint profite également d'un certain nombre d'autres bibliothèques - gratuites LGPL. Sous Linux, tout comme SDL, ils devraient être soit - déjà installées, soit facilement disponibles avec votre distribution - Linux. + Tux Paint profite également d'un certain nombre d'autres bibliothèques + gratuites LGPL. Sous Linux, tout comme SDL, ils devraient être soit déjà + installées, soit facilement disponibles avec votre distribution Linux. - libPNG + libPNG - Tux Paint utilise le format PNG (Portable Network Graphics) pour ses - fichiers de données. SDL_image nécessitera l'installation de libPNG. + Tux Paint utilise le format PNG (Portable Network Graphics) pour + ses fichiers de données. SDL_image nécessitera l'installation de + libPNG. - http://www.libpng.org/pub/png/libpng.html + http://www.libpng.org/pub/png/libpng.html - gettext + gettext - Tux Paint utilise les paramètres régionaux de votre système avec la - bibliothèque "gettext" pour prendre en charge plusieurs langues (par - exemple, l'espagnol). Vous aurez besoin d'installer la bibliothèque - de gettext. + Tux Paint utilise les paramètres régionaux de votre système avec + la bibliothèque "gettext" pour prendre en charge plusieurs langues + (par exemple, l'espagnol). Vous aurez besoin d'installer la + bibliothèque de gettext. - http://www.gnu.org/software/gettext/ + http://www.gnu.org/software/gettext/ - libpaper (Linux/Unix uniquement) + libpaper (Linux/Unix uniquement) - Depuis Tux Paint 0.9.17, Tux Paint peut déterminer le format de - papier par défaut (par exemple, A4 ou Lettre), ou peut être invité à - utiliser un format particulier, ceci grâce à libpaper. + Depuis Tux Paint 0.9.17, Tux Paint peut déterminer le format de + papier par défaut (par exemple, A4 ou Lettre), ou peut être invité + à utiliser un format particulier, ceci grâce à libpaper. - https://github.com/naota/libpaper + https://github.com/naota/libpaper - FriBiDi + FriBiDi - Les outils "Texte" et "Étiquette" de Tux Paint supportent les - langues bidirectionnelles, grâce à la bibliothèque "FriBidi". + Les outils "Texte" et "Étiquette" de Tux Paint supportent les + langues bidirectionnelles, grâce à la bibliothèque "FriBidi". - http://fribidi.org/ + http://fribidi.org/ - Support des graphismes SVG + Support des graphismes SVG - À partir de Tux Paint 0.9.17, Tux Paint peut prendre en charge les - images SVG (Scalable Vector Graphics) pour les tampons. Deux - ensembles de bibliothèques sont pris en charge et le support SVG - peut être complètement désactivé (via "make SVG_LIB:==") + À partir de Tux Paint 0.9.17, Tux Paint peut prendre en charge les + images SVG (Scalable Vector Graphics) pour les tampons. Deux + ensembles de bibliothèques sont pris en charge et le support SVG + peut être complètement désactivé (via "make SVG_LIB:==") - librsvg-2 & libCairo2 (nouvelles bibliothèques) + librsvg-2 & libCairo2 (nouvelles bibliothèques) + * libRSVG 2: http://librsvg.sourceforge.net/ + * Cairo 2: http://www.cairographics.org/ + * Celles-ci dépendent aussi de : + * GdkPixbuf & GLib: http://www.gtk.org/ + * Pango: http://www.pango.org/ - * libRSVG 2: http://librsvg.sourceforge.net/ - * Cairo 2: http://www.cairographics.org/ - * Celles-ci dépendent aussi de : - * GdkPixbuf & GLib: http://www.gtk.org/ - * Pango: http://www.pango.org/ + Anciennes bibliothèques + * libcairo1, libsvg1, & libsvg-cairo1: + http://www.cairographics.org/ + * Celles-ci dépendent aussi de : + * libxml2: + https://gitlab.gnome.org/GNOME/libxml2 - Anciennes bibliothèques + Fonction d'exportation de GIF animés - * libcairo1, libsvg1, & libsvg-cairo1: - http://www.cairographics.org/ - * Celles-ci dépendent aussi de : - * libxml2: https://gitlab.gnome.org/GNOME/libxml2 + Pour prendre en compte l'exportation de GIF animés (diaporama), la + bibliothèque "libimagequant" (issue du projet "pngquant" est + nécessaire. - Fonction d'exportation de GIF animés + https://github.com/ImageOptim/libimagequant - Pour prendre en compte l'exportation de GIF animés (diaporama), la - bibliothèque "libimagequant" (issue du projet "pngquant" est - nécessaire. + Outils NetPBM (optionnel) ne sont plus utilisés par défaut - https://github.com/ImageOptim/libimagequant + 📜 Sous Linux et Unix, les anciennes versions de Tux Paint + utilisaient les outils NetPBM comme aide à l'impression. (Un PNG + est généré par TuxPaint et converti en PostScript en utilisant en + ligne de commande les outils NetPBM pngtopnm et pnmtops.) - Outils NetPBM (optionnel) ne sont plus utilisés par défaut + http://netpbm.sourceforge.net/ - Sous Linux et Unix, les anciennes versions de Tux Paint utilisaient - les outils NetPBM comme aide à l'impression. (Un PNG est généré par - TuxPaint et converti en PostScript en utilisant en ligne de commande - les outils NetPBM pngtopnm et pnmtops.) + Compilation et installation - http://netpbm.sourceforge.net/ + Tux Paint est publié sous la licence publique générale GNU (GPL) (voir + "COPYING.txt" pour plus de détails), et donc le 'code source' du programme + est disponible gratuitement. - ---------------------------------------------------------------------- +Windows -Compilation et installation + novembre 3, 2021 Shin-ichi TOYAMA dolphin6k@wmail.plala.or.jp + - Tux Paint est publié sous la licence publique générale GNU (GPL) (voir - "COPYING.txt" pour plus de détails), et donc le 'code source' du - programme est disponible gratuitement. + Réglages pour compilation - Utilisateurs de Windows + Depuis février 2005 (à partir de Tux Paint 0.9.15), le "Makefile" inclut + la prise en charge de la construction sur un système Windows à l'aide de + MinGW/MSYS (https://sourceforge.net/projects/msys2/). - novembre 3, 2021 Shin-ichi TOYAMA dolphin6k@wmail.plala.or.jp - + Beaucoup d'outils et de bibliothèques sont nécessaires pour élaborer Tux + Paint. Le système de gestion de paquet "pacman" apporte une aide pour + installer automatiquement, en résolvant les dépendances nombreuses. - Réglages pour compilation + Téléchargez le dernier environnement MSYS2 à partir de + https://sourceforge.net/projects/msys2/files/Base/ et installez-le où vous + voulez (par défaut "C:\msys64") - Depuis février 2005 (à partir de Tux Paint 0.9.15), le "Makefile" - inclut la prise en charge de la construction sur un système Windows - à l'aide de MinGW/MSYS (https://sourceforge.net/projects/msys2/). + Ouvrez le shell MSYS2 via le "Menu de Démarrage" ->"MSYS2 64bit" -> "MSTS2 + MSYS" et exécutez la commande suivante (pressez [Entrée] ou [Retour] pour + accepter par défaut toutes les questions) : - Beaucoup d'outils et de bibliothèques sont nécessaires pour élaborer - Tux Paint. Le système de gestion de paquet "pacman" apporte une aide - pour installer automatiquement, en résolvant les dépendances - nombreuses. + pacman -Syu - Téléchargez le dernier environnement MSYS2 à partir de - https://sourceforge.net/projects/msys2/files/Base/ et installez-le - où vous voulez (par défaut "C:\msys64") + Ceci mettra à jour tout le système et la fenêtre de se fermera + automatiquement. Répétez les étapes précédentes encore une fois pour + finaliser le process restant de mise à jour. - Ouvrez le shell MSYS2 via le "Menu de Démarrage" ->"MSYS2 64bit" -> - "MSTS2 MSYS" et exécutez la commande suivante (pressez [Entrée] ou - [Retour] pour accepter par défaut toutes les questions) : + Sous le shell MSYS2, exécutez la commande suivante pour installer outils + basiques pour le développement : - pacman -Syu + pacman -S base-devel msys2-devel git - Ceci mettra à jour tout le système et la fenêtre de se fermera - automatiquement. Répétez les étapes précédentes encore une fois pour - finaliser le process restant de mise à jour. - - Sous le shell MSYS2, exécutez la commande suivante pour installer - outils basiques pour le développement : - - pacman -S base-devel msys2-devel git - - Allez à la prochaine section "chaînes d'outils MinGW 64bit (x86_64) ", - ou bien à la section "chaînes d'outils MinGW 32bit (i686)" si vous ne - voulez qu'un environnement de travail 32bit. + Allez à la prochaine section "chaînes d'outils MinGW 64bit (x86_64) ", ou + bien à la section "chaînes d'outils MinGW 32bit (i686)" si vous ne voulez + qu'un environnement de travail 32bit. ------------------------------------------------------- Chaînes d'outils MinGW 64bit (x86_64) - Sous le shell MSYS2, exécutez la commande suivante pour installer - outils basiques pour le développement 64bit : + Sous le shell MSYS2, exécutez la commande suivante pour installer outils + basiques pour le développement 64bit : - pacman -S mingw-w64-x86_64-toolchain + pacman -S mingw-w64-x86_64-toolchain bibliothèques de dépendance 64bit (x86_64) pour Tux Paint - You can install tools and libraries required for compiling Tux Paint - on MSYS2/MINGW using "pacman" except for SDL_Pango. + You can install tools and libraries required for compiling Tux Paint on + MSYS2/MINGW using "pacman" except for SDL_Pango. - "ntldd" est un petit outil qui examine les fichiers exécutables de - windows en vue de lister les fichiers DLL (.dll) qui leur sont - nécessaires. Le process de fabrication de Tux Paint pour fournir des - fichiers binaires s'en sert pour trouver les fichiers .dll requis. + "ntldd" est un petit outil qui examine les fichiers exécutables de windows + en vue de lister les fichiers DLL (.dll) qui leur sont nécessaires. Le + process de fabrication de Tux Paint pour fournir des fichiers binaires + s'en sert pour trouver les fichiers .dll requis. - FLTK est un ensemble d'outils multiplateforme utilisé par "Tux Paint - Config.". Vous pouvez ne pas l'installer si vous compilez seulement - "Tux Paint". + FLTK est un ensemble d'outils multiplateforme utilisé par "Tux Paint + Config.". Vous pouvez ne pas l'installer si vous compilez seulement "Tux + Paint". - $ pacman -S mingw-w64-x86_64-SDL_{image,mixer,ttf,gfx} - $ pacman -S mingw-w64-x86_64-librsvg - $ pacman -S mingw-w64-x86_64-fribidi - $ pacman -S mingw-w64-x86_64-libimagequant - $ pacman -S mingw-w64-x86_64-fltk - $ pacman -S mingw-w64-x86_64-ntldd-git + $ pacman -S mingw-w64-x86_64-SDL_{image,mixer,ttf,gfx} + $ pacman -S mingw-w64-x86_64-librsvg + $ pacman -S mingw-w64-x86_64-fribidi + $ pacman -S mingw-w64-x86_64-libimagequant + $ pacman -S mingw-w64-x86_64-fltk + $ pacman -S mingw-w64-x86_64-ntldd-git - Nota : Fermez l'interpréteur de commandes avant de passer à la - suite. + 💡 Nota : Fermez l'interpréteur de commandes avant de passer à la suite. Install SDL_Pango on the 64bit environment - SDL_Pango should be installed manually. + SDL_Pango should be installed manually. - Cette fois-ci, utilisez le shell MinGW "64bit". Ouvrez le shell - depuis le "Menu de Démarrage" -> "MSYS2 64bit" -> "MSYS2 MinGW - 64-bit" + Cette fois-ci, utilisez le shell MinGW "64bit". Ouvrez le shell depuis le + "Menu de Démarrage" -> "MSYS2 64bit" -> "MSYS2 MinGW 64-bit" SDL_Pango - Tout d'abord, vous devrez préparer l'archive source et un patch - qui est requis, dans le même répertoire. + Tout d'abord, vous devrez préparer l'archive source et un patch qui est + requis, dans le même répertoire. + * Télécharger fichier source de SDL_Pango-0.1.2 depuis La page SDL_Pango + sur Sourceforge.net. + * Télécharger un fichier patch depuis La page web de John Popplewell + traitant des "instructions pour la compilation de Tux Paint - + MinGW/MSYS". (Ceci ajoute une fonctionnalité supplémentaire (requise) + à SDL_Pango.) - * Télécharger fichier source de SDL_Pango-0.1.2 depuis La page - SDL_Pango sur Sourceforge.net. - * Télécharger un fichier patch depuis La page web de John - Popplewell traitant des "instructions pour la compilation de - Tux Paint - MinGW/MSYS". (Ceci ajoute une fonctionnalité - supplémentaire (requise) à SDL_Pango.) + Compiler et installer SDL_Pango comme suit. - Compiler et installer SDL_Pango comme suit. + $ tar zxvf SDL_Pango-0.1.2.tar.gz + $ cd SDL_Pango-0.1.2/ + $ patch -p0 < ../SDL_Pango-configure-extra-api.patch + $ ./configure --prefix=/mingw64 && make && make install - $ tar zxvf SDL_Pango-0.1.2.tar.gz - $ cd SDL_Pango-0.1.2/ - $ patch -p0 < ../SDL_Pango-configure-extra-api.patch - $ ./configure --prefix=/mingw64 && make && make install - - Aller à la prochaine section "chaines d'outils MinGW 32bit (i686)", ou - bien aller directement à la section "ImageMagick" si vous n'avez - besoin que d'un environnement de travail 64bit. + Aller à la prochaine section "chaines d'outils MinGW 32bit (i686)", ou + bien aller directement à la section "ImageMagick" si vous n'avez besoin + que d'un environnement de travail 64bit. ------------------------------------------------------- Chaînes d'outils MinGW 32bit (i686) - Sous le shell MSYS2, exécutez la commande suivante pour installer - outils basiques pour le développement 32bit : + Sous le shell MSYS2, exécutez la commande suivante pour installer outils + basiques pour le développement 32bit : - pacman -S mingw-w64-i686-toolchain + pacman -S mingw-w64-i686-toolchain bibliothèques de dépendance 32bit (i686) pour Tux Paint - You can install tools and libraries required for compiling Tux Paint - on MSYS2/MINGW using "pacman" except for SDL_Pango. + You can install tools and libraries required for compiling Tux Paint on + MSYS2/MINGW using "pacman" except for SDL_Pango. - "ntldd" est un petit outil qui examine les fichiers exécutables de - windows en vue de lister les fichiers DLL (.dll) qui leur sont - nécessaires. Le process de fabrication de Tux Paint pour fournir des - fichiers binaires s'en sert pour trouver les fichiers .dll requis. + "ntldd" est un petit outil qui examine les fichiers exécutables de windows + en vue de lister les fichiers DLL (.dll) qui leur sont nécessaires. Le + process de fabrication de Tux Paint pour fournir des fichiers binaires + s'en sert pour trouver les fichiers .dll requis. - FLTK est un ensemble d'outils multiplateforme utilisé par "Tux Paint - Config.". Vous pouvez ne pas l'installer si vous compilez seulement - "Tux Paint". + FLTK est un ensemble d'outils multiplateforme utilisé par "Tux Paint + Config.". Vous pouvez ne pas l'installer si vous compilez seulement "Tux + Paint". - $ pacman -S mingw-w64-i686-SDL_{image,mixer,ttf,gfx} - $ pacman -S mingw-w64-i686-librsvg - $ pacman -S mingw-w64-i686-fribidi - $ pacman -S mingw-w64-i686-libimagequant - $ pacman -S mingw-w64-i686-fltk - $ pacman -S mingw-w64-i686-ntldd-git + $ pacman -S mingw-w64-i686-SDL_{image,mixer,ttf,gfx} + $ pacman -S mingw-w64-i686-librsvg + $ pacman -S mingw-w64-i686-fribidi + $ pacman -S mingw-w64-i686-libimagequant + $ pacman -S mingw-w64-i686-fltk + $ pacman -S mingw-w64-i686-ntldd-git - Nota : Fermez l'interpréteur de commandes avant de passer à la - suite. + 💡 Nota : Fermez l'interpréteur de commandes avant de passer à la suite. Install SDL_Pango on the 32bit environment - SDL_Pango should be installed manually. + SDL_Pango should be installed manually. - Cette fois-ci, utilisez le shell MinGW "32bit". Ouvrez le shell - depuis le "Menu de Démarrage" -> "MSYS2 64bit" -> "MSYS2 MinGW - 32-bit" + Cette fois-ci, utilisez le shell MinGW "32bit". Ouvrez le shell depuis le + "Menu de Démarrage" -> "MSYS2 64bit" -> "MSYS2 MinGW 32-bit" SDL_Pango - Tout d'abord, vous devrez préparer l'archive source et un patch - qui est requis, dans le même répertoire. + Tout d'abord, vous devrez préparer l'archive source et un patch qui est + requis, dans le même répertoire. + * Télécharger fichier source de SDL_Pango-0.1.2 depuis La page SDL_Pango + sur Sourceforge.net. + * Télécharger un fichier patch depuis La page web de John Popplewell + traitant des "instructions pour la compilation de Tux Paint - + MinGW/MSYS". (Ceci ajoute une fonctionnalité supplémentaire (requise) + à SDL_Pango.) - * Télécharger fichier source de SDL_Pango-0.1.2 depuis La page - SDL_Pango sur Sourceforge.net. - * Télécharger un fichier patch depuis La page web de John - Popplewell traitant des "instructions pour la compilation de - Tux Paint - MinGW/MSYS". (Ceci ajoute une fonctionnalité - supplémentaire (requise) à SDL_Pango.) + Compiler et installer SDL_Pango comme suit. - Compiler et installer SDL_Pango comme suit. + $ tar zxvf SDL_Pango-0.1.2.tar.gz + $ cd SDL_Pango-0.1.2/ + $ patch -p0 < ../SDL_Pango-configure-extra-api.patch + $ ./configure --prefix=/mingw32 && make && make install - $ tar zxvf SDL_Pango-0.1.2.tar.gz - $ cd SDL_Pango-0.1.2/ - $ patch -p0 < ../SDL_Pango-configure-extra-api.patch - $ ./configure --prefix=/mingw32 && make && make install + ImageMagick - ------------------------------------------------------- + ImageMagick est un ensemble d'outils en ligne de commande pour créer, + éditer, composer ou convertir des images bitmap, et qui supporte un grand + nombre de formats d'image. Tux Paint utilise deux fonctions ("convert" et + "composite") pour générer des vignettes pour les images de démarrage et + des modèles durant le process de compilation. - ImageMagick + L'utilisation des binaires officiels tirés de "Versions binaires pour + Windows" est recommandée car les commandes installées avec "pacman" sur + MinGW/MSYS ne fonctionnent pas comme elles devraient ! - ImageMagick est un ensemble d'outils en ligne de commande pour - créer, éditer, composer ou convertir des images bitmap, et qui - supporte un grand nombre de formats d'image. Tux Paint utilise deux - fonctions ("convert" et "composite") pour générer des vignettes pour - les images de démarrage et des modèles durant le process de - compilation. + N'oubliez pas de cocher "Installer les utilitaires hérités (par ex. + convert)" pour l'installation, car le processus de compilation de Tux + Paint les utilise. - L'utilisation des binaires officiels tirés de "Versions binaires - pour Windows" est recommandée car les commandes installées avec - "pacman" sur MinGW/MSYS ne fonctionnent pas comme elles devraient ! + Ajoutez le chemin où ImageMagick est installé au début de votre variable + d'environnement "PATH". Par exemple : - N'oubliez pas de cocher "Installer les utilitaires hérités (par ex. - convert)" pour l'installation, car le processus de compilation de - Tux Paint les utilise. + $ export PATH=/c/Program\ Files/ImageMagick-7.0.10-Q16-HDRI:$PATH - Ajoutez le chemin où ImageMagick est installé au début de votre - variable d'environnement "PATH". Par exemple : + Vous pouvez rendre ceci permanent en ajoutant ce qui précède à votre + fichier de configuration du shell BASH, "~/.bash_profile". - $ export PATH=/c/Program\ Files/ImageMagick-7.0.10-Q16-HDRI:$PATH + Tux Paint - Vous pouvez rendre ceci permanent en ajoutant ce qui précède à votre - fichier de configuration du shell BASH, "~/.bash_profile". + Vous pouvez compiler des binaires 64bit en utilisant le shell MSYS2 64bit, + et des binaires 32bit en utilisant le shell MSYS2 32bit. - ------------------------------------------------------- + * Choisissez "MSYS2 64bit" -> "MSYS2 MinGW 64-bit" dans le "Menu de + Démarrage" pour ouvrir le shell 64bit. + * Choisissez "MSYS2 64bit" -> "MSYS2 MinGW 32-bit" dans le "Menu de + Démarrage" pour ouvrir le shell 32bit. - Tux Paint + Compilez Tux Paint avec la commande suivante : - Vous pouvez compiler des binaires 64bit en utilisant le shell MSYS2 - 64bit, et des binaires 32bit en utilisant le shell MSYS2 32bit. + $ make bdist-win32 - * Choisissez "MSYS2 64bit" -> "MSYS2 MinGW 64-bit" dans le "Menu - de Démarrage" pour ouvrir le shell 64bit. - * Choisissez "MSYS2 64bit" -> "MSYS2 MinGW 32-bit" dans le "Menu - de Démarrage" pour ouvrir le shell 32bit. + 💡 Nota : À ce stade, vous voudrez compiler "Tux Paint Config". Pour + Windows, il peut être ainsi inclus avec "Tux Paint", si vous faites une + version officielle (ou de test).La compilation ira chercher un répertoire + nommé "tuxpaint-config" (sans numéro de version, par ex voir + "tuxpaint-config-X.Y.Z"). Voir le fichier INSTALL.txt de "Tux Paint + Config" pour les détails. - Compilez Tux Paint avec la commande suivante : + Tous les fichiers nécessaires pour démarrer Tux Paint (et Tux Paint + Config) sont rassemblés dans le répertoire de la distribution binaire + "bdist", répertoire situé sous "win323. Vous pouvez les démarrer en + double-cliquant leurs fichiers exéctutables (.exe) dans le répertoire + "bdist". - $ make bdist-win32 + Building the Tux Paint Windows Installer - Nota : À ce stade, vous voudrez compiler "Tux Paint Config". Pour - Windows, il peut être ainsi inclus avec "Tux Paint", si vous faites - une version officielle (ou de test).La compilation ira chercher un - répertoire nommé "tuxpaint-config" (sans numéro de version, par ex - voir "tuxpaint-config-X.Y.Z"). Voir le fichier INSTALL.txt de "Tux - Paint Config" pour les détails. + Inno Setup est utilisé pour construire l'installeur exécutable de Tux + Paint. Vous devez donc l'installer en premier. - Tous les fichiers nécessaires pour démarrer Tux Paint (et Tux Paint - Config) sont rassemblés dans le répertoire de la distribution - binaire "bdist", répertoire situé sous "win323. Vous pouvez les - démarrer en double-cliquant leurs fichiers exéctutables (.exe) dans - le répertoire "bdist". + Officiellement Inno Setup prend en compte des traductions dans environ 20 + langues. Cependant, un des points majeurs de Tux Paint est qu'il supporte + beaucoup de langues. Aussi, le script de mise au point "tuxpaint.iss" qui + sert pour construire le programme d'installation est écrit en beaucoup + plus de langues, y compris des non-officielles qui sont disponibles sur + "Inno Setup Translations". Vous devez télécharger les fichiers de + traduction (.isl) qui sont requis et les mettre dans le répertoire + "Languages" sous le répertoire dans lequel Inno Setup est installé. - ------------------------------------------------------- + Before building an installer, edit the "tuxpaint.iss" file and enable one + of the lines starting with "#define BuildTarget=", depending on the + architecture of the installer you want to create. - Construire l'installateur de Tux Paint sous Windows : + Alors, vous pouvez facilement construire un installateur exécutable en + cliquant-droit sur l'icône "tuxpaint.iss" du répertoires "win32" et + sélectionner "Compile" dans la liste. Cela prendra un certain temps, et + éventuellement vous obtiendrez un fichier + "tuxpaint-X.Y.Z-windows--installer.exe" dans le même répertoire. - Inno Setup est utilisé pour construire l'installeur exécutable de - Tux Paint. Vous devez donc l'installer en premier. + Running the Tux Paint Windows Installer - Officiellement Inno Setup prend en compte des traductions dans - environ 20 langues. Cependant, un des points majeurs de Tux Paint - est qu'il supporte beaucoup de langues. Aussi, le script de mise au - point "tuxpaint.iss" qui sert pour construire le programme - d'installation est écrit en beaucoup plus de langues, y compris des - non-officielles qui sont disponibles sur "Inno Setup Translations". - Vous devez télécharger les fichiers de traduction (.isl) qui sont - requis et les mettre dans le répertoire "Languages" sous le - répertoire dans lequel Inno Setup est installé. + Double-cliquez sur l'exécutable du programme d'installation de Tux Paint + (fichier .EXE) et suivez les instructions. - Before building an installer, edit the "tuxpaint.iss" file and - enable one of the lines starting with "#define BuildTarget=", - depending on the architecture of the installer you want to create. + First, you will be asked to read the license. (It is the GNU General + Public License (GPL), which is also available as "COPYING.txt".) - Alors, vous pouvez facilement construire un installateur exécutable - en cliquant-droit sur l'icône "tuxpaint.iss" du répertoires "win32" - et sélectionner "Compile" dans la liste. Cela prendra un certain - temps, et éventuellement vous obtiendrez un fichier - "tuxpaint-X.Y.Z-windows--installer.exe" dans le même - répertoire. + Il vous sera ensuite demandé si vous souhaitez installer des raccourcis à + Tux Paint dans votre menu Démarrer de Windows et sur votre bureau + Windows.(Les deux options sont définies par défaut.) - ------------------------------------------------------- + Puis, il vous sera demandé où vous souhaitez installer Tux Paint. La + valeur par défaut devrait convenir, tant qu'il y a de l'espace disponible. + Sinon, choisissez un autre emplacement. - Utiliser l'installateur de Tux Paint sous Windows : + À ce stade, vous pouvez cliquer sur «Installer» pour installer Tux Paint ! - Double-cliquez sur l'exécutable du programme d'installation de Tux - Paint (fichier .EXE) et suivez les instructions. + Changing the Settings Using the Shortcut - First, you will be asked to read the license. (It is the GNU General - Public License (GPL), which is also available as "COPYING.txt".) + Pour modifier les paramètres du programme, cliquez avec le bouton droit + sur le raccourci TuxPaint et sélectionnez «Propriétés» (en bas). - Il vous sera ensuite demandé si vous souhaitez installer des - raccourcis à Tux Paint dans votre menu Démarrer de Windows et sur - votre bureau Windows.(Les deux options sont définies par défaut.) + Assurez-vous que l'onglet "Raccourci" est sélectionné dans la fenêtre qui + apparaît et examinez le champ «Cible:». Vous devriez voir quelque chose + comme ceci : - Puis, il vous sera demandé où vous souhaitez installer Tux Paint. La - valeur par défaut devrait convenir, tant qu'il y a de l'espace - disponible. Sinon, choisissez un autre emplacement. + "C:\Program Files\TuxPaint\TuxPaint.exe" - À ce stade, vous pouvez cliquer sur «Installer» pour installer Tux - Paint ! + Vous pouvez maintenant ajouter des options de ligne de commande qui seront + activées lorsque vous double-cliquez sur l'icône. - ------------------------------------------------------- + Par exemple, pour faire fonctionner le jeu en mode plein écran, avec des + formes simples (pas d'option de rotation) et en français, ajoutez les + options (après 'TuxPaint.exe'), comme ceci : - Modification des paramètres à l'aide du raccourci : + "C:\Program Files\TuxPaint\TuxPaint.exe" -f -s --lang french - Pour modifier les paramètres du programme, cliquez avec le bouton - droit sur le raccourci TuxPaint et sélectionnez «Propriétés» (en - bas). + (Voir «README.txt» pour une liste complète des options de ligne de + commande disponibles.) - Assurez-vous que l'onglet "Raccourci" est sélectionné dans la - fenêtre qui apparaît et examinez le champ «Cible:». Vous devriez - voir quelque chose comme ceci : + Si vous faites une erreur ou que tout disparaît, utilisez [Ctrl] + [Z] + pour annuler ou appuyez simplement sur la touche [Esc] et la boîte se + fermera sans aucune modification (sauf si vous avez appuyé sur le bouton + "Appliquer" !). - "C:\Program Files\TuxPaint\TuxPaint.exe" + Quand vous avez fini, appuyez sur "OK". - Vous pouvez maintenant ajouter des options de ligne de commande qui - seront activées lorsque vous double-cliquez sur l'icône. + If Something Goes Wrong - Par exemple, pour faire fonctionner le jeu en mode plein écran, avec - des formes simples (pas d'option de rotation) et en français, - ajoutez les options (après 'TuxPaint.exe'), comme ceci : + Si, lorsque vous double-cliquez sur le raccourci pour lancer le jeu, rien + ne se passe, c'est probablement parce que certaines des options en lignes + de commande sont erronées. Ouvrez un explorateur comme avant et recherchez + un fichier appelé "stderr.txt" dans le dossier TuxPaint. - "C:\Program Files\TuxPaint\TuxPaint.exe" -f -s --lang french + Il contiendra une description de ce qui n'allait pas. Habituellement, ce + sera simplement dû à une casse de caractère incorrecte (majuscule 'Z' à la + place de 'z' minuscule) ou un '-' (tiret) manquant (en trop). - (Voir «README.txt» pour une liste complète des options de ligne de - commande disponibles.) +Linux/Unix - Si vous faites une erreur ou que tout disparaît, utilisez [Ctrl] + - [Z] pour annuler ou appuyez simplement sur la touche [Esc] et la - boîte se fermera sans aucune modification (sauf si vous avez appuyé - sur le bouton "Appliquer" !). + Compilation : - Quand vous avez fini, appuyez sur "OK". + 💡 Note: Tux Paint does not use autoconf/automake, so there is no + "./configure" script to run. Compiling should be straight-forward though, + assuming everything Tux Paint needs is installed. - ------------------------------------------------------- + Pour compiler le programme à partir des sources, lancez simplement la + commande suivante après une invite shell (par ex. "$") : - Si quelque chose ne va pas : + $ make - Si, lorsque vous double-cliquez sur le raccourci pour lancer le jeu, - rien ne se passe, c'est probablement parce que certaines des options - en lignes de commande sont erronées. Ouvrez un explorateur comme - avant et recherchez un fichier appelé "stderr.txt" dans le dossier - TuxPaint. + Désactivation du support SVG (donc des dépendances Cairo, libSVG, et + svg-cairo) - Il contiendra une description de ce qui n'allait pas. - Habituellement, ce sera simplement dû à une casse de caractère - incorrecte (majuscule 'Z' à la place de 'z' minuscule) ou un '-' - (tiret) manquant (en trop). + Pour désactiver le support de SVG (par ex. si votre système n'a pas de + bibliothèque Cairo, ou d'autres choses dont SVG est dépendant), vous + pouvez exécuter "make" avec "SVG_LIB= SVG_CFLAGS= NOSVGFLAG=NOSVG" : - ---------------------------------------------------------------------- + $ make SVG_LIB= SVG_CFLAGS= - Utilisateurs de Linux/Unix + Désactivation du support Pango (donc des dépendances Pango, Cairo, etc ...) - Compilation : + 📜 Avant la version 0.9.18, Tuxpaint utilisait la bibliothèque libSDL_ttf + pour gérer les fichiers utilisant les fontes True Type. Depuis la 09.18 + libSDL_Pango est utilisée, car il permet un meilleur support pour + l'internationalisation. Cependant, si vous voulez désactiver l'utilisation + de SDL_Pango, vous pouvez le faire en exécutant "make" avec + "SDL_PANGO_LIB=" : - Remarque :Tux Paint n'utilise pas autoconf/automake, dès lors il n'y - a pas de script "./configure" à lancer. La compilation devrait aller - cependant aller toute seule, en supposant que Tux Paint ait tout ce - dont il a besoin. + $ make SDL_PANGO_LIB= - Pour compiler le programme à partir des sources, lancez simplement - la commande suivante après une invite shell (par ex. "$") : + Disabling Sound at Compile-time - $ make + 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 SDL_mixer), vous pouvez + exécuter "make" avec "SDL_MIXER_LIB=" comme paramètre : - ------------------------------------------------------- + $ make SDL_MIXER_LIB= - Désactivation du support SVG (donc des dépendances Cairo, libSVG, et - svg-cairo) + Other options - Pour désactiver le support de SVG (par ex. si votre système n'a pas - de bibliothèque Cairo, ou d'autres choses dont SVG est dépendant), - vous pouvez exécuter "make" avec "SVG_LIB= SVG_CFLAGS= - NOSVGFLAG=NOSVG" : + Diverses autres options (par exemple, les dossiers d'installation) peuvent + être remplacées; voir dans "Makefile" pour plus de détails. - $ make SVG_LIB= SVG_CFLAGS= + If you get errors - ------------------------------------------------------- + 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 "-dev" ou "-devel" correspondants, sinon vous ne pourrez pas + compiler Tux Paint (et d'autres programmes) provenant des sources ! - Désactivation du support Pango (donc des dépendances Pango, Cairo, etc ...) + Installng - Avant la version 0.9.18, Tuxpaint utilisait la bibliothèque - libSDL_ttf pour gérer les fichiers utilisant les fontes True Type. - Depuis la 09.18 libSDL_Pango est utilisée, car il permet un meilleur - support pour l'internationalisation. Cependant, si vous voulez - désactiver l'utilisation de SDL_Pango, vous pouvez le faire en - exécutant "make" avec "SDL_PANGO_LIB=" : + En supposant qu'aucune erreur fatale ne se soit produite, vous pouvez + maintenant installer le programme afin qu'il puisse être exécuté par les + utilisateurs du système. Par défaut, cela doit être effectué par + l'utilisateur "root" ("superutilisateur"). Passer à "root" en tapant la + commande : - $ make SDL_PANGO_LIB= + $ su - ------------------------------------------------------- + Entrez le mot de passe de "root" à l'invite. Vous devriez maintenant être + "root" (avec une invite comme "#"). Pour installer le programme et ses + fichiers de données, tapez : - Désactiver le son lors de la compilation : + # make install - 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 SDL_mixer), - vous pouvez exécuter "make" avec "SDL_MIXER_LIB=" comme paramètre : + Pour finir, vous pouvez revenir sur votre compte utilisateur en sortant du + compte superutilisateur : - $ make SDL_MIXER_LIB= + # exit - ------------------------------------------------------- + Autre manière : vous faites simplement utilisation de la commande "sudo" + (par ex. sur Ubuntu) : - Autres options : + $ sudo make install - Diverses autres options (par exemple, les dossiers d'installation) - peuvent être remplacées; voir dans "Makefile" pour plus de détails. + 💡 Note: By default, "tuxpaint", the executable program, is placed in + "/usr/local/bin/". The data files (images, sounds, etc.) are placed in + "/usr/local/share/tuxpaint/". - ------------------------------------------------------- + Changer où vont les fichiers - Si vous obtenez des erreurs : + Vous pouvez changer où iront les fichiers en définissant des variables + pour "Makefile" sur la ligne de commande. "DESTDIR" est utilisé pour + indiquer la sortie des résultats de la compilation. "PREFIX" est la base + où tous les autres fichiers iront et est définie par défaut comme + "/usr/local". - 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 "-dev" ou "-devel" - correspondants, sinon vous ne pourrez pas compiler Tux Paint (et - d'autres programmes) provenant des sources ! + Les autres variables sont : - ------------------------------------------------------- + BIN_PREFIX + Où le binaire "tuxpaint" sera installé. (Par défaut + "$(PREFIX)/bin", par ex. "/usr/local/bin") - Installation : + DATA_PREFIX + Où les fichiers de données (sons, graphiques, pinceaux, tampons, + fontes) iront, et où Tux Paint ira les chercher pour tourner + (Réglé à "$(PREFIX)/share/tuxpaint") - En supposant qu'aucune erreur fatale ne se soit produite, vous - pouvez maintenant installer le programme afin qu'il puisse être - exécuté par les utilisateurs du système. Par défaut, cela doit être - effectué par l'utilisateur "root" ("superutilisateur"). Passer à - "root" en tapant la commande : + DOC_PREFIX + Où sera mise la documentation (les répertoires "docs". 'Réglé à + "$(PREFIX)/share/doc/tuxpaint") - $ su + MAN_PREFIX + Où ira la page de manuel de Tuxpaint (Réglé à + "$(PREFIX)/share/man") - Entrez le mot de passe de "root" à l'invite. Vous devriez maintenant - être "root" (avec une invite comme "#"). Pour installer le programme - et ses fichiers de données, tapez : + ICON_PREFIX — $(PREFIX)/share/pixmaps - # make install + X11_ICON_PREFIX — $(PREFIX)/X11R6/include/X11/pixmaps - Pour finir, vous pouvez revenir sur votre compte utilisateur en - sortant du compte superutilisateur : + GNOME_PREFIX — $(PREFIX)/share/gnome/apps/Graphics - # exit + KDE_PREFIX — $(PREFIX)/share/applnk/Graphics + Où iront les icônes et les lanceurs (pour GNOME et KDE) - Autre manière : vous faites simplement utilisation de la commande - "sudo" (par ex. sur Ubuntu) : + LOCALE_PREFIX + Où iront les fichiers de traduction, et où Tux Paint ira les + chercher. (Réglé à "$(PREFIX)/share/locale/") (la destination + finale de la traduction sera dans le répertoire de la locale (par + ex "es" pour l'espagnol, dans le sous-répertoire "LC_MESSAGES"). - $ sudo make install + 💡 Note: This list is out of date. See "Makefile" and "Makefile-i18n" for a + complete list. - Remarque :Par défaut, "tuxpaint, le programme exécutable, est placé - en "/usr/local/bin/". Les données (images, sons, etc ...) sont dans - "/usr/local/share/tuxpaint/". +macOS - Changer où vont les fichiers + janvier 20, 2022 Mark Kim - Vous pouvez changer où iront les fichiers en définissant des - variables pour "Makefile" sur la ligne de commande. "DESTDIR" est - utilisé pour indiquer la sortie des résultats de la compilation. - "PREFIX" est la base où tous les autres fichiers iront et est - définie par défaut comme "/usr/local". + Tux Paint 0.9.22, et avant, devrait être construit avec Xcode IDE. À + partir de la version 0.9.23, cependant, Tux Paint pour macOS est construit + comme si c'était une application Linux. - Les autres variables sont : + Prérequis - BIN_PREFIX - Où le binaire "tuxpaint" sera installé. (Par défaut - "$(PREFIX)/bin", par ex. "/usr/local/bin") + Bien Tux Paint puisse être construit sans Xcode IDE, ce dernier est + toujours nécessaire. Téléchargez le = partir de l' the App Store, et + lancez le une fois pour accepter ses accords de licence. Vous pouvez aussi + installer les outils de ligne de commande de Xcode en tapant la commande : - DATA_PREFIX - Où les fichiers de données (sons, graphiques, pinceaux, - tampons, fontes) iront, et où Tux Paint ira les chercher - pour tourner (Réglé à "$(PREFIX)/share/tuxpaint") + xcode-select --install - DOC_PREFIX - Où sera mise la documentation (les répertoires "docs". - 'Réglé à "$(PREFIX)/share/doc/tuxpaint") + Construire Tux Paint nécessite plusieurs bibliothèques. Nous les + installons à partir de MacPorts quand c'est possible, sinon à partir du + code source. Installez MacPorts avec le chemin par défaut /opt/local + suivant les instructions données sur leur site : https://www.macports.org/ + * ImageMagick + * cairo + * fribidi + * lbzip2 + * libimagequant^* + * libpaper + * libpng + * librsvg + * libsdl + * libsdl_image + * libsdl_mixer + * libsdl_pango + * libsdl_ttf + * libsdl_gfx + * pkgconfig + * zlib + ... mais vous devriez installer tout paquet requis par la dernière version + de Tux Paint. - MAN_PREFIX - Où ira la page de manuel de Tuxpaint (Réglé à - "$(PREFIX)/share/man") + ^* Non disponible depuis MacPorts à ce moment, voir ci-dessous. - ICON_PREFIX — $(PREFIX)/share/pixmaps + libimagequant - X11_ICON_PREFIX — $(PREFIX)/X11R6/include/X11/pixmaps + libimagequant n'est pas disponible sur MacPorts à cette heure. Il peut + être installé sur /opt/local (comme pour MacPorts) pour la bibliothèque + devant être incluse dans TuxPaint.dmg. - GNOME_PREFIX — $(PREFIX)/share/gnome/apps/Graphics + $ sudo port install rust cargo + $ git clone https://github.com/ImageOptim/libimagequant.git + $ cd libimagequant/imagequant-sys + $ cargo build --release # Must use cargo from MacPorts + $ sudo make PREFIX=/opt/local install - KDE_PREFIX — $(PREFIX)/share/applnk/Graphics - Où iront les icônes et les lanceurs (pour GNOME et KDE) + ATTENTION :Posséder des outils Unix à côté de MacPorts et Xcode, tels que + Fink ou Brew, vous empêchera de créer un programme portable. V"rifiez que + Fink et Brew ne soient pas accessibles via votre environnement de travail. + + Comment construire - LOCALE_PREFIX - Où iront les fichiers de traduction, et où Tux Paint ira - les chercher. (Réglé à "$(PREFIX)/share/locale/") (la - destination finale de la traduction sera dans le - répertoire de la locale (par ex "es" pour l'espagnol, dans - le sous-répertoire "LC_MESSAGES"). + Tapez simplement : - Remarque : Cette liste est obsolète. Voir "Makefile" et - "Makefile-i18n" pour une liste complète. + % make + % make install + + ... to create the TuxPaint.app application bundle that can be run in-place + or copied to /Applications. To create the DMG file for distribution, use + 'make TuxPaint.dmg'. + + Additional steps may be required when building for the Apple Silicon. See + "Building for Apple Silicon" below. + + Problèmes connus + + * Un binaire macOS construit sur une version spécifique de macOS ne + fonctionnera qu'avec cette version, ou une plus récente. Pour + s'assurer que Tux Paint puisse tourner sur la plus vieille version de + macOS possible, construisez le sur la plus vieille version de macOS + disponible. Au moment où nous écrivons Tux Paint ne peut être + construit pour tourner sur macOS 10.7 ou plus récent. + + Voyez "Vieilles Versions de macOS" ci-dessous pour les meilleures + instructions pour obtenir, installer et construire Tux Paint sur des + vieilles versions de macOS. + + Alternatively, Tux Paint and all of its library dependencies may be + compiled with appropriate options to be runnable on older versions of + macOS. These options are already set on Tux Paint, so only its + dependencies (from MacPorts) need to be recompiled. See "Recompiling + MacPorts" below for the instructions. + + Vieilles versions de macOS + + Quelques vieilles versions de macOS peuvent être téléchargées sur la page + d'aide d'Apple : https://support.apple.com/en-us/HT211683 + + macOS for Intel CPU does allow dual booting of multiple versions of the + OS, but it's safer and easier to install the old macOS onto a flash drive. + Wherever you're installing it, the target drive's partitioniong scheme and + partition type must match what the old macOS expects, so use the Disk + Utility to partition and format the flash drive accordingly. + + Dual booting multiple versions of macOS for Apple Silicon has been so far + unsuccessful. Instead of installing an older version of macOS for Apple + Silicon to build Tux Paint to run on the old version of macOS for Apple + Silicon, use the instructions found in the "Recompiling MacPorts" section + to build Tux Paint to run on older versions of macOS for Apple Silicon. + + À ce moment, l'ancienne version de macOS disponible sur le site d'Apple + est la Yosemite 10.10, qui un partitionnement "GPT (GUID Partition Table)" + au lieu de MBR, et "Mac OS Extended (Journalisé)" comme type de partition + au lieu du nouveau type APFS. + + Au lancement de l'installateur, si vous avez un message disant que macOD + est trop vieux ou trop récent pour être installé, un installateur bootable + peut être créé en suivant les instructions données ici : + https://support.apple.com/en-mide/HT201372 + + Une fois l'ancienne version de macOS installée, vous pouvez trouver que le + Xcode du App Store est trop récent pour tourner sur la version du vieux + macOS. Des anciennes versions de Xcode peuvent être téléchargées sur le + site des développeurs d'Apple dans une zone accessible après + enregistrement gratuit : https://developer.apple.com/download/more/ + + La liste des versions de macOS et de la dernière version de Xcode + compatible avec celle-ci a été gentiment mise sur la page Wikipedia sur + Xcode : https://en.wikipedia.org/wiki/Xcode#Table de comparaison des + versions + + Comme Xcode a été installé manuellement, vous pouvez sauter l'étape + d'installation des outils de commande en terminal (ne pas exécuter + "xcode-select --install") mais alors vous compilez Tux Paint en utilisant + les mêmes étapes décrites auparavant dans ce document. - ---------------------------------------------------------------------- + Recompiling MacPorts - Utilisateurs de macOS + To recompile MacPorts to be usable on older versions of macOS, set the + following options in /opt/local/etc/macports/macports.conf: - janvier 20, 2022 Mark Kim + buildfromsource always + macosx_deployment_target 10.10 - Tux Paint 0.9.22, et avant, devrait être construit avec Xcode IDE. À - partir de la version 0.9.23, cependant, Tux Paint pour macOS est - construit comme si c'était une application Linux. + Then uninstall all MacPorts packages: - Prérequis + $ sudo port -fp uninstall installed - Bien Tux Paint puisse être construit sans Xcode IDE, ce dernier est - toujours nécessaire. Téléchargez le = partir de l' the App Store, et - lancez le une fois pour accepter ses accords de licence. Vous pouvez - aussi installer les outils de ligne de commande de Xcode en tapant - la commande : + Then reinstall all MacPorts packages needed by Tux Paint. Also rebuild + libimagequant using the updated Cargo package from MacPorts. + + As of this writing, all libraries Tux Paint requires from MacPorts can be + recompiled in this manner to run on macOS 10.10 Yosemite and later on + Intel CPUs, and macOS 11.0 Big Sur and later on Apple Silicon. + Unfortunately, although MacPorts has the option to enable the building of + universal libraries, several libraries Tux Paint require cannot be built + as universal libraries so they can only be built to run natively on the + hardware on which they were built. See "Building a Universal Binary" below + for instructions on how to build Tux Paint as a Universal Binary. - xcode-select --install + Building for Apple Silicon - Construire Tux Paint nécessite plusieurs bibliothèques. Nous les - installons à partir de MacPorts quand c'est possible, sinon à partir - du code source. Installez MacPorts avec le chemin par défaut - /opt/local suivant les instructions données sur leur site : - https://www.macports.org/ - * ImageMagick - * cairo - * fribidi - * lbzip2 - * libimagequant^* - * libpaper - * libpng - * librsvg - * libsdl - * libsdl_image - * libsdl_mixer - * libsdl_pango - * libsdl_ttf - * libsdl_gfx - * pkgconfig - * zlib - ... mais vous devriez installer tout paquet requis par la dernière - version de Tux Paint. + macOS for Applie Silicon requires all native Apple Silicon applications be + signed, even if it is signed "ad-hoc" (anonymously). Because of this, + compilers that produce native Apple Silicon applications sign all produced + binaries and libraries as a part of the compilation process.^* However, + the Tux Paint compilation process modifies the libraries to be modular + (using install_name_tool) so they can be added into the application + bundle, which has the unfortunate side effect of breaking the signature. + This can be addressed by signing the application bundle ad-hoc (example + below) or using your own Apple Developer Identity if you have one. The DMG + file, if needed, must be created after signing the App Bundle so the DMG + file is created with signed App Bundle: + + $ codesign -s - TuxPaint.app + $ make TuxPaint.dmg + + ^* For more information on the code signing requirements on the Apple + Silicon, see + https://developer.apple.com/documentation/macos-release-notes/macos-big-sur-11_0_1-universal-apps-release-notes#:~:text=New%20in%20macOS,pass%20through%20Gatekeeper. + + If you get an error that the application bundle is already signed, remove + it before signing:: + + $ codesign --remove-signature TuxPaint.app + + If you plan to combine the Apple Silicon bundle with the Intel CPU bundle + to produce the Universal bundle, the code signing must be done after they + are combined. See "Building a Universal Binary" below. + + Building a Universal Binary + + To build Tux Paint as a Universal Binary, compile Tux Paint for the Intel + CPU and the Apple Silicon separately first. Then rename the app bundle for + the Intel CPU to TuxPaint-x86_64.app, and the bundle for the Apple Silicon + to TuxPaint-arm64.app, copy the app bundle from the Intel machine to the + Apple Silicon machine, then use the provided build-universal.sh script to + combine the two application bundles as below. The produced bundle must be + signed (see "Building for Apple Silicon" above for more details). The DMG + file, if required, must be built after the signing: + + $ macos/build-universal.sh + $ codesign -s - TuxPaint.app + $ make TuxPaint.dmg + + Débogage + + ⚙ Le débogage — vers "STDOUT", avec Linux et Unix, vers un fichier + "stdout.txt"avec Windows, et vers le fichier "/tmp/tuxpaint.log" avec + macOS — peut être activé en définissant "DEBUG" (et, si un mode verbeux + est souhaité, "VERBOSE") # define dans "src/debug.h, et en (re)compilant + Tux Paint. - ^* Non disponible depuis MacPorts à ce moment, voir ci-dessous. - - libimagequant - - libimagequant n'est pas disponible sur MacPorts à cette heure. Il - peut être installé sur /opt/local (comme pour MacPorts) pour la - bibliothèque devant être incluse dans TuxPaint.dmg. - - $ sudo port install rust cargo - $ git clone https://github.com/ImageOptim/libimagequant.git - $ cd libimagequant/imagequant-sys - $ cargo build --release # Must use cargo from MacPorts - $ sudo make PREFIX=/opt/local install - - ATTENTION :Posséder des outils Unix à côté de MacPorts et Xcode, - tels que Fink ou Brew, vous empêchera de créer un programme - portable. V"rifiez que Fink et Brew ne soient pas accessibles via - votre environnement de travail. + Désinstallation de Tux Paint - ------------------------------------------------------- +Windows - Comment construire + Utilisation du désinstalleur - Tapez simplement : - - % make - % make install - - ... to create the TuxPaint.app application bundle that can be run - in-place or copied to /Applications. To create the DMG file for - distribution, use 'make TuxPaint.dmg'. + Si vous avez installé les raccourcis du menu Démarrer (par défaut), + accédez au dossier TuxPaint et sélectionnez "Désinstaller". Une boîte + s'affichera qui confirme que vous êtes sur le point de désinstaller Tux + Paint et, si vous en êtes certain et que vous souhaitez supprimer + définitivement Tux Paint, cliquez sur le bouton 'Désinstaller'. - Additional steps may be required when building for the Apple - Silicon. See "Building for Apple Silicon" below. - - ------------------------------------------------------- - - Problèmes connus - - * Un binaire macOS construit sur une version spécifique de macOS - ne fonctionnera qu'avec cette version, ou une plus récente. Pour - s'assurer que Tux Paint puisse tourner sur la plus vieille - version de macOS possible, construisez le sur la plus vieille - version de macOS disponible. Au moment où nous écrivons Tux - Paint ne peut être construit pour tourner sur macOS 10.7 ou plus - récent. - - Voyez "Vieilles Versions de macOS" ci-dessous pour les - meilleures instructions pour obtenir, installer et construire - Tux Paint sur des vieilles versions de macOS. - - Alternatively, Tux Paint and all of its library dependencies may - be compiled with appropriate options to be runnable on older - versions of macOS. These options are already set on Tux Paint, - so only its dependencies (from MacPorts) need to be recompiled. - See "Recompiling MacPorts" below for the instructions. - - ------------------------------------------------------- - - Vieilles versions de macOS - - Quelques vieilles versions de macOS peuvent être téléchargées sur la - page d'aide d'Apple : https://support.apple.com/en-us/HT211683 - - macOS for Intel CPU does allow dual booting of multiple versions of - the OS, but it's safer and easier to install the old macOS onto a - flash drive. Wherever you're installing it, the target drive's - partitioniong scheme and partition type must match what the old - macOS expects, so use the Disk Utility to partition and format the - flash drive accordingly. - - Dual booting multiple versions of macOS for Apple Silicon has been - so far unsuccessful. Instead of installing an older version of macOS - for Apple Silicon to build Tux Paint to run on the old version of - macOS for Apple Silicon, use the instructions found in the - "Recompiling MacPorts" section to build Tux Paint to run on older - versions of macOS for Apple Silicon. - - À ce moment, l'ancienne version de macOS disponible sur le site - d'Apple est la Yosemite 10.10, qui un partitionnement "GPT (GUID - Partition Table)" au lieu de MBR, et "Mac OS Extended (Journalisé)" - comme type de partition au lieu du nouveau type APFS. - - Au lancement de l'installateur, si vous avez un message disant que - macOD est trop vieux ou trop récent pour être installé, un - installateur bootable peut être créé en suivant les instructions - données ici : https://support.apple.com/en-mide/HT201372 - - Une fois l'ancienne version de macOS installée, vous pouvez trouver - que le Xcode du App Store est trop récent pour tourner sur la - version du vieux macOS. Des anciennes versions de Xcode peuvent être - téléchargées sur le site des développeurs d'Apple dans une zone - accessible après enregistrement gratuit : - https://developer.apple.com/download/more/ + Quand c'est fini, cliquez sur "Fermer". - La liste des versions de macOS et de la dernière version de Xcode - compatible avec celle-ci a été gentiment mise sur la page Wikipedia - sur Xcode : https://en.wikipedia.org/wiki/Xcode#Table de comparaison - des versions + En utilisant le panneau de configuration - Comme Xcode a été installé manuellement, vous pouvez sauter l'étape - d'installation des outils de commande en terminal (ne pas exécuter - "xcode-select --install") mais alors vous compilez Tux Paint en - utilisant les mêmes étapes décrites auparavant dans ce document. + Il est également possible d'utiliser l'entrée "TuxPaint (supprimer + uniquement)" dans la Section Ajout / Suppression de programmes du Panneau + de configuration. - Recompiling MacPorts +macOS - To recompile MacPorts to be usable on older versions of macOS, set - the following options in /opt/local/etc/macports/macports.conf: + Enlevez "TuxPaint.app" du dossier "Applications". Les fichiers de données + les fichiers de configuration, les tampons et les images sauvegardées + peuvent être trouvées dans "Bibliothèque/Support d'Application/Tux Paint" + (pour tous les utilisateurs) et "/Users/USERNAME/Library/Application + Support/TuxPaint" pour les utilisateurs individuels. - buildfromsource always - macosx_deployment_target 10.10 +Linux - Then uninstall all MacPorts packages: - - $ sudo port -fp uninstall installed - - Then reinstall all MacPorts packages needed by Tux Paint. Also - rebuild libimagequant using the updated Cargo package from MacPorts. - - As of this writing, all libraries Tux Paint requires from MacPorts - can be recompiled in this manner to run on macOS 10.10 Yosemite and - later on Intel CPUs, and macOS 11.0 Big Sur and later on Apple - Silicon. Unfortunately, although MacPorts has the option to enable - the building of universal libraries, several libraries Tux Paint - require cannot be built as universal libraries so they can only be - built to run natively on the hardware on which they were built. See - "Building a Universal Binary" below for instructions on how to build - Tux Paint as a Universal Binary. - - Building for Apple Silicon - - macOS for Applie Silicon requires all native Apple Silicon - applications be signed, even if it is signed "ad-hoc" (anonymously). - Because of this, compilers that produce native Apple Silicon - applications sign all produced binaries and libraries as a part of - the compilation process.^* However, the Tux Paint compilation - process modifies the libraries to be modular (using - install_name_tool) so they can be added into the application bundle, - which has the unfortunate side effect of breaking the signature. - This can be addressed by signing the application bundle ad-hoc - (example below) or using your own Apple Developer Identity if you - have one. The DMG file, if needed, must be created after signing the - App Bundle so the DMG file is created with signed App Bundle: - - $ codesign -s - TuxPaint.app - $ make TuxPaint.dmg - - ^* For more information on the code signing requirements on the - Apple Silicon, see - https://developer.apple.com/documentation/macos-release-notes/macos-big-sur-11_0_1-universal-apps-release-notes#:~:text=New%20in%20macOS,pass%20through%20Gatekeeper. - - If you get an error that the application bundle is already signed, - remove it before signing:: - - $ codesign --remove-signature TuxPaint.app - - If you plan to combine the Apple Silicon bundle with the Intel CPU - bundle to produce the Universal bundle, the code signing must be - done after they are combined. See "Building a Universal Binary" - below. - - Building a Universal Binary - - To build Tux Paint as a Universal Binary, compile Tux Paint for the - Intel CPU and the Apple Silicon separately first. Then rename the - app bundle for the Intel CPU to TuxPaint-x86_64.app, and the bundle - for the Apple Silicon to TuxPaint-arm64.app, copy the app bundle - from the Intel machine to the Apple Silicon machine, then use the - provided build-universal.sh script to combine the two application - bundles as below. The produced bundle must be signed (see "Building - for Apple Silicon" above for more details). The DMG file, if - required, must be built after the signing: - - $ macos/build-universal.sh - $ codesign -s - TuxPaint.app - $ make TuxPaint.dmg - - ---------------------------------------------------------------------- - -Débogage - - Le débogage — vers "STDOUT", avec Linux et Unix, vers un fichier - "stdout.txt"avec Windows, et vers le fichier "/tmp/tuxpaint.log" avec - macOS — peut être activé en définissant "DEBUG" (et, si un mode verbeux - est souhaité, "VERBOSE") # define dans "src/debug.h, et en (re)compilant - Tux Paint. - - ---------------------------------------------------------------------- - -Désinstallation de Tux Paint - - Windows - - Utilisation du désinstalleur - - Si vous avez installé les raccourcis du menu Démarrer (par défaut), - accédez au dossier TuxPaint et sélectionnez "Désinstaller". Une - boîte s'affichera qui confirme que vous êtes sur le point de - désinstaller Tux Paint et, si vous en êtes certain et que vous - souhaitez supprimer définitivement Tux Paint, cliquez sur le bouton - 'Désinstaller'. - - Quand c'est fini, cliquez sur "Fermer". - - En utilisant le panneau de configuration - - Il est également possible d'utiliser l'entrée "TuxPaint (supprimer - uniquement)" dans la Section Ajout / Suppression de programmes du - Panneau de configuration. - - ---------------------------------------------------------------------- - - macOS - - Enlevez "TuxPaint.app" du dossier "Applications". Les fichiers de - données les fichiers de configuration, les tampons et les images - sauvegardées peuvent être trouvées dans "Bibliothèque/Support - d'Application/Tux Paint" (pour tous les utilisateurs) et - "/Users/USERNAME/Library/Application Support/TuxPaint" pour les - utilisateurs individuels. - - ---------------------------------------------------------------------- - - Linux - - Dans le répertoire source de Tux Paint (où vous avez compilé Tux - Paint), vous pouvez utiliser une cible "make uninstall" pour - désinstaller Tux Paint. Par défaut, cela doit être fait par - l'utilisateur "root" ("superutilisateur"), mais si vous avez installé - Tux Paint à un autre endroit (par ex. en mettant "PREFIX=..." à "make" - et "make install", vous ne pourrez pas, et il faudra fournir les mêmes - réglages ici. (Voir + -
-

- Tux Paint
- version 0.9.28
- Documentation sur l'installation

+
+
+
+

+ Tux Paint
+ version 0.9.28
+ Documentation sur l'installation

-

- Copyright © 2002-2022 by divers contributeurs; see AUTHORS.txt.
- https://tuxpaint.org/ -

+

+ Copyright © 2002-2022 by divers contributeurs; see AUTHORS.txt.
+ https://tuxpaint.org/ +

-

- janvier 20, 2022

-
+

+ mars 31, 2022

+
+ -
+ + + + -
+ Table des matières
- - - + + + +
- Table des matières
+ +
+ - - - - - - +
+
+

+ + Exigences +

+
-
+
+
+

+ + Biliothèque Simple DirectMedia Layer (libSDL) +

+
-

- - Exigences -

-
- -

- - Biliothèque Simple DirectMedia Layer (libSDL) -

-

Tux Paint nécessite la bibliothèque de couches DirectMedia simple (libSDL), une bibliothèque de programmation multimédia Open Source disponible sous la Licence publique générale limitée GNU (LGPL).

Avec libSDL, Tux Paint dépend d'un certain nombre d'autres bibliothèques 'd'aide' SDL : SDL_Image (pour les fichiers graphiques), SDL_gfx (pour certaines fonctions graphiques, comme la rotation), SDL_TTF et (en option) SDL_Pango (pour la prise en charge des polices True Type) et, éventuellement, SDL_Mixer (pour les effets sonores).

-

Utilisateurs de Linux/Unix :

-
-

- Les bibliothèques SDL sont disponibles en tant que code source, ou en tant que paquets RPM ou Debian pour diverses distributions de Linux. Ils peuvent être téléchargés à partir de :

- +
+
Linux/Unix
+
+

+ Les bibliothèques SDL sont disponibles en tant que code source, ou en tant que paquets RPM ou Debian pour diverses distributions de Linux. Ils peuvent être téléchargés à partir de :

+ -

- Elles sont aussi parmi les paquets inclus dans votre distribution (par ex. sur le media d'installation, ou via la maintenance de vos logiciels comme la commande apt de Debian).

+

+ Elles sont aussi parmi les paquets inclus dans votre distribution (par ex. sur le media d'installation, ou via la maintenance de vos logiciels comme la commande apt de Debian).

-

- Remarque ;lors de l'installation à partir de packages, assurez-vous d'installer AUSSI les versions de développement des paquets (Par ex. installez les deux "SDL-1.2.4.rpm" et "SDL-1.2.4-devel.rpm".)

-
-
+

+ 💡 Note: When installing libraries from packages, be sure to ALSO install the development versions of the packages. (For example, install both "SDL-1.2.4.rpm" and "SDL-1.2.4-devel.rpm".)

+ + +
+ +
+
+

+ + Autres bibliothèques +

+
-

- - Autres bibliothèques -

-

Tux Paint profite également d'un certain nombre d'autres bibliothèques gratuites LGPL. Sous Linux, tout comme SDL, ils devraient être soit déjà installées, soit facilement disponibles avec votre distribution Linux.

-

libPNG

-
-

- Tux Paint utilise le format PNG (Portable Network Graphics) pour ses fichiers de données. SDL_image nécessitera l'installation de libPNG.

+
+
libPNG
+
+

+ Tux Paint utilise le format PNG (Portable Network Graphics) pour ses fichiers de données. SDL_image nécessitera l'installation de libPNG.

-

- http://www.libpng.org/pub/png/libpng.html -

-
+

+ http://www.libpng.org/pub/png/libpng.html +

+ -

gettext

-
-

- Tux Paint utilise les paramètres régionaux de votre système avec la bibliothèque "gettext" pour prendre en charge plusieurs langues (par exemple, l'espagnol). Vous aurez besoin d'installer la bibliothèque de gettext.

+
gettext
+
+

+ Tux Paint utilise les paramètres régionaux de votre système avec la bibliothèque "gettext" pour prendre en charge plusieurs langues (par exemple, l'espagnol). Vous aurez besoin d'installer la bibliothèque de gettext.

-

- http://www.gnu.org/software/gettext/ -

-
+

+ http://www.gnu.org/software/gettext/ +

+ -

libpaper (Linux/Unix uniquement)

-
-

- Depuis Tux Paint 0.9.17, Tux Paint peut déterminer le format de papier par défaut (par exemple, A4 ou Lettre), ou peut être invité à utiliser un format particulier, ceci grâce à libpaper.

+
libpaper (Linux/Unix uniquement)
+
+

+ Depuis Tux Paint 0.9.17, Tux Paint peut déterminer le format de papier par défaut (par exemple, A4 ou Lettre), ou peut être invité à utiliser un format particulier, ceci grâce à libpaper.

-

- https://github.com/naota/libpaper -

-
+

+ https://github.com/naota/libpaper +

+ -

FriBiDi

-
-

- Les outils "Texte" et "Étiquette" de Tux Paint supportent les langues bidirectionnelles, grâce à la bibliothèque "FriBidi".

+
FriBiDi
+
+

+ Les outils "Texte" et "Étiquette" de Tux Paint supportent les langues bidirectionnelles, grâce à la bibliothèque "FriBidi".

-

- http://fribidi.org/ -

-
+

+ http://fribidi.org/ +

+ -

Support des graphismes SVG

-
-

- À partir de Tux Paint 0.9.17, Tux Paint peut prendre en charge les images SVG (Scalable Vector Graphics) pour les tampons. Deux ensembles de bibliothèques sont pris en charge et le support SVG peut être complètement désactivé (via "make SVG_LIB:==")

+
Support des graphismes SVG
+
+

+ À partir de Tux Paint 0.9.17, Tux Paint peut prendre en charge les images SVG (Scalable Vector Graphics) pour les tampons. Deux ensembles de bibliothèques sont pris en charge et le support SVG peut être complètement désactivé (via "make SVG_LIB:==")

-
librsvg-2 & libCairo2 (nouvelles bibliothèques)
- +
+
librsvg-2 & libCairo2 (nouvelles bibliothèques)
+
+ +
-
Anciennes bibliothèques
- -
+
Anciennes bibliothèques
+
+ +
+ + -

Fonction d'exportation de GIF animés

-
-

- Pour prendre en compte l'exportation de GIF animés (diaporama), la bibliothèque "libimagequant" (issue du projet "pngquant" est nécessaire.

+
Fonction d'exportation de GIF animés
+
+

+ Pour prendre en compte l'exportation de GIF animés (diaporama), la bibliothèque "libimagequant" (issue du projet "pngquant" est nécessaire.

-

- https://github.com/ImageOptim/libimagequant -

-
+

+ https://github.com/ImageOptim/libimagequant +

+ -

Outils NetPBM (optionnel) ne sont plus utilisés par défaut

-
-

- Sous Linux et Unix, les anciennes versions de Tux Paint utilisaient les outils NetPBM comme aide à l'impression. (Un PNG est généré par TuxPaint et converti en PostScript en utilisant en ligne de commande les outils NetPBM pngtopnm et pnmtops.)

+
Outils NetPBM (optionnel) ne sont plus utilisés par défaut
+
+

+ 📜 Sous Linux et Unix, les anciennes versions de Tux Paint utilisaient les outils NetPBM comme aide à l'impression. (Un PNG est généré par TuxPaint et converti en PostScript en utilisant en ligne de commande les outils NetPBM pngtopnm et pnmtops.)

-

- http://netpbm.sourceforge.net/ -

-
-
- +

+ http://netpbm.sourceforge.net/ +

+ + +
+
-
+
+
+

+ + Compilation et installation +

+
-

- - Compilation et installation -

-

Tux Paint est publié sous la licence publique générale GNU (GPL) (voir "COPYING.txt" pour plus de détails), et donc le 'code source' du programme est disponible gratuitement.

-

- - Utilisateurs de Windows -

-

- - novembre 3, 2021 Shin-ichi TOYAMA dolphin6k@wmail.plala.or.jp <dolphin6k@wmail.plala.or.jp> - -

-
-

Réglages pour compilation

-
+
+
+

+ + Windows +

+ +

+ + novembre 3, 2021 Shin-ichi TOYAMA dolphin6k@wmail.plala.or.jp <dolphin6k@wmail.plala.or.jp> + +

+
+ +
+
+

Réglages pour compilation

+
+

Depuis février 2005 (à partir de Tux Paint 0.9.15), le "Makefile" inclut la prise en charge de la construction sur un système Windows à l'aide de MinGW/MSYS (https://sourceforge.net/projects/msys2/).

@@ -276,183 +339,194 @@

-
+

+ + Allez à la prochaine section "chaînes d'outils MinGW 64bit (x86_64) ", ou bien à la section "chaînes d'outils MinGW 32bit (i686)" si vous ne voulez qu'un environnement de travail 32bit. +

-

- - Allez à la prochaine section "chaînes d'outils MinGW 64bit (x86_64) ", ou bien à la section "chaînes d'outils MinGW 32bit (i686)" si vous ne voulez qu'un environnement de travail 32bit. -

- -
-

- - Chaînes d'outils MinGW 64bit (x86_64) -

- -
-

- Sous le shell MSYS2, exécutez la commande suivante pour installer outils basiques pour le développement 64bit :

- - pacman -S mingw-w64-x86_64-toolchain - -
-

- -
- -

- bibliothèques de dépendance 64bit (x86_64) pour Tux Paint

- -
-

- You can install tools and libraries required for compiling Tux Paint on MSYS2/MINGW using "pacman" except for SDL_Pango.

-

- "ntldd" est un petit outil qui examine les fichiers exécutables de windows en vue de lister les fichiers DLL (.dll) qui leur sont nécessaires. Le process de fabrication de Tux Paint pour fournir des fichiers binaires s'en sert pour trouver les fichiers .dll requis.

-

- FLTK est un ensemble d'outils multiplateforme utilisé par "Tux Paint Config.". Vous pouvez ne pas l'installer si vous compilez seulement "Tux Paint".

-

-

- - $ pacman -S mingw-w64-x86_64-SDL_{image,mixer,ttf,gfx}
- $ pacman -S mingw-w64-x86_64-librsvg
- $ pacman -S mingw-w64-x86_64-fribidi
- $ pacman -S mingw-w64-x86_64-libimagequant
- $ pacman -S mingw-w64-x86_64-fltk
- $ pacman -S mingw-w64-x86_64-ntldd-git - -
-

-

- Nota : Fermez l'interpréteur de commandes avant de passer à la suite.

- -
- -

- Install SDL_Pango on the 64bit environment

- -
-

- SDL_Pango should be installed manually.

-

- Cette fois-ci, utilisez le shell MinGW "64bit". Ouvrez le shell depuis le "Menu de Démarrage" -> "MSYS2 64bit" -> "MSYS2 MinGW 64-bit"

- -
SDL_Pango
- -
- -

- Tout d'abord, vous devrez préparer l'archive source et un patch qui est requis, dans le même répertoire.

- -

- Compiler et installer SDL_Pango comme suit.

- - $ tar zxvf SDL_Pango-0.1.2.tar.gz
- $ cd SDL_Pango-0.1.2/
- $ patch -p0 < ../SDL_Pango-configure-extra-api.patch
- $ ./configure --prefix=/mingw64 && make && make install - -
-

-
- -
- -

- - Aller à la prochaine section "chaines d'outils MinGW 32bit (i686)", ou bien aller directement à la section "ImageMagick" si vous n'avez besoin que d'un environnement de travail 64bit. -

-

- - Chaînes d'outils MinGW 32bit (i686) -

- -
-

- Sous le shell MSYS2, exécutez la commande suivante pour installer outils basiques pour le développement 32bit :

- - pacman -S mingw-w64-i686-toolchain - -
-

- -
- -

- bibliothèques de dépendance 32bit (i686) pour Tux Paint

- -
-

- You can install tools and libraries required for compiling Tux Paint on MSYS2/MINGW using "pacman" except for SDL_Pango.

-

- "ntldd" est un petit outil qui examine les fichiers exécutables de windows en vue de lister les fichiers DLL (.dll) qui leur sont nécessaires. Le process de fabrication de Tux Paint pour fournir des fichiers binaires s'en sert pour trouver les fichiers .dll requis.

-

- FLTK est un ensemble d'outils multiplateforme utilisé par "Tux Paint Config.". Vous pouvez ne pas l'installer si vous compilez seulement "Tux Paint".

-

-

- - $ pacman -S mingw-w64-i686-SDL_{image,mixer,ttf,gfx}
- $ pacman -S mingw-w64-i686-librsvg
- $ pacman -S mingw-w64-i686-fribidi
- $ pacman -S mingw-w64-i686-libimagequant
- $ pacman -S mingw-w64-i686-fltk
- $ pacman -S mingw-w64-i686-ntldd-git - -
-

-

- Nota : Fermez l'interpréteur de commandes avant de passer à la suite.

- -
- -

- Install SDL_Pango on the 32bit environment

- -
-

- SDL_Pango should be installed manually.

-

- Cette fois-ci, utilisez le shell MinGW "32bit". Ouvrez le shell depuis le "Menu de Démarrage" -> "MSYS2 64bit" -> "MSYS2 MinGW 32-bit"

- -
SDL_Pango
- -
+
+
+

+ + Chaînes d'outils MinGW 64bit (x86_64) +

+

- Tout d'abord, vous devrez préparer l'archive source et un patch qui est requis, dans le même répertoire.

- -

- Compiler et installer SDL_Pango comme suit.

+ Sous le shell MSYS2, exécutez la commande suivante pour installer outils basiques pour le développement 64bit :
- $ tar zxvf SDL_Pango-0.1.2.tar.gz
- $ cd SDL_Pango-0.1.2/
- $ patch -p0 < ../SDL_Pango-configure-extra-api.patch
- $ ./configure --prefix=/mingw32 && make && make install + pacman -S mingw-w64-x86_64-toolchain

-
+
-
+
+
+

+ bibliothèques de dépendance 64bit (x86_64) pour Tux Paint

+
- -
+

+ You can install tools and libraries required for compiling Tux Paint on MSYS2/MINGW using "pacman" except for SDL_Pango.

+

+ "ntldd" est un petit outil qui examine les fichiers exécutables de windows en vue de lister les fichiers DLL (.dll) qui leur sont nécessaires. Le process de fabrication de Tux Paint pour fournir des fichiers binaires s'en sert pour trouver les fichiers .dll requis.

+

+ FLTK est un ensemble d'outils multiplateforme utilisé par "Tux Paint Config.". Vous pouvez ne pas l'installer si vous compilez seulement "Tux Paint".

+

+

+ + $ pacman -S mingw-w64-x86_64-SDL_{image,mixer,ttf,gfx}
+ $ pacman -S mingw-w64-x86_64-librsvg
+ $ pacman -S mingw-w64-x86_64-fribidi
+ $ pacman -S mingw-w64-x86_64-libimagequant
+ $ pacman -S mingw-w64-x86_64-fltk
+ $ pacman -S mingw-w64-x86_64-ntldd-git + +
+

+

+ 💡 Nota : Fermez l'interpréteur de commandes avant de passer à la suite.

+
-

- ImageMagick -

+
+
+

+ Install SDL_Pango on the 64bit environment

+
+ +

+ SDL_Pango should be installed manually.

+

+ Cette fois-ci, utilisez le shell MinGW "64bit". Ouvrez le shell depuis le "Menu de Démarrage" -> "MSYS2 64bit" -> "MSYS2 MinGW 64-bit"

+ +
+
+
SDL_Pango
+
+ +

+ Tout d'abord, vous devrez préparer l'archive source et un patch qui est requis, dans le même répertoire.

+

+

+ Compiler et installer SDL_Pango comme suit.

+ + $ tar zxvf SDL_Pango-0.1.2.tar.gz
+ $ cd SDL_Pango-0.1.2/
+ $ patch -p0 < ../SDL_Pango-configure-extra-api.patch
+ $ ./configure --prefix=/mingw64 && make && make install + +
+

+
+ +

+ + Aller à la prochaine section "chaines d'outils MinGW 32bit (i686)", ou bien aller directement à la section "ImageMagick" si vous n'avez besoin que d'un environnement de travail 64bit. +

+ +
+ +
+
+
+

+ + Chaînes d'outils MinGW 32bit (i686) +

+
+ +

+ Sous le shell MSYS2, exécutez la commande suivante pour installer outils basiques pour le développement 32bit :

+ + pacman -S mingw-w64-i686-toolchain + +
+

+
+ +
+
+

+ bibliothèques de dépendance 32bit (i686) pour Tux Paint

+
+ +

+ You can install tools and libraries required for compiling Tux Paint on MSYS2/MINGW using "pacman" except for SDL_Pango.

+

+ "ntldd" est un petit outil qui examine les fichiers exécutables de windows en vue de lister les fichiers DLL (.dll) qui leur sont nécessaires. Le process de fabrication de Tux Paint pour fournir des fichiers binaires s'en sert pour trouver les fichiers .dll requis.

+

+ FLTK est un ensemble d'outils multiplateforme utilisé par "Tux Paint Config.". Vous pouvez ne pas l'installer si vous compilez seulement "Tux Paint".

+

+

+ + $ pacman -S mingw-w64-i686-SDL_{image,mixer,ttf,gfx}
+ $ pacman -S mingw-w64-i686-librsvg
+ $ pacman -S mingw-w64-i686-fribidi
+ $ pacman -S mingw-w64-i686-libimagequant
+ $ pacman -S mingw-w64-i686-fltk
+ $ pacman -S mingw-w64-i686-ntldd-git + +
+

+

+ 💡 Nota : Fermez l'interpréteur de commandes avant de passer à la suite.

+
+ +
+
+

+ Install SDL_Pango on the 32bit environment

+
+ +

+ SDL_Pango should be installed manually.

+

+ Cette fois-ci, utilisez le shell MinGW "32bit". Ouvrez le shell depuis le "Menu de Démarrage" -> "MSYS2 64bit" -> "MSYS2 MinGW 32-bit"

+ +
+
+
SDL_Pango
+
+ +

+ Tout d'abord, vous devrez préparer l'archive source et un patch qui est requis, dans le même répertoire.

+

+

+ Compiler et installer SDL_Pango comme suit.

+ + $ tar zxvf SDL_Pango-0.1.2.tar.gz
+ $ cd SDL_Pango-0.1.2/
+ $ patch -p0 < ../SDL_Pango-configure-extra-api.patch
+ $ ./configure --prefix=/mingw32 && make && make install + +
+

+
+ + +
+ +
+ +
+
+

+ ImageMagick +

+
-

ImageMagick est un ensemble d'outils en ligne de commande pour créer, éditer, composer ou convertir des images bitmap, et qui supporte un grand nombre de formats d'image. Tux Paint utilise deux fonctions ("convert" et "composite") pour générer des vignettes pour les images de démarrage et des modèles durant le process de compilation.

@@ -468,13 +542,13 @@

Vous pouvez rendre ceci permanent en ajoutant ce qui précède à votre fichier de configuration du shell BASH, "~/.bash_profile".

-
+
-
+
+
+

Tux Paint

+
-

Tux Paint

- -

Vous pouvez compiler des binaires 64bit en utilisant le shell MSYS2 64bit, et des binaires 32bit en utilisant le shell MSYS2 32bit.

    @@ -490,16 +564,17 @@

-

- Nota : À ce stade, vous voudrez compiler "Tux Paint Config". Pour Windows, il peut être ainsi inclus avec "Tux Paint", si vous faites une version officielle (ou de test).La compilation ira chercher un répertoire nommé "tuxpaint-config" (sans numéro de version, par ex voir "tuxpaint-config-X.Y.Z"). Voir le fichier INSTALL.txt de "Tux Paint Config" pour les détails.

+

+ 💡 Nota : À ce stade, vous voudrez compiler "Tux Paint Config". Pour Windows, il peut être ainsi inclus avec "Tux Paint", si vous faites une version officielle (ou de test).La compilation ira chercher un répertoire nommé "tuxpaint-config" (sans numéro de version, par ex voir "tuxpaint-config-X.Y.Z"). Voir le fichier INSTALL.txt de "Tux Paint Config" pour les détails.

Tous les fichiers nécessaires pour démarrer Tux Paint (et Tux Paint Config) sont rassemblés dans le répertoire de la distribution binaire "bdist", répertoire situé sous "win323. Vous pouvez les démarrer en double-cliquant leurs fichiers exéctutables (.exe) dans le répertoire "bdist".

- +
-
- -

Construire l'installateur de Tux Paint sous Windows :

-
+
+
+

+ Building the Tux Paint Windows Installer

+

Inno Setup est utilisé pour construire l'installeur exécutable de Tux Paint. Vous devez donc l'installer en premier.

@@ -509,14 +584,17 @@ Before building an installer, edit the "tuxpaint.iss" file and enable one of the lines starting with "#define BuildTarget=", depending on the architecture of the installer you want to create.

Alors, vous pouvez facilement construire un installateur exécutable en cliquant-droit sur l'icône "tuxpaint.iss" du répertoires "win32" et sélectionner "Compile" dans la liste. Cela prendra un certain temps, et éventuellement vous obtiendrez un fichier "tuxpaint-X.Y.Z-windows-<arch>-installer.exe" dans le même répertoire.

-
+ -
+
+
+

+ Running the Tux Paint Windows Installer

+
-

Utiliser l'installateur de Tux Paint sous Windows :

-

- Double-cliquez sur l'exécutable du programme d'installation de Tux Paint (fichier .EXE) et suivez les instructions. + Double-cliquez sur l'exécutable du programme d'installation de Tux Paint (fichier .EXE) et suivez les instructions.

+

First, you will be asked to read the license. (It is the GNU General Public License (GPL), which is also available as "COPYING.txt".)

@@ -528,12 +606,14 @@

À ce stade, vous pouvez cliquer sur «Installer» pour installer Tux Paint !

-
+
-
+
+
+

+ Changing the Settings Using the Shortcut

+
-

Modification des paramètres à l'aide du raccourci :

-

Pour modifier les paramètres du programme, cliquez avec le bouton droit sur le raccourci TuxPaint et sélectionnez «Propriétés» (en bas).

@@ -566,31 +646,38 @@

Quand vous avez fini, appuyez sur "OK".

-
+
-
+
+
+

+ If Something Goes Wrong

+
-

Si quelque chose ne va pas :

-

Si, lorsque vous double-cliquez sur le raccourci pour lancer le jeu, rien ne se passe, c'est probablement parce que certaines des options en lignes de commande sont erronées. Ouvrez un explorateur comme avant et recherchez un fichier appelé "stderr.txt" dans le dossier TuxPaint.

Il contiendra une description de ce qui n'allait pas. Habituellement, ce sera simplement dû à une casse de caractère incorrecte (majuscule 'Z' à la place de 'z' minuscule) ou un '-' (tiret) manquant (en trop).

-
- +
+ -
+
+
+

+ + Linux/Unix +

+
-

- - Utilisateurs de Linux/Unix -

-
-

Compilation :

-
-

- Remarque :Tux Paint n'utilise pas autoconf/automake, dès lors il n'y a pas de script "./configure" à lancer. La compilation devrait aller cependant aller toute seule, en supposant que Tux Paint ait tout ce dont il a besoin.

+
+
+

+ Compilation :

+
+ +

+ 💡 Note: Tux Paint does not use autoconf/automake, so there is no "./configure" script to run. Compiling should be straight-forward though, assuming everything Tux Paint needs is installed.

Pour compiler le programme à partir des sources, lancez simplement la commande suivante après une invite shell (par ex. "$") :

@@ -600,13 +687,14 @@ $ make
-
+
-
+
+
+

+ Désactivation du support SVG (donc des dépendances Cairo, libSVG, et svg-cairo)

+
-

- Désactivation du support SVG (donc des dépendances Cairo, libSVG, et svg-cairo)

-

Pour désactiver le support de SVG (par ex. si votre système n'a pas de bibliothèque Cairo, ou d'autres choses dont SVG est dépendant), vous pouvez exécuter "make" avec "SVG_LIB= SVG_CFLAGS= NOSVGFLAG=NOSVG" :

@@ -614,54 +702,64 @@ $ make SVG_LIB= SVG_CFLAGS=
-
+
-
+
+
+

+ Désactivation du support Pango (donc des dépendances Pango, Cairo, etc ...)

+
-

- Désactivation du support Pango (donc des dépendances Pango, Cairo, etc ...)

-
-

- Avant la version 0.9.18, Tuxpaint utilisait la bibliothèque libSDL_ttf pour gérer les fichiers utilisant les fontes True Type. Depuis la 09.18 libSDL_Pango est utilisée, car il permet un meilleur support pour l'internationalisation. Cependant, si vous voulez désactiver l'utilisation de SDL_Pango, vous pouvez le faire en exécutant "make" avec "SDL_PANGO_LIB=" :

+

+ 📜 Avant la version 0.9.18, Tuxpaint utilisait la bibliothèque libSDL_ttf pour gérer les fichiers utilisant les fontes True Type. Depuis la 09.18 libSDL_Pango est utilisée, car il permet un meilleur support pour l'internationalisation. Cependant, si vous voulez désactiver l'utilisation de SDL_Pango, vous pouvez le faire en exécutant "make" avec "SDL_PANGO_LIB=" :

$ make SDL_PANGO_LIB=
-
+
-
+
+
+

+ Disabling Sound at Compile-time

+
-

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 programme sans support sonore (et donc sans dépendance SDL_mixer), vous pouvez exécuter "make" avec "SDL_MIXER_LIB=" comme paramètre :

+

+ 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 SDL_mixer), vous pouvez exécuter "make" avec "SDL_MIXER_LIB=" comme paramètre :

$ make SDL_MIXER_LIB=
-
+
-
+
+
+

+ Other options

+
-

Autres options :

-

Diverses autres options (par exemple, les dossiers d'installation) peuvent être remplacées; voir dans "Makefile" pour plus de détails.

-
+
-
+
+
+

+ If you get errors

+
-

Si vous obtenez des erreurs :

-

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 "-dev" ou "-devel" correspondants, sinon vous ne pourrez pas compiler Tux Paint (et d'autres programmes) provenant des sources !

-
+
-
+
+
+

+ Installng

+
-

Installation :

-

En supposant qu'aucune erreur fatale ne se soit produite, vous pouvez maintenant installer le programme afin qu'il puisse être exécuté par les utilisateurs du système. Par défaut, cela doit être effectué par l'utilisateur "root" ("superutilisateur"). Passer à "root" en tapant la commande :

@@ -698,11 +796,15 @@
-

- Remarque :Par défaut, "tuxpaint, le programme exécutable, est placé en "/usr/local/bin/". Les données (images, sons, etc ...) sont dans "/usr/local/share/tuxpaint/".

+

+ 💡 Note: By default, "tuxpaint", the executable program, is placed in "/usr/local/bin/". The data files (images, sounds, etc.) are placed in "/usr/local/share/tuxpaint/".

+ +
+
+

+ Changer où vont les fichiers

+
-
Changer où vont les fichiers
-

Vous pouvez changer où iront les fichiers en définissant des variables pour "Makefile" sur la ligne de commande. "DESTDIR" est utilisé pour indiquer la sortie des résultats de la compilation. "PREFIX" est la base où tous les autres fichiers iront et est définie par défaut comme "/usr/local".

@@ -737,30 +839,34 @@ Où iront les fichiers de traduction, et où Tux Paint ira les chercher. (Réglé à "$(PREFIX)/share/locale/") (la destination finale de la traduction sera dans le répertoire de la locale (par ex "es" pour l'espagnol, dans le sous-répertoire "LC_MESSAGES"). -

- Remarque : Cette liste est obsolète. Voir "Makefile" et "Makefile-i18n" pour une liste complète.

-
- - +

+ 💡 Note: This list is out of date. See "Makefile" and "Makefile-i18n" for a complete list.

+
+
+ -
+
+
+

+ + macOS +

+

+ + janvier 20, 2022 Mark Kim <markuskimius@gmail.com> + +

+
-

- - Utilisateurs de macOS -

-

- - janvier 20, 2022 Mark Kim <markuskimius@gmail.com> - -

- -

Tux Paint 0.9.22, et avant, devrait être construit avec Xcode IDE. À partir de la version 0.9.23, cependant, Tux Paint pour macOS est construit comme si c'était une application Linux.

-

Prérequis

-
+
+
+

+ Prérequis

+
+

Bien Tux Paint puisse être construit sans Xcode IDE, ce dernier est toujours nécessaire. Téléchargez le = partir de l' the App Store, et lancez le une fois pour accepter ses accords de licence. Vous pouvez aussi installer les outils de ligne de commande de Xcode en tapant la commande :

@@ -792,8 +898,13 @@
* Non disponible depuis MacPorts à ce moment, voir ci-dessous.

-
libimagequant
-
+
+
+

+ libimagequant +

+
+

libimagequant n'est pas disponible sur MacPorts à cette heure. Il peut être installé sur /opt/local (comme pour MacPorts) pour la bibliothèque devant être incluse dans TuxPaint.dmg.

@@ -805,17 +916,18 @@

- -
+

ATTENTION :Posséder des outils Unix à côté de MacPorts et Xcode, tels que Fink ou Brew, vous empêchera de créer un programme portable. V"rifiez que Fink et Brew ne soient pas accessibles via votre environnement de travail.

-
+
-
+
+
+

+ Comment construire

+
-

Comment construire

-

Tapez simplement :

@@ -827,12 +939,14 @@

Additional steps may be required when building for the Apple Silicon. See "Building for Apple Silicon" below.

-
+
-
+
+
+

+ Problèmes connus

+
-

Problèmes connus

-
  • Un binaire macOS construit sur une version spécifique de macOS ne fonctionnera qu'avec cette version, ou une plus récente. Pour s'assurer que Tux Paint puisse tourner sur la plus vieille version de macOS possible, construisez le sur la plus vieille version de macOS disponible. Au moment où nous écrivons Tux Paint ne peut être construit pour tourner sur macOS 10.7 ou plus récent.
    @@ -841,12 +955,14 @@
    Alternatively, Tux Paint and all of its library dependencies may be compiled with appropriate options to be runnable on older versions of macOS. These options are already set on Tux Paint, so only its dependencies (from MacPorts) need to be recompiled. See "Recompiling MacPorts" below for the instructions.
-
+
-
+
+
+

+ Vieilles versions de macOS

+
-

Vieilles versions de macOS

-

Quelques vieilles versions de macOS peuvent être téléchargées sur la page d'aide d'Apple : https://support.apple.com/en-us/HT211683

@@ -870,11 +986,14 @@

Comme Xcode a été installé manuellement, vous pouvez sauter l'étape d'installation des outils de commande en terminal (ne pas exécuter "xcode-select --install") mais alors vous compilez Tux Paint en utilisant les mêmes étapes décrites auparavant dans ce document.

+
- +
+
+

+ Recompiling MacPorts

+
-

Recompiling MacPorts

-

To recompile MacPorts to be usable on older versions of macOS, set the following options in /opt/local/etc/macports/macports.conf:

@@ -897,18 +1016,21 @@

As of this writing, all libraries Tux Paint requires from MacPorts can be recompiled in this manner to run on macOS 10.10 Yosemite and later on Intel CPUs, and macOS 11.0 Big Sur and later on Apple Silicon. Unfortunately, although MacPorts has the option to enable the building of universal libraries, several libraries Tux Paint require cannot be built as universal libraries so they can only be built to run natively on the hardware on which they were built. See "Building a Universal Binary" below for instructions on how to build Tux Paint as a Universal Binary.

-
+
+ +
+
+

+ Building for Apple Silicon

+
-

Building for Apple Silicon

-

macOS for Applie Silicon requires all native Apple Silicon applications be signed, even if it is signed "ad-hoc" (anonymously). Because of this, compilers that produce native Apple Silicon applications sign all produced binaries and libraries as a part of the compilation process.* However, the Tux Paint compilation process modifies the libraries to be modular (using install_name_tool) so they can be added into the application bundle, which has the unfortunate side effect of breaking the signature. This can be addressed by signing the application bundle ad-hoc (example below) or using your own Apple Developer Identity if you have one. The DMG file, if needed, must be created after signing the App Bundle so the DMG file is created with signed App Bundle:

$ codesign -s - TuxPaint.app
$ make TuxPaint.dmg
- * For more information on the code signing requirements on the Apple Silicon, see https://developer.apple.com/documentation/macos-release-notes/macos-big-sur-11_0_1-universal-apps-release-notes#:~:text=New%20in%20macOS,pass%20through%20Gatekeeper. -

+ * For more information on the code signing requirements on the Apple Silicon, see https://developer.apple.com/documentation/macos-release-notes/macos-big-sur-11_0_1-universal-apps-release-notes#:~:text=New%20in%20macOS,pass%20through%20Gatekeeper.

If you get an error that the application bundle is already signed, remove it before signing::

$ codesign --remove-signature TuxPaint.app @@ -916,10 +1038,14 @@

If you plan to combine the Apple Silicon bundle with the Intel CPU bundle to produce the Universal bundle, the code signing must be done after they are combined. See "Building a Universal Binary" below.

-
+
+ +
+
+

+ Building a Universal Binary

+
-

Building a Universal Binary

-

To build Tux Paint as a Universal Binary, compile Tux Paint for the Intel CPU and the Apple Silicon separately first. Then rename the app bundle for the Intel CPU to TuxPaint-x86_64.app, and the bundle for the Apple Silicon to TuxPaint-arm64.app, copy the app bundle from the Intel machine to the Apple Silicon machine, then use the provided build-universal.sh script to combine the two application bundles as below. The produced bundle must be signed (see "Building for Apple Silicon" above for more details). The DMG file, if required, must be built after the signing:

@@ -929,71 +1055,87 @@

-
+
- + - + -
+
+
+

+ + Débogage +

+
-

- - Débogage -

-
- Le débogage — vers "STDOUT", avec Linux et Unix, vers un fichier "stdout.txt"avec Windows, et vers le fichier "/tmp/tuxpaint.log" avec macOS — peut être activé en définissant "DEBUG" (et, si un mode verbeux est souhaité, "VERBOSE") # define dans "src/debug.h, et en (re)compilant Tux Paint.
+

+ ⚙ Le débogage — vers "STDOUT", avec Linux et Unix, vers un fichier "stdout.txt"avec Windows, et vers le fichier "/tmp/tuxpaint.log" avec macOS — peut être activé en définissant "DEBUG" (et, si un mode verbeux est souhaité, "VERBOSE") # define dans "src/debug.h, et en (re)compilant Tux Paint.

+
-
+
+
+

+ + Désinstallation de Tux Paint +

+
+ +
+
+

+ + Windows +

+
+ +
+
+

+ Utilisation du désinstalleur

+
-

- - Désinstallation de Tux Paint

- -
-

- - Windows -

-
-

Utilisation du désinstalleur

-

Si vous avez installé les raccourcis du menu Démarrer (par défaut), accédez au dossier TuxPaint et sélectionnez "Désinstaller". Une boîte s'affichera qui confirme que vous êtes sur le point de désinstaller Tux Paint et, si vous en êtes certain et que vous souhaitez supprimer définitivement Tux Paint, cliquez sur le bouton 'Désinstaller'.

Quand c'est fini, cliquez sur "Fermer".

-
+
+ +
+
+

+ En utilisant le panneau de configuration

+
-

En utilisant le panneau de configuration

-

Il est également possible d'utiliser l'entrée "TuxPaint (supprimer uniquement)" dans la Section Ajout / Suppression de programmes du Panneau de configuration.

-
- +
+
-
+
+
+

+ + macOS +

+
-

- - macOS -

- -

Enlevez "TuxPaint.app" du dossier "Applications". Les fichiers de données les fichiers de configuration, les tampons et les images sauvegardées peuvent être trouvées dans "Bibliothèque/Support d'Application/Tux Paint" (pour tous les utilisateurs) et "/Users/USERNAME/Library/Application Support/TuxPaint" pour les utilisateurs individuels.

-
+
-
+
+
+

+ + Linux +

+
-

- - Linux -

-

Dans le répertoire source de Tux Paint (où vous avez compilé Tux Paint), vous pouvez utiliser une cible "make uninstall" pour désinstaller Tux Paint. Par défaut, cela doit être fait par l'utilisateur "root" ("superutilisateur"), mais si vous avez installé Tux Paint à un autre endroit (par ex. en mettant "PREFIX=..." à "make" et "make install", vous ne pourrez pas, et il faudra fournir les mêmes réglages ici. (Voir - Tux Paint publícase baixo a Licenza Pública Xeral de GNU (GPL) (consulte - «COPYING.txt» para máis detalles) e, polo tanto, o «código fonte» do - programa está dispoñíbel libremente. + Compiling Set-Up - Usuarios de Windows + A partir de febreiro de 2005 (comezando con Tux Paint 0.9.15), o + «Makefile» inclúe compatibilidade para construír nun sistema Windows + usando MinGW/MSYS (https://sourceforge.net/projects/msys2/). - 3 de Novembro de 2021 Shin-ichi TOYAMA dolphin6k@wmail.plala.or.jp - + Many tools and libraries are required to build Tux Paint. The package + management system "pacman" helps you install them automatically solving + complicated dependencies. - Compiling Set-Up + Download the latest MSYS2 environment from + https://sourceforge.net/projects/msys2/files/Base/ and install it where + you'd like (the default is "C:\msys64") - A partir de febreiro de 2005 (comezando con Tux Paint 0.9.15), o - «Makefile» inclúe compatibilidade para construír nun sistema Windows - usando MinGW/MSYS (https://sourceforge.net/projects/msys2/). + Open the MSYS2 shell from the "Start Menu" -> "MSYS2 64bit" -> "MSYS2 + MSYS" and execute following command (press [Intro] or [Retorno] to accept + the defaults for all questions): - Many tools and libraries are required to build Tux Paint. The - package management system "pacman" helps you install them - automatically solving complicated dependencies. + pacman -Syu - Download the latest MSYS2 environment from - https://sourceforge.net/projects/msys2/files/Base/ and install it - where you'd like (the default is "C:\msys64") + This will update core system and the window will close automatically. + Repeat the steps above one more time to finish the remaining update + process. - Open the MSYS2 shell from the "Start Menu" -> "MSYS2 64bit" -> - "MSYS2 MSYS" and execute following command (press [Intro] or - [Retorno] to accept the defaults for all questions): + Within the MSYS2 shell, run the following command to install basic + development tools: - pacman -Syu + pacman -S base-devel msys2-devel git - This will update core system and the window will close - automatically. Repeat the steps above one more time to finish the - remaining update process. - - Within the MSYS2 shell, run the following command to install basic - development tools: - - pacman -S base-devel msys2-devel git - - Proceed to the next "MinGW 64bit (x86_64) toolchains" section, or skip - to the "MinGW 32bit (i686) toolchains" section if you need only a - 32bit build environment. + Proceed to the next "MinGW 64bit (x86_64) toolchains" section, or skip 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 - 64bit development tools: + Within the MSYS2 shell, run the following command to install basic 64bit + development tools: - pacman -S mingw-w64-x86_64-toolchain + pacman -S mingw-w64-x86_64-toolchain 64bit (x86_64) dependency libraries for Tux Paint - You can install tools and libraries required for compiling Tux Paint - on MSYS2/MINGW using "pacman" except for SDL_Pango. + You can install tools and libraries required for compiling Tux Paint on + MSYS2/MINGW using "pacman" except for SDL_Pango. - "ntldd" is a small tool which examine windows executable files to - list Dynamic Link Library (.dll) files they depends on. Tux Paint's - packaging process for binary distribution uses it to find required - .dll files. + "ntldd" is a small tool which examine windows executable files to list + Dynamic Link Library (.dll) files they depends on. Tux Paint's packaging + process for binary distribution uses it to find required .dll files. - FLTK is a cross-platform GUI toolkit used by "Tux Paint Config.". - You can skip installing it if you are only building "Tux Paint". + FLTK is a cross-platform GUI toolkit used by "Tux Paint Config.". You can + skip installing it if you are only building "Tux Paint". - $ pacman -S mingw-w64-x86_64-SDL_{image,mixer,ttf,gfx} - $ pacman -S mingw-w64-x86_64-librsvg - $ pacman -S mingw-w64-x86_64-fribidi - $ pacman -S mingw-w64-x86_64-libimagequant - $ pacman -S mingw-w64-x86_64-fltk - $ pacman -S mingw-w64-x86_64-ntldd-git + $ pacman -S mingw-w64-x86_64-SDL_{image,mixer,ttf,gfx} + $ pacman -S mingw-w64-x86_64-librsvg + $ pacman -S mingw-w64-x86_64-fribidi + $ pacman -S mingw-w64-x86_64-libimagequant + $ pacman -S mingw-w64-x86_64-fltk + $ pacman -S mingw-w64-x86_64-ntldd-git - Note: Close the shell before proceeding to the remaining process. + 💡 Note: Close the shell before proceeding to the remaining process. Install SDL_Pango on the 64bit environment - SDL_Pango should be installed manually. + SDL_Pango should be installed manually. - This time, use the MinGW "64bit" shell. Open the shell from the - "Start Menu" -> "MSYS2 64bit" -> "MSYS2 MinGW 64-bit" + This time, use the MinGW "64bit" shell. Open the shell from the "Start + Menu" -> "MSYS2 64bit" -> "MSYS2 MinGW 64-bit" SDL_Pango - At first, you have to prepare source tar-ball and a required patch - in the same directory. + At first, you have to prepare source tar-ball and a required patch in the + same directory. + * Download source tar-ball of SDL_Pango-0.1.2 from SDL_Pango's page on + Sourceforge.net. + * Download a patch file from John Popplewell's "Tux Paint - MinGW/MSYS + build instructions" webpage. (This adds some extra (required) + functionality to SDL_Pango.) - * Download source tar-ball of SDL_Pango-0.1.2 from SDL_Pango's - page on Sourceforge.net. - * Download a patch file from John Popplewell's "Tux Paint - - MinGW/MSYS build instructions" webpage. (This adds some extra - (required) functionality to SDL_Pango.) + Build and install SDL_Pango as follows. - Build and install SDL_Pango as follows. + $ tar zxvf SDL_Pango-0.1.2.tar.gz + $ cd SDL_Pango-0.1.2/ + $ patch -p0 < ../SDL_Pango-configure-extra-api.patch + $ ./configure --prefix=/mingw64 && make && make install - $ tar zxvf SDL_Pango-0.1.2.tar.gz - $ cd SDL_Pango-0.1.2/ - $ patch -p0 < ../SDL_Pango-configure-extra-api.patch - $ ./configure --prefix=/mingw64 && make && make install - - Proceed to the next "MinGW 32bit (i686) toolchains" section, or skip - to the "ImageMagick" section if you need only a 64bit build - environment. + Proceed to the next "MinGW 32bit (i686) toolchains" section, or skip 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 - 32bit development tools: + Within the MSYS2 shell, run the following command to install basic 32bit + development tools: - pacman -S mingw-w64-i686-toolchain + pacman -S mingw-w64-i686-toolchain 32bit (i686) dependency libraries for Tux Paint - You can install tools and libraries required for compiling Tux Paint - on MSYS2/MINGW using "pacman" except for SDL_Pango. + You can install tools and libraries required for compiling Tux Paint on + MSYS2/MINGW using "pacman" except for SDL_Pango. - "ntldd" is a small tool which examine windows executable files to - list Dynamic Link Library (.dll) files they depends on. Tux Paint's - packaging process for binary distribution uses it to find required - .dll files. + "ntldd" is a small tool which examine windows executable files to list + Dynamic Link Library (.dll) files they depends on. Tux Paint's packaging + process for binary distribution uses it to find required .dll files. - FLTK is a cross-platform GUI toolkit used by "Tux Paint Config.". - You can skip installing it if you are only building "Tux Paint". + FLTK is a cross-platform GUI toolkit used by "Tux Paint Config.". You can + skip installing it if you are only building "Tux Paint". - $ pacman -S mingw-w64-i686-SDL_{image,mixer,ttf,gfx} - $ pacman -S mingw-w64-i686-librsvg - $ pacman -S mingw-w64-i686-fribidi - $ pacman -S mingw-w64-i686-libimagequant - $ pacman -S mingw-w64-i686-fltk - $ pacman -S mingw-w64-i686-ntldd-git + $ pacman -S mingw-w64-i686-SDL_{image,mixer,ttf,gfx} + $ pacman -S mingw-w64-i686-librsvg + $ pacman -S mingw-w64-i686-fribidi + $ pacman -S mingw-w64-i686-libimagequant + $ pacman -S mingw-w64-i686-fltk + $ pacman -S mingw-w64-i686-ntldd-git - Note: Close the shell before proceeding to the remaining process. + 💡 Note: Close the shell before proceeding to the remaining process. Install SDL_Pango on the 32bit environment - SDL_Pango should be installed manually. + SDL_Pango should be installed manually. - This time, use the MinGW "32bit" shell. Open the shell from the - "Start Menu" -> "MSYS2 64bit" -> "MSYS2 MinGW 32-bit" + This time, use the MinGW "32bit" shell. Open the shell from the "Start + Menu" -> "MSYS2 64bit" -> "MSYS2 MinGW 32-bit" SDL_Pango - At first, you have to prepare source tar-ball and a required patch - in the same directory. + At first, you have to prepare source tar-ball and a required patch in the + same directory. + * Download source tar-ball of SDL_Pango-0.1.2 from SDL_Pango's page on + Sourceforge.net. + * Download a patch file from John Popplewell's "Tux Paint - MinGW/MSYS + build instructions" webpage. (This adds some extra (required) + functionality to SDL_Pango.) - * Download source tar-ball of SDL_Pango-0.1.2 from SDL_Pango's - page on Sourceforge.net. - * Download a patch file from John Popplewell's "Tux Paint - - MinGW/MSYS build instructions" webpage. (This adds some extra - (required) functionality to SDL_Pango.) + Build and install SDL_Pango as follows. - Build and install SDL_Pango as follows. + $ tar zxvf SDL_Pango-0.1.2.tar.gz + $ cd SDL_Pango-0.1.2/ + $ patch -p0 < ../SDL_Pango-configure-extra-api.patch + $ ./configure --prefix=/mingw32 && make && make install - $ tar zxvf SDL_Pango-0.1.2.tar.gz - $ cd SDL_Pango-0.1.2/ - $ patch -p0 < ../SDL_Pango-configure-extra-api.patch - $ ./configure --prefix=/mingw32 && make && make install + ImageMagick - ------------------------------------------------------- + ImageMagick is a compilation of command line tools to create, edit, + compose, or convert bitmap images supporting quite a large number of image + formats. Tux Paint uses two functions ("convert" and "composite") in it to + generate thumbnails for startar images and templates during the build + process. - ImageMagick + Using official binary release available from "Windows Binary Release" is + recommended, due to the commands installed with "pacman" on MinGW/MSYS not + working as expected! - ImageMagick is a compilation of command line tools to create, edit, - compose, or convert bitmap images supporting quite a large number of - image formats. Tux Paint uses two functions ("convert" and - "composite") in it to generate thumbnails for startar images and - templates during the build process. + Do not forget to enable "Install legacy utilities (e.g. convert)" while + installing it, because Tux Paint's build process uses them. - Using official binary release available from "Windows Binary - Release" is recommended, due to the commands installed with "pacman" - on MinGW/MSYS not working as expected! + Add the path to the directory in which ImageMagick is installed at the top + of your "PATH" environment variable. For example: - Do not forget to enable "Install legacy utilities (e.g. convert)" - while installing it, because Tux Paint's build process uses them. + $ export PATH=/c/Program\ Files/ImageMagick-7.0.10-Q16-HDRI:$PATH - Add the path to the directory in which ImageMagick is installed at - the top of your "PATH" environment variable. For example: + You can make this permanent by adding the above to your the BASH shell + configuration file, "~/.bash_profile". - $ export PATH=/c/Program\ Files/ImageMagick-7.0.10-Q16-HDRI:$PATH + Tux Paint - You can make this permanent by adding the above to your the BASH - shell configuration file, "~/.bash_profile". + You can compile 64bit binaries using MSYS2 64bit shell, and 32bit binaries + using MSYS2 32bit shell, respectively. - ------------------------------------------------------- + * Select "MSYS2 64bit" -> "MSYS2 MinGW 64-bit" from the "Start Menu" to + open the 64bit shell. + * Select "MSYS2 64bit" -> "MSYS2 MinGW 32-bit" from the "Start Menu" to + open the 32bit shell. - Tux Paint + Compile Tux Paint with the following command: - You can compile 64bit binaries using MSYS2 64bit shell, and 32bit - binaries using MSYS2 32bit shell, respectively. + $ make bdist-win32 - * Select "MSYS2 64bit" -> "MSYS2 MinGW 64-bit" from the "Start - Menu" to open the 64bit shell. - * Select "MSYS2 64bit" -> "MSYS2 MinGW 32-bit" from the "Start - Menu" to open the 32bit shell. + 💡 Note: At this point, you will want to build "Tux Paint Config." for + Windows, so it can be included along with "Tux Paint", if you're making an + official (or test) release. The build process will look for it in a + directory named "tuxpaint-config" (with no version number, e.g., + "tuxpaint-config-X.Y.Z"). See "Tux Paint Config."'s INSTALL.txt + documentation for details. - Compile Tux Paint with the following command: + All the files needed for starting Tux Paint (and Tux Paint Config.) are + collected in the directory for binary distribution "bdist" directory under + "win32". You can start them by double-clicking their executable (.exe) + files in the "bdist" directory. - $ make bdist-win32 + Building the Tux Paint Windows Installer - Note: At this point, you will want to build "Tux Paint Config." for - Windows, so it can be included along with "Tux Paint", if you're - making an official (or test) release. The build process will look - for it in a directory named "tuxpaint-config" (with no version - number, e.g., "tuxpaint-config-X.Y.Z"). See "Tux Paint Config."'s - INSTALL.txt documentation for details. + Inno Setup is used to build executable installer for Tux Paint. Therefore + you have to install it in the first place. - All the files needed for starting Tux Paint (and Tux Paint Config.) - are collected in the directory for binary distribution "bdist" - directory under "win32". You can start them by double-clicking their - executable (.exe) files in the "bdist" directory. + Inno Setup officially supports translations for only about 20 languages. + However, one of the great points of Tux Paint is it supports so many + languages. Therefore, the set up script "tuxpaint.iss" to build the + installer is written to use much more translations including unofficial + one which are available on "Inno Setup Translations". You have to download + translation files (.isl) required and put them in "Languages" directory + under the directory in which Inno Setup is installed. - ------------------------------------------------------- + Before building an installer, edit the "tuxpaint.iss" file and enable one + of the lines starting with "#define BuildTarget=", depending on the + architecture of the installer you want to create. - Building the Tux Paint Windows Installer: + Then, you can easily build an executable installer by right-clicking on + the "tuxpaint.iss" icon in the "win32" directory and selecting "Compile" + on the list. It will run for a while, and eventually you will find a + "tuxpaint-X.Y.Z-windows--installer.exe" file in the same directory. - Inno Setup is used to build executable installer for Tux Paint. - Therefore you have to install it in the first place. + Running the Tux Paint Windows Installer - Inno Setup officially supports translations for only about 20 - languages. However, one of the great points of Tux Paint is it - supports so many languages. Therefore, the set up script - "tuxpaint.iss" to build the installer is written to use much more - translations including unofficial one which are available on "Inno - Setup Translations". You have to download translation files (.isl) - required and put them in "Languages" directory under the directory - in which Inno Setup is installed. + Faga dobre clic no executábel do instalador de Tux Paint (ficheiro .EXE) e + siga as instrucións. - Before building an installer, edit the "tuxpaint.iss" file and - enable one of the lines starting with "#define BuildTarget=", - depending on the architecture of the installer you want to create. + First, you will be asked to read the license. (It is the GNU General + Public License (GPL), which is also available as "COPYING.txt".) - Then, you can easily build an executable installer by right-clicking - on the "tuxpaint.iss" icon in the "win32" directory and selecting - "Compile" on the list. It will run for a while, and eventually you - will find a "tuxpaint-X.Y.Z-windows--installer.exe" file in - the same directory. + Após preguntaráselle se quere instalar accesos directos a Tux Paint no seu + menú de inicio de Windows e no escritorio de Windows. (Ámbalas dúas + opcións están definidas de xeito predeterminado.) - ------------------------------------------------------- + A seguir preguntaráselle onde quere instalar Tux Paint. O valor + predeterminado debería ser axeitado, sempre que haxa espazo dispoñíbel. Se + non, escolla un lugar diferente. - Running the Tux Paint Windows Installer: + Neste punto, pode premer en «Instalar» para instalar Tux Paint. - Faga dobre clic no executábel do instalador de Tux Paint (ficheiro - .EXE) e siga as instrucións. + Changing the Settings Using the Shortcut - First, you will be asked to read the license. (It is the GNU General - Public License (GPL), which is also available as "COPYING.txt".) + Para cambiar os axustes do programa, prema co botón dereito no atallo de + TuxPaint e seleccione «Propiedades» (na parte inferior). - Após preguntaráselle se quere instalar accesos directos a Tux Paint - no seu menú de inicio de Windows e no escritorio de Windows. - (Ámbalas dúas opcións están definidas de xeito predeterminado.) + Asegúrese de que a lapela «Atallo» está seleccionada na xanela que aparece + e examine o campo «Obxectivo:». Debería ver algo así: - A seguir preguntaráselle onde quere instalar Tux Paint. O valor - predeterminado debería ser axeitado, sempre que haxa espazo - dispoñíbel. Se non, escolla un lugar diferente. + "C:\Program Files\TuxPaint\TuxPaint.exe" - Neste punto, pode premer en «Instalar» para instalar Tux Paint. + Agora pode engadir opcións de liña de ordes que se activarán ao facer + dobre clic na icona. - ------------------------------------------------------- + Por exemplo, para que o xogo se execute en modo de pantalla completa, con + formas sinxelas (sen opción de rotación) e en francés, engada as opcións + (após «TuxPaint.exe»), así: - Cambiar os axustes usando o acceso directo: + "C:\Program Files\TuxPaint\TuxPaint.exe" -f -s --lang french - Para cambiar os axustes do programa, prema co botón dereito no - atallo de TuxPaint e seleccione «Propiedades» (na parte inferior). + (Vexa a documentación principal para obter unha lista completa das opcións + dispoñíbeis da liña de ordes.) - Asegúrese de que a lapela «Atallo» está seleccionada na xanela que - aparece e examine o campo «Obxectivo:». Debería ver algo así: + Se se trabuca ou desaparece todo, use [Ctrl] + [Z] para desfacer ou só + prema a tecla [Esc] e a caixa pecharase sen facer cambios (a non ser que + premera o botón «Aplicar»). - "C:\Program Files\TuxPaint\TuxPaint.exe" + Cando teña rematado, prema en «Aceptar». - Agora pode engadir opcións de liña de ordes que se activarán ao - facer dobre clic na icona. + If Something Goes Wrong - Por exemplo, para que o xogo se execute en modo de pantalla - completa, con formas sinxelas (sen opción de rotación) e en francés, - engada as opcións (após «TuxPaint.exe»), así: + Se ao facer dobre clic no atallo para executar Tux Paint, non ocorre nada, + probabelmente sexa porque algunhas destas opcións da liña de ordes son + incorrectas. Abra un explorador de ficheiros coma antes e busque un + ficheiro chamado «stderr.txt» no cartafol TuxPaint. - "C:\Program Files\TuxPaint\TuxPaint.exe" -f -s --lang french + Conterá unha descrición do que estaba mal. Normalmente só se debe a + maiúsculas e minúsculas incorrectas (maiúsculas «Z» no canto de minúsculas + «z») ou a falta (ou exceso) de «-» (guións). - (Vexa a documentación principal para obter unha lista completa das - opcións dispoñíbeis da liña de ordes.) +Linux/Unix - Se se trabuca ou desaparece todo, use [Ctrl] + [Z] para desfacer ou - só prema a tecla [Esc] e a caixa pecharase sen facer cambios (a non - ser que premera o botón «Aplicar»). + Compilación: - Cando teña rematado, prema en «Aceptar». + 💡 Note: Tux Paint does not use autoconf/automake, so there is no + "./configure" script to run. Compiling should be straight-forward though, + assuming everything Tux Paint needs is installed. - ------------------------------------------------------- + Para compilar o programa dende o código fonte, simplemente execute a + seguinte orde dende un indicador do sistema (p. ex.: «$»): - Se algo vai mal: + $ make - Se ao facer dobre clic no atallo para executar Tux Paint, non ocorre - nada, probabelmente sexa porque algunhas destas opcións da liña de - ordes son incorrectas. Abra un explorador de ficheiros coma antes e - busque un ficheiro chamado «stderr.txt» no cartafol TuxPaint. + Desactivar a compatibilidade de «SVG» (e, polo tanto, as dependencias de + «Cairo, libSVG, e svg-cairo»: - Conterá unha descrición do que estaba mal. Normalmente só se debe a - maiúsculas e minúsculas incorrectas (maiúsculas «Z» no canto de - minúsculas «z») ou a falta (ou exceso) de «-» (guións). + Para desactivar a compatibilidade con SVG (por exemplo, se o seu sistema + non é compatíbel coa biblioteca de Cairo ou outras dependencias + relacionadas co SVG), pode executar «make» engadindo «SVG_LIB= SVG_CFLAGS= + NOSVGFLAG=NOSVG»: - ---------------------------------------------------------------------- + $ make SVG_LIB= SVG_CFLAGS= - Usuarios de Linux/Unix + Desactivar a compatibilidade de «Pango» (e, polo tanto, as dependencias de + «Pango, Cairo, etc.»: - Compilación: + 📜 Antes da versión 0.9.18, Tux Paint utilizaba a biblioteca libSDL_ttf + para renderizar texto usando tipos de letra TrueType. Dende o 0.9.18 úsase + libSDL_Pango, xa que ten unha mellor compatibilidade coa + internacionalización. Non obstante, se quere desactivar o uso de + SDL_Pango, pode facelo executando «make» engadindo «SDL_PANGO_LIB=»: - Nota: Tux Paint non usa autoconf/automake, polo que non hai ningún - script «./configure» para executar. Non obstante, a compilación - debería ser directa, supoñendo que todo o que precisa Tux Paint está - instalado. + $ make SDL_PANGO_LIB= - Para compilar o programa dende o código fonte, simplemente execute a - seguinte orde dende un indicador do sistema (p. ex.: «$»): + Disabling Sound at Compile-time - $ make + Se non te unha tarxeta de son ou prefire construír o programa sen + asistencia de son (e polo tanto sen a dependencia SDL_mixer), pode + executar «make» con «SDL_MIXER_LIB=» engadido: - ------------------------------------------------------- + $ make SDL_MIXER_LIB= - Desactivar a compatibilidade de «SVG» (e, polo tanto, as dependencias de - «Cairo, libSVG, e svg-cairo»: + Other options - Para desactivar a compatibilidade con SVG (por exemplo, se o seu - sistema non é compatíbel coa biblioteca de Cairo ou outras - dependencias relacionadas co SVG), pode executar «make» engadindo - «SVG_LIB= SVG_CFLAGS= NOSVGFLAG=NOSVG»: + Outras opcións (p. ex.: rutas de instalación) poden ser anuladas; véxaas + en «Makefile» para máis detalles. - $ make SVG_LIB= SVG_CFLAGS= + If you get errors - ------------------------------------------------------- + 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 «-dev» ou + «-devel», se non, non poderá compilar Tux Paint (e outros programas) dende + o código fonte. - Desactivar a compatibilidade de «Pango» (e, polo tanto, as dependencias de - «Pango, Cairo, etc.»: + Installng - Antes da versión 0.9.18, Tux Paint utilizaba a biblioteca libSDL_ttf - para renderizar texto usando tipos de letra TrueType. Dende o 0.9.18 - úsase libSDL_Pango, xa que ten unha mellor compatibilidade coa - internacionalización. Non obstante, se quere desactivar o uso de - SDL_Pango, pode facelo executando «make» engadindo «SDL_PANGO_LIB=»: + Supoñendo que non se produciron erros graves, agora pode instalar o + programa para que os usuarios do sistema poidan executalo. De xeito + predeterminado, isto debe facelo o usuario «root» («superusuario»). Cambie + a «root» escribindo a orde: - $ make SDL_PANGO_LIB= + $ su - ------------------------------------------------------- + Introduza o contrasinal de «root» no indicador do sistema. Agora debería + ser «root» (cun indicador como «#»). Para instalar o programa e os seus + ficheiros de datos, escriba: - Desactivación do son en tempo de compilación: + # make install - Se non te unha tarxeta de son ou prefire construír o programa sen - asistencia de son (e polo tanto sen a dependencia SDL_mixer), pode - executar «make» con «SDL_MIXER_LIB=» engadido: + Finalmente, pode volver ao seu usuario habitual saíndo do modo de + superusuario: - $ make SDL_MIXER_LIB= + # exit - ------------------------------------------------------- + Como alternativa, pode simplemente usar a orde «sudo» (po.ex.: en Ubuntu + Linux): - Outras opcións: + $ sudo make install - Outras opcións (p. ex.: rutas de instalación) poden ser anuladas; - véxaas en «Makefile» para máis detalles. + 💡 Note: By default, "tuxpaint", the executable program, is placed in + "/usr/local/bin/". The data files (images, sounds, etc.) are placed in + "/usr/local/share/tuxpaint/". - ------------------------------------------------------- + Cambiar onde van as cousas - Se se producen erros: + Pode cambiar onde irán as cousas axustando as variábeis de «Makefile» na + liña de ordes. «DESTDIR» úsase para colocar a saída nunha área de espera + para a creación de paquetes. «PREFIX» é a base de onde van todos os demais + ficheiros e, de xeito predeterminado, está estabelecido en «/usr/local». - 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 «-dev» ou «-devel», se non, non poderá - compilar Tux Paint (e outros programas) dende o código fonte. + Outras variábeis son: - ------------------------------------------------------- + BIN_PREFIX + Onde se instalará o binario «tuxpaint». (Estabelécese como + «$(PREFIX)/bin»como predeterminado, p. ex.: «/usr/local/bin») - Instalar: + DATA_PREFIX + Onde irán os ficheiros de datos (son, gráficos, pinceis, selos, + tipos de letra) e onde os buscará Tux Paint cando se execute. + (Estabelecer en «$(PREFIX)/share/tuxpaint») - Supoñendo que non se produciron erros graves, agora pode instalar o - programa para que os usuarios do sistema poidan executalo. De xeito - predeterminado, isto debe facelo o usuario «root» («superusuario»). - Cambie a «root» escribindo a orde: + DOC_PREFIX + Onde irán os ficheiros de texto da documentación (o directorio + «docs»). (Estabelecer como «$(PREFIX)/share/doc/tuxpaint») - $ su + MAN_PREFIX + Onde irá a páxina do manual de Tux Paint. (Estabelecer como + «$(PREFIX)/share/man») - Introduza o contrasinal de «root» no indicador do sistema. Agora - debería ser «root» (cun indicador como «#»). Para instalar o - programa e os seus ficheiros de datos, escriba: + ICON_PREFIX — $(PREFIX)/share/pixmaps - # make install + X11_ICON_PREFIX — $(PREFIX)/X11R6/include/X11/pixmaps - Finalmente, pode volver ao seu usuario habitual saíndo do modo de - superusuario: + GNOME_PREFIX — $(PREFIX)/share/gnome/apps/Graphics - # exit + KDE_PREFIX — $(PREFIX)/share/applnk/Graphics + Onde irán as iconas e os lanzadores (para GNOME e KDE). - Como alternativa, pode simplemente usar a orde «sudo» (po.ex.: en - Ubuntu Linux): + LOCALE_PREFIX + Onde irán os ficheiros de tradución para Tux Paint e onde os + buscará Tux Paint. (Estabelécese en «$(PREFIX)/share/locale/») (A + localización final dun ficheiro de tradución estará no directorio + da configuración local (por exemplo, «es» para o español), dentro + do subdirectorio «LC_MESSAGES»). - $ sudo make install + 💡 Note: This list is out of date. See "Makefile" and "Makefile-i18n" for a + complete list. - Nota: De xeito predeterminado, «tuxpaint», o programa executábel, - colócase en «/usr/local/bin/». Os ficheiros de datos (imaxes, sons, - etc.) colócanse en «/usr/local/share/tuxpaint/». +macOS - Cambiar onde van as cousas + 20 de Xaneiro de 2022 Mark Kim - Pode cambiar onde irán as cousas axustando as variábeis de - «Makefile» na liña de ordes. «DESTDIR» úsase para colocar a saída - nunha área de espera para a creación de paquetes. «PREFIX» é a - base de onde van todos os demais ficheiros e, de xeito - predeterminado, está estabelecido en «/usr/local». + 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. - Outras variábeis son: + Prerequisites - BIN_PREFIX - Onde se instalará o binario «tuxpaint». (Estabelécese como - «$(PREFIX)/bin»como predeterminado, p. ex.: - «/usr/local/bin») + 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: - DATA_PREFIX - Onde irán os ficheiros de datos (son, gráficos, pinceis, - selos, tipos de letra) e onde os buscará Tux Paint cando - se execute. (Estabelecer en «$(PREFIX)/share/tuxpaint») + xcode-select --install - DOC_PREFIX - Onde irán os ficheiros de texto da documentación (o - directorio «docs»). (Estabelecer como - «$(PREFIX)/share/doc/tuxpaint») + 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 + * libsdl_gfx + * pkgconfig + * zlib + ... but you should install any package that is required by the latest + version of Tux Paint. - MAN_PREFIX - Onde irá a páxina do manual de Tux Paint. (Estabelecer - como «$(PREFIX)/share/man») + ^* Not available from MacPorts as of this writing, see below. - ICON_PREFIX — $(PREFIX)/share/pixmaps + libimagequant - X11_ICON_PREFIX — $(PREFIX)/X11R6/include/X11/pixmaps + 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. - GNOME_PREFIX — $(PREFIX)/share/gnome/apps/Graphics + $ sudo port install rust cargo + $ git clone https://github.com/ImageOptim/libimagequant.git + $ cd libimagequant/imagequant-sys + $ cargo build --release # Must use cargo from MacPorts + $ sudo make PREFIX=/opt/local install - KDE_PREFIX — $(PREFIX)/share/applnk/Graphics - Onde irán as iconas e os lanzadores (para GNOME e KDE). + 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. - LOCALE_PREFIX - Onde irán os ficheiros de tradución para Tux Paint e onde - os buscará Tux Paint. (Estabelécese en - «$(PREFIX)/share/locale/») (A localización final dun - ficheiro de tradución estará no directorio da - configuración local (por exemplo, «es» para o español), - dentro do subdirectorio «LC_MESSAGES»). + How to Build - Nota: Esta lista non está actualizada. Consulte «Makefile» e - «Makefile-i18n» para ver unha lista completa. + Simply, run: + + % make + % make install + + ... to create the TuxPaint.app application bundle that can be run in-place + or copied to /Applications. To create the DMG file for distribution, use + 'make TuxPaint.dmg'. + + Additional steps may be required when building for the Apple Silicon. See + "Building for Apple Silicon" below. + + 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. + + Alternatively, Tux Paint and all of its library dependencies may be + compiled with appropriate options to be runnable on older versions of + macOS. These options are already set on Tux Paint, so only its + dependencies (from MacPorts) need to be recompiled. See "Recompiling + MacPorts" below for the instructions. + + 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 for Intel CPU does allow dual booting of multiple versions of the + OS, but it's safer and easier to install the old macOS onto a flash drive. + Wherever you're installing it, the target drive's partitioniong scheme and + partition type must match what the old macOS expects, so use the Disk + Utility to partition and format the flash drive accordingly. + + Dual booting multiple versions of macOS for Apple Silicon has been so far + unsuccessful. Instead of installing an older version of macOS for Apple + Silicon to build Tux Paint to run on the old version of macOS for Apple + Silicon, use the instructions found in the "Recompiling MacPorts" section + to build Tux Paint to run on older versions of macOS for Apple Silicon. + + 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 + + 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. - Usuarios de macOS + Recompiling MacPorts - 20 de Xaneiro de 2022 Mark Kim + To recompile MacPorts to be usable on older versions of macOS, set the + following options in /opt/local/etc/macports/macports.conf: - 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. + buildfromsource always + macosx_deployment_target 10.10 - Prerequisites + Then uninstall all MacPorts packages: - 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: + $ sudo port -fp uninstall installed - xcode-select --install + Then reinstall all MacPorts packages needed by Tux Paint. Also rebuild + libimagequant using the updated Cargo package from MacPorts. - 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 - * libsdl_gfx - * pkgconfig - * zlib - ... but you should install any package that is required by the - latest version of Tux Paint. + As of this writing, all libraries Tux Paint requires from MacPorts can be + recompiled in this manner to run on macOS 10.10 Yosemite and later on + Intel CPUs, and macOS 11.0 Big Sur and later on Apple Silicon. + Unfortunately, although MacPorts has the option to enable the building of + universal libraries, several libraries Tux Paint require cannot be built + as universal libraries so they can only be built to run natively on the + hardware on which they were built. See "Building a Universal Binary" below + for instructions on how to build Tux Paint as a Universal Binary. - ^* 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. + Building for Apple Silicon - $ sudo port install rust cargo - $ git clone https://github.com/ImageOptim/libimagequant.git - $ cd libimagequant/imagequant-sys - $ cargo build --release # Must use cargo from MacPorts - $ sudo make PREFIX=/opt/local install + macOS for Applie Silicon requires all native Apple Silicon applications be + signed, even if it is signed "ad-hoc" (anonymously). Because of this, + compilers that produce native Apple Silicon applications sign all produced + binaries and libraries as a part of the compilation process.^* However, + the Tux Paint compilation process modifies the libraries to be modular + (using install_name_tool) so they can be added into the application + bundle, which has the unfortunate side effect of breaking the signature. + This can be addressed by signing the application bundle ad-hoc (example + below) or using your own Apple Developer Identity if you have one. The DMG + file, if needed, must be created after signing the App Bundle so the DMG + file is created with signed App Bundle: - 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. + $ codesign -s - TuxPaint.app + $ make TuxPaint.dmg - ------------------------------------------------------- + ^* For more information on the code signing requirements on the Apple + Silicon, see + https://developer.apple.com/documentation/macos-release-notes/macos-big-sur-11_0_1-universal-apps-release-notes#:~:text=New%20in%20macOS,pass%20through%20Gatekeeper. - How to Build + If you get an error that the application bundle is already signed, remove + it before signing:: - Simply, run: - - % make - % make install + $ codesign --remove-signature TuxPaint.app - ... to create the TuxPaint.app application bundle that can be run - in-place or copied to /Applications. To create the DMG file for - distribution, use 'make TuxPaint.dmg'. + If you plan to combine the Apple Silicon bundle with the Intel CPU bundle + to produce the Universal bundle, the code signing must be done after they + are combined. See "Building a Universal Binary" below. - Additional steps may be required when building for the Apple - Silicon. See "Building for Apple Silicon" below. - - ------------------------------------------------------- - - 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. - - Alternatively, Tux Paint and all of its library dependencies may - be compiled with appropriate options to be runnable on older - versions of macOS. These options are already set on Tux Paint, - so only its dependencies (from MacPorts) need to be recompiled. - See "Recompiling MacPorts" below for the instructions. - - ------------------------------------------------------- - - 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 for Intel CPU does allow dual booting of multiple versions of - the OS, but it's safer and easier to install the old macOS onto a - flash drive. Wherever you're installing it, the target drive's - partitioniong scheme and partition type must match what the old - macOS expects, so use the Disk Utility to partition and format the - flash drive accordingly. - - Dual booting multiple versions of macOS for Apple Silicon has been - so far unsuccessful. Instead of installing an older version of macOS - for Apple Silicon to build Tux Paint to run on the old version of - macOS for Apple Silicon, use the instructions found in the - "Recompiling MacPorts" section to build Tux Paint to run on older - versions of macOS for Apple Silicon. - - 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 - - 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/ + Building a Universal Binary - 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 + To build Tux Paint as a Universal Binary, compile Tux Paint for the Intel + CPU and the Apple Silicon separately first. Then rename the app bundle for + the Intel CPU to TuxPaint-x86_64.app, and the bundle for the Apple Silicon + to TuxPaint-arm64.app, copy the app bundle from the Intel machine to the + Apple Silicon machine, then use the provided build-universal.sh script to + combine the two application bundles as below. The produced bundle must be + signed (see "Building for Apple Silicon" above for more details). The DMG + file, if required, must be built after the signing: - 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. + $ macos/build-universal.sh + $ codesign -s - TuxPaint.app + $ make TuxPaint.dmg - Recompiling MacPorts + Debugging - To recompile MacPorts to be usable on older versions of macOS, set - the following options in /opt/local/etc/macports/macports.conf: + ⚙ Debugging output — to "STDOUT" on Linux and Unix, to a "stdout.txt" file + on Windows, and to the file "/tmp/tuxpaint.log" on macOS — can be enabled + by setting "DEBUG" (and, if verbose logging is wanted, "VERBOSE") #defines + in "src/debug.h" and (re)compiling Tux Paint. - buildfromsource always - macosx_deployment_target 10.10 + Uninstalling Tux Paint - Then uninstall all MacPorts packages: +Windows - $ sudo port -fp uninstall installed + Uso do desinstalador - Then reinstall all MacPorts packages needed by Tux Paint. Also - rebuild libimagequant using the updated Cargo package from MacPorts. + Se instalou os atallos do menú Inicio (o predeterminado), vaia ao cartafol + TuxPaint e seleccione «Desinstalar». Amosarase unha caixa que confirmará + que está a piques de desinstalar Tux Paint e, se está seguro de que quere + eliminar permanentemente Tux Paint, prema no botón «Desinstalar». - As of this writing, all libraries Tux Paint requires from MacPorts - can be recompiled in this manner to run on macOS 10.10 Yosemite and - later on Intel CPUs, and macOS 11.0 Big Sur and later on Apple - Silicon. Unfortunately, although MacPorts has the option to enable - the building of universal libraries, several libraries Tux Paint - require cannot be built as universal libraries so they can only be - built to run natively on the hardware on which they were built. See - "Building a Universal Binary" below for instructions on how to build - Tux Paint as a Universal Binary. + Cando remate, prema no botón pechar. - Building for Apple Silicon + Usar o Panel de control - macOS for Applie Silicon requires all native Apple Silicon - applications be signed, even if it is signed "ad-hoc" (anonymously). - Because of this, compilers that produce native Apple Silicon - applications sign all produced binaries and libraries as a part of - the compilation process.^* However, the Tux Paint compilation - process modifies the libraries to be modular (using - install_name_tool) so they can be added into the application bundle, - which has the unfortunate side effect of breaking the signature. - This can be addressed by signing the application bundle ad-hoc - (example below) or using your own Apple Developer Identity if you - have one. The DMG file, if needed, must be created after signing the - App Bundle so the DMG file is created with signed App Bundle: + Tamén é posíbel usar a entrada «TuxPaint (só eliminar)« na sección + Engadir/Eliminar programas do Panel de control. - $ codesign -s - TuxPaint.app - $ make TuxPaint.dmg +macOS - ^* For more information on the code signing requirements on the - Apple Silicon, see - https://developer.apple.com/documentation/macos-release-notes/macos-big-sur-11_0_1-universal-apps-release-notes#:~:text=New%20in%20macOS,pass%20through%20Gatekeeper. + Delete "TuxPaint.app" from the "Applications" folder. Data files, + including the configuration files, stamps, and saved pictures, may be + found in "Library/Application Support/TuxPaint" (all users) and + "/Users/USERNAME/Library/Application Support/TuxPaint" (individual users). - If you get an error that the application bundle is already signed, - remove it before signing:: +Linux - $ codesign --remove-signature TuxPaint.app - - If you plan to combine the Apple Silicon bundle with the Intel CPU - bundle to produce the Universal bundle, the code signing must be - done after they are combined. See "Building a Universal Binary" - below. - - Building a Universal Binary - - To build Tux Paint as a Universal Binary, compile Tux Paint for the - Intel CPU and the Apple Silicon separately first. Then rename the - app bundle for the Intel CPU to TuxPaint-x86_64.app, and the bundle - for the Apple Silicon to TuxPaint-arm64.app, copy the app bundle - from the Intel machine to the Apple Silicon machine, then use the - provided build-universal.sh script to combine the two application - bundles as below. The produced bundle must be signed (see "Building - for Apple Silicon" above for more details). The DMG file, if - required, must be built after the signing: - - $ macos/build-universal.sh - $ codesign -s - TuxPaint.app - $ make TuxPaint.dmg - - ---------------------------------------------------------------------- - -Debugging - - Debugging output — to "STDOUT" on Linux and Unix, to a "stdout.txt" file - on Windows, and to the file "/tmp/tuxpaint.log" on macOS — can be - enabled by setting "DEBUG" (and, if verbose logging is wanted, - "VERBOSE") #defines in "src/debug.h" and (re)compiling Tux Paint. - - ---------------------------------------------------------------------- - -Uninstalling Tux Paint - - Windows - - Uso do desinstalador - - Se instalou os atallos do menú Inicio (o predeterminado), vaia ao - cartafol TuxPaint e seleccione «Desinstalar». Amosarase unha caixa - que confirmará que está a piques de desinstalar Tux Paint e, se está - seguro de que quere eliminar permanentemente Tux Paint, prema no - botón «Desinstalar». - - Cando remate, prema no botón pechar. - - Usar o Panel de control - - Tamén é posíbel usar a entrada «TuxPaint (só eliminar)« na sección - Engadir/Eliminar programas do Panel de control. - - ---------------------------------------------------------------------- - - macOS - - Delete "TuxPaint.app" from the "Applications" folder. Data files, - including the configuration files, stamps, and saved pictures, may be - found in "Library/Application Support/TuxPaint" (all users) and - "/Users/USERNAME/Library/Application Support/TuxPaint" (individual - users). - - ---------------------------------------------------------------------- - - Linux - - Within the Tux Paint source directory (where you compiled Tux Paint), - you can use the "make uninstall" target to uninstall Tux Paint. By - default, this must be done by the "root" user ('superuser'), but if - you installed Tux Paint somewhere else (e.g., using a "PREFIX=..." - setting to "make" and "make install"), you may not, and will want to - provide those same settings here. (See the installation instructions - above for further information.) + Within the Tux Paint source directory (where you compiled Tux Paint), you + can use the "make uninstall" target to uninstall Tux Paint. By default, + this must be done by the "root" user ('superuser'), but if you installed + Tux Paint somewhere else (e.g., using a "PREFIX=..." setting to "make" and + "make install"), you may not, and will want to provide those same settings + here. (See the installation instructions above for further information.) diff --git a/docs/gl_ES.UTF-8/html/EXTENDING.html b/docs/gl_ES.UTF-8/html/EXTENDING.html index a8af76155..df5ab9f7b 100644 --- a/docs/gl_ES.UTF-8/html/EXTENDING.html +++ b/docs/gl_ES.UTF-8/html/EXTENDING.html @@ -21,15 +21,17 @@ } div.keeptogether { page-break-inside: avoid; } section h1 { font-size: 2em; } - h1, h2, h3, h4 { font-family: sans; } + h1, h2, h3, h4, h5 { font-family: sans; } h1 { color: #800; page-break-before: always; break-before: always; } h2 { color: #440; page-break-after: avoid; break-after: avoid; } h3 { color: #080; page-break-after: avoid; break-after: avoid; } h4 { color: #008; page-break-after: avoid; break-after: avoid; } + h5 { color: #808; page-break-after: avoid; break-after: avoid; } h1 + p { page-break-inside: avoid; } h2 + p { page-break-inside: avoid; } h3 + p { page-break-inside: avoid; } h4 + p { page-break-inside: avoid; } + h5 + p { page-break-inside: avoid; } dt { font-size: large; color: #404; diff --git a/docs/gl_ES.UTF-8/html/INSTALL.html b/docs/gl_ES.UTF-8/html/INSTALL.html index cdaa21d16..898c80374 100644 --- a/docs/gl_ES.UTF-8/html/INSTALL.html +++ b/docs/gl_ES.UTF-8/html/INSTALL.html @@ -5,249 +5,312 @@ Documentación da instalación de Tux Paint + -

-

- Tux Paint
- versión 0.9.28
- Documentación da instalación

+
+
+
+

+ Tux Paint
+ versión 0.9.28
+ Documentación da instalación

-

- Copyright © 2002-2022 by varios colaboradores; see AUTHORS.txt.
- https://tuxpaint.org/ -

+

+ Copyright © 2002-2022 by varios colaboradores; see AUTHORS.txt.
+ https://tuxpaint.org/ +

-

- 20 de Xaneiro de 2022

-
+

+ 31 de Marzo de 2022

+
+ -
+ + + + -
+ Índice
- - - + + + +
- Índice
+ +
+
- - - - - - +
+
+

+ + Requirements +

+
-
+
+
+

+ + Simple DirectMedia Layer library (libSDL) +

+
-

- - Requirements -

-
- -

- - Simple DirectMedia Layer library (libSDL) -

-

Tux Paint require a «Simple DirectMedia Layer Library (libSDL)», unha biblioteca de programación multimedia de código aberto dispoñíbel baixo a licenza pública GNU Lesser General Public License (LGPL).

Along with libSDL, Tux Paint depends on a number of other SDL 'helper' libraries: SDL_Image (for graphics files), SDL_gfx (for some graphical functions, like rotation), SDL_TTF and (optionally) SDL_Pango (for True Type Font support) and, optionally, SDL_Mixer (for sound effects).

-

Usuarios de Linux/Unix:

-
-

- As bibliotecas SDL están dispoñíbeis como código fonte ou como paquetes RPM ou Debian para varias distribucións de Linux. Pódense descargar dende:

- +
+
Linux/Unix
+
+

+ As bibliotecas SDL están dispoñíbeis como código fonte ou como paquetes RPM ou Debian para varias distribucións de Linux. Pódense descargar dende:

+ -

- Normalmente tamén están dispoñíbeis xunto coa súa distribución de Linux (p. ex.: nun medio de instalación ou dispoñíbeis a través dun software de mantemento de paquetes como «apt» de Debian).

+

+ Normalmente tamén están dispoñíbeis xunto coa súa distribución de Linux (p. ex.: nun medio de instalación ou dispoñíbeis a través dun software de mantemento de paquetes como «apt» de Debian).

-

- Nota: Cando instale bibliotecas a partir de paquetes, asegúrese de instalar TAMÉN as versións de desenvolvemento dos paquetes. (Por exemplo, instale tanto «SDL-1.2.4.rpm» como «SDL-1.2.4-devel.rpm».).

-
-
+

+ 💡 Note: When installing libraries from packages, be sure to ALSO install the development versions of the packages. (For example, install both "SDL-1.2.4.rpm" and "SDL-1.2.4-devel.rpm".)

+ + +
+ +
+
+

+ + Outras bibliotecas +

+
-

- - Outras bibliotecas -

-

Tux Paint tamén aproveita outras bibliotecas libres con licenza LGPL. En Linux, do mesmo xeito que SDL, deberían estar xa instaladas ou estar dispoñíbeis para a súa instalación como parte da súa distribución de Linux.

-

libPNG

-
-

- Tux Paint utiliza o formato PNG (Portable Network Graphics – Gráficos de Rede Portátiles) para os seus ficheiros de datos. A imaxe SDL requirirá a instalación de libPNG.

+
+
libPNG
+
+

+ Tux Paint utiliza o formato PNG (Portable Network Graphics – Gráficos de Rede Portátiles) para os seus ficheiros de datos. A imaxe SDL requirirá a instalación de libPNG.

-

- http://www.libpng.org/pub/png/libpng.html -

-
+

+ http://www.libpng.org/pub/png/libpng.html +

+ -

gettext

-
-

- Tux Paint utiliza a configuración local do sistema xunto coa biblioteca «gettext» para admitir varios idiomas (p. ex., o español). Necesitará ter a biblioteca gettext instalada.

+
gettext
+
+

+ Tux Paint utiliza a configuración local do sistema xunto coa biblioteca «gettext» para admitir varios idiomas (p. ex., o español). Necesitará ter a biblioteca gettext instalada.

-

- http://www.gnu.org/software/gettext/ -

-
+

+ http://www.gnu.org/software/gettext/ +

+ -

libpaper (Só Linux/Unix)

-
-

- A partir de Tux Paint 0.9.17, Tux Paint pode determinar o tamaño de papel predeterminado do seu sistema (p. ex.: A4 ou Carta), ou pódeselle indicar que use un tamaño de papel particular, grazas a «libpaper».

+
libpaper (Só Linux/Unix)
+
+

+ A partir de Tux Paint 0.9.17, Tux Paint pode determinar o tamaño de papel predeterminado do seu sistema (p. ex.: A4 ou Carta), ou pódeselle indicar que use un tamaño de papel particular, grazas a «libpaper».

-

- https://github.com/naota/libpaper -

-
+

+ https://github.com/naota/libpaper +

+ -

FriBiDi

-
-

- As ferramentas «Texto» e «Etiqueta» de Tux Paint admiten linguaxes bidireccionais grazas á biblioteca «FriBiDi».

+
FriBiDi
+
+

+ As ferramentas «Texto» e «Etiqueta» de Tux Paint admiten linguaxes bidireccionais grazas á biblioteca «FriBiDi».

-

- http://fribidi.org/ -

-
+

+ http://fribidi.org/ +

+ -

Compatibilidade de SVG

-
-

- A partir de Tux Paint 0.9.17, Tux Paint pode cargar imaxes SVG (Scalable Vector Graphics — Gráficos Vectoriais Escalábeis) como selos. Admítense dous conxuntos de bibliotecas e pódese desactivar completamente a compatibilidade SVG (a través de «make SVG_LIB:=»)

+
Compatibilidade de SVG
+
+

+ A partir de Tux Paint 0.9.17, Tux Paint pode cargar imaxes SVG (Scalable Vector Graphics — Gráficos Vectoriais Escalábeis) como selos. Admítense dous conxuntos de bibliotecas e pódese desactivar completamente a compatibilidade SVG (a través de «make SVG_LIB:=»)

-
librsvg-2 & libCairo2 (bibliotecas máis recentes)
- +
+
librsvg-2 & libCairo2 (bibliotecas máis recentes)
+
+ +
-
Bibliotecas SVG máis antigas
- -
+
Bibliotecas SVG máis antigas
+
+ +
+ + -

Función de exportación de GIF animado

-
-

- Para a compatibilidade da exportación de GIF animados (presentacións de diapositivas), é necesaria a biblioteca «libimagequant» (do proxecto «pngquant2»).

+
Función de exportación de GIF animado
+
+

+ Para a compatibilidade da exportación de GIF animados (presentacións de diapositivas), é necesaria a biblioteca «libimagequant» (do proxecto «pngquant2»).

-

- https://github.com/ImageOptim/libimagequant -

-
+

+ https://github.com/ImageOptim/libimagequant +

+ -

Ferramentas NetPBM (opcional) Xa non se usa, de xeito predeterminado

-
-

- En Linux e Unix, as versións anteriores de Tux Paint utilizaban as ferramentas NetPBM para axudar á impresión. (Tux Paint xera un PNG e convértese nun PostScript usando as ferramentas da liña de ordes NetPBM «pngtopnm» e «pnmtops»).

+
Ferramentas NetPBM (opcional) Xa non se usa, de xeito predeterminado
+
+

+ 📜 En Linux e Unix, as versións anteriores de Tux Paint utilizaban as ferramentas NetPBM para axudar á impresión. (Tux Paint xera un PNG e convértese nun PostScript usando as ferramentas da liña de ordes NetPBM «pngtopnm» e «pnmtops»).

-

- http://netpbm.sourceforge.net/ -

-
-
- +

+ http://netpbm.sourceforge.net/ +

+ + +
+
-
+
+
+

+ + Compiling and Installation +

+
-

- - Compiling and Installation -

-

Tux Paint publícase baixo a Licenza Pública Xeral de GNU (GPL) (consulte «COPYING.txt» para máis detalles) e, polo tanto, o «código fonte» do programa está dispoñíbel libremente.

-

- - Usuarios de Windows -

-

- - 3 de Novembro de 2021 Shin-ichi TOYAMA dolphin6k@wmail.plala.or.jp <dolphin6k@wmail.plala.or.jp> - -

-
-

Compiling Set-Up

-
+
+
+

+ + Windows +

+ +

+ + 3 de Novembro de 2021 Shin-ichi TOYAMA dolphin6k@wmail.plala.or.jp <dolphin6k@wmail.plala.or.jp> + +

+
+ +
+
+

Compiling Set-Up

+
+

A partir de febreiro de 2005 (comezando con Tux Paint 0.9.15), o «Makefile» inclúe compatibilidade para construír nun sistema Windows usando MinGW/MSYS (https://sourceforge.net/projects/msys2/).

@@ -276,183 +339,194 @@

-
+

+ + Proceed to the next "MinGW 64bit (x86_64) toolchains" section, or skip to the "MinGW 32bit (i686) toolchains" section if you need only a 32bit build environment. +

-

- - Proceed to the next "MinGW 64bit (x86_64) toolchains" section, or skip 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 64bit development tools:

- - pacman -S mingw-w64-x86_64-toolchain - -
-

- -
- -

- 64bit (x86_64) dependency libraries for Tux Paint

- -
-

- You can install tools and libraries required for compiling Tux Paint on MSYS2/MINGW using "pacman" except for SDL_Pango.

-

- "ntldd" is a small tool which examine windows executable files to list Dynamic Link Library (.dll) files they depends on. Tux Paint's packaging process for binary distribution uses it to find required .dll files.

-

- FLTK is a cross-platform GUI toolkit used by "Tux Paint Config.". You can skip installing it if you are only building "Tux Paint".

-

-

- - $ pacman -S mingw-w64-x86_64-SDL_{image,mixer,ttf,gfx}
- $ pacman -S mingw-w64-x86_64-librsvg
- $ pacman -S mingw-w64-x86_64-fribidi
- $ pacman -S mingw-w64-x86_64-libimagequant
- $ pacman -S mingw-w64-x86_64-fltk
- $ pacman -S mingw-w64-x86_64-ntldd-git - -
-

-

- Note: Close the shell before proceeding to the remaining process.

- -
- -

- Install SDL_Pango on the 64bit environment

- -
-

- SDL_Pango should be installed manually.

-

- This time, use the MinGW "64bit" shell. Open the shell from the "Start Menu" -> "MSYS2 64bit" -> "MSYS2 MinGW 64-bit"

- -
SDL_Pango
- -
- -

- At first, you have to prepare source tar-ball and a required patch in the same directory.

- -

- Build and install SDL_Pango as follows.

- - $ tar zxvf SDL_Pango-0.1.2.tar.gz
- $ cd SDL_Pango-0.1.2/
- $ patch -p0 < ../SDL_Pango-configure-extra-api.patch
- $ ./configure --prefix=/mingw64 && make && make install - -
-

-
- -
- -

- - Proceed to the next "MinGW 32bit (i686) toolchains" section, or skip 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 32bit development tools:

- - pacman -S mingw-w64-i686-toolchain - -
-

- -
- -

- 32bit (i686) dependency libraries for Tux Paint

- -
-

- You can install tools and libraries required for compiling Tux Paint on MSYS2/MINGW using "pacman" except for SDL_Pango.

-

- "ntldd" is a small tool which examine windows executable files to list Dynamic Link Library (.dll) files they depends on. Tux Paint's packaging process for binary distribution uses it to find required .dll files.

-

- FLTK is a cross-platform GUI toolkit used by "Tux Paint Config.". You can skip installing it if you are only building "Tux Paint".

-

-

- - $ pacman -S mingw-w64-i686-SDL_{image,mixer,ttf,gfx}
- $ pacman -S mingw-w64-i686-librsvg
- $ pacman -S mingw-w64-i686-fribidi
- $ pacman -S mingw-w64-i686-libimagequant
- $ pacman -S mingw-w64-i686-fltk
- $ pacman -S mingw-w64-i686-ntldd-git - -
-

-

- Note: Close the shell before proceeding to the remaining process.

- -
- -

- Install SDL_Pango on the 32bit environment

- -
-

- SDL_Pango should be installed manually.

-

- This time, use the MinGW "32bit" shell. Open the shell from the "Start Menu" -> "MSYS2 64bit" -> "MSYS2 MinGW 32-bit"

- -
SDL_Pango
- -
+
+
+

+ + MinGW 64bit (x86_64) toolchains +

+

- At first, you have to prepare source tar-ball and a required patch in the same directory.

- -

- Build and install SDL_Pango as follows.

+ Within the MSYS2 shell, run the following command to install basic 64bit development tools:
- $ tar zxvf SDL_Pango-0.1.2.tar.gz
- $ cd SDL_Pango-0.1.2/
- $ patch -p0 < ../SDL_Pango-configure-extra-api.patch
- $ ./configure --prefix=/mingw32 && make && make install + pacman -S mingw-w64-x86_64-toolchain

-
+
-
+
+
+

+ 64bit (x86_64) dependency libraries for Tux Paint

+
- -
+

+ You can install tools and libraries required for compiling Tux Paint on MSYS2/MINGW using "pacman" except for SDL_Pango.

+

+ "ntldd" is a small tool which examine windows executable files to list Dynamic Link Library (.dll) files they depends on. Tux Paint's packaging process for binary distribution uses it to find required .dll files.

+

+ FLTK is a cross-platform GUI toolkit used by "Tux Paint Config.". You can skip installing it if you are only building "Tux Paint".

+

+

+ + $ pacman -S mingw-w64-x86_64-SDL_{image,mixer,ttf,gfx}
+ $ pacman -S mingw-w64-x86_64-librsvg
+ $ pacman -S mingw-w64-x86_64-fribidi
+ $ pacman -S mingw-w64-x86_64-libimagequant
+ $ pacman -S mingw-w64-x86_64-fltk
+ $ pacman -S mingw-w64-x86_64-ntldd-git + +
+

+

+ 💡 Note: Close the shell before proceeding to the remaining process.

+
-

- ImageMagick -

+
+
+

+ Install SDL_Pango on the 64bit environment

+
+ +

+ SDL_Pango should be installed manually.

+

+ This time, use the MinGW "64bit" shell. Open the shell from the "Start Menu" -> "MSYS2 64bit" -> "MSYS2 MinGW 64-bit"

+ +
+
+
SDL_Pango
+
+ +

+ At first, you have to prepare source tar-ball and a required patch in the same directory.

+

+

+ Build and install SDL_Pango as follows.

+ + $ tar zxvf SDL_Pango-0.1.2.tar.gz
+ $ cd SDL_Pango-0.1.2/
+ $ patch -p0 < ../SDL_Pango-configure-extra-api.patch
+ $ ./configure --prefix=/mingw64 && make && make install + +
+

+
+ +

+ + Proceed to the next "MinGW 32bit (i686) toolchains" section, or skip 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 32bit development tools:

+ + pacman -S mingw-w64-i686-toolchain + +
+

+
+ +
+
+

+ 32bit (i686) dependency libraries for Tux Paint

+
+ +

+ You can install tools and libraries required for compiling Tux Paint on MSYS2/MINGW using "pacman" except for SDL_Pango.

+

+ "ntldd" is a small tool which examine windows executable files to list Dynamic Link Library (.dll) files they depends on. Tux Paint's packaging process for binary distribution uses it to find required .dll files.

+

+ FLTK is a cross-platform GUI toolkit used by "Tux Paint Config.". You can skip installing it if you are only building "Tux Paint".

+

+

+ + $ pacman -S mingw-w64-i686-SDL_{image,mixer,ttf,gfx}
+ $ pacman -S mingw-w64-i686-librsvg
+ $ pacman -S mingw-w64-i686-fribidi
+ $ pacman -S mingw-w64-i686-libimagequant
+ $ pacman -S mingw-w64-i686-fltk
+ $ pacman -S mingw-w64-i686-ntldd-git + +
+

+

+ 💡 Note: Close the shell before proceeding to the remaining process.

+
+ +
+
+

+ Install SDL_Pango on the 32bit environment

+
+ +

+ SDL_Pango should be installed manually.

+

+ This time, use the MinGW "32bit" shell. Open the shell from the "Start Menu" -> "MSYS2 64bit" -> "MSYS2 MinGW 32-bit"

+ +
+
+
SDL_Pango
+
+ +

+ At first, you have to prepare source tar-ball and a required patch in the same directory.

+

+

+ Build and install SDL_Pango as follows.

+ + $ tar zxvf SDL_Pango-0.1.2.tar.gz
+ $ cd SDL_Pango-0.1.2/
+ $ patch -p0 < ../SDL_Pango-configure-extra-api.patch
+ $ ./configure --prefix=/mingw32 && make && make install + +
+

+
+ + +
+ +
+ +
+
+

+ ImageMagick +

+
-

ImageMagick is a compilation of command line tools to create, edit, compose, or convert bitmap images supporting quite a large number of image formats. Tux Paint uses two functions ("convert" and "composite") in it to generate thumbnails for startar images and templates during the build process.

@@ -468,13 +542,13 @@

You can make this permanent by adding the above to your the BASH shell configuration file, "~/.bash_profile".

-
+
-
+
+
+

Tux Paint

+
-

Tux Paint

- -

You can compile 64bit binaries using MSYS2 64bit shell, and 32bit binaries using MSYS2 32bit shell, respectively.

    @@ -490,16 +564,17 @@

-

- Note: At this point, you will want to build "Tux Paint Config." for Windows, so it can be included along with "Tux Paint", if you're making an official (or test) release. The build process will look for it in a directory named "tuxpaint-config" (with no version number, e.g., "tuxpaint-config-X.Y.Z"). See "Tux Paint Config."'s INSTALL.txt documentation for details.

+

+ 💡 Note: At this point, you will want to build "Tux Paint Config." for Windows, so it can be included along with "Tux Paint", if you're making an official (or test) release. The build process will look for it in a directory named "tuxpaint-config" (with no version number, e.g., "tuxpaint-config-X.Y.Z"). See "Tux Paint Config."'s INSTALL.txt documentation for details.

All the files needed for starting Tux Paint (and Tux Paint Config.) are collected in the directory for binary distribution "bdist" directory under "win32". You can start them by double-clicking their executable (.exe) files in the "bdist" directory.

- +
-
- -

Building the Tux Paint Windows Installer:

-
+
+
+

+ Building the Tux Paint Windows Installer

+

Inno Setup is used to build executable installer for Tux Paint. Therefore you have to install it in the first place.

@@ -509,14 +584,17 @@ Before building an installer, edit the "tuxpaint.iss" file and enable one of the lines starting with "#define BuildTarget=", depending on the architecture of the installer you want to create.

Then, you can easily build an executable installer by right-clicking on the "tuxpaint.iss" icon in the "win32" directory and selecting "Compile" on the list. It will run for a while, and eventually you will find a "tuxpaint-X.Y.Z-windows-<arch>-installer.exe" file in the same directory.

-
+
-
+
+
+

+ Running the Tux Paint Windows Installer

+
-

Running the Tux Paint Windows Installer:

-

- Faga dobre clic no executábel do instalador de Tux Paint (ficheiro .EXE) e siga as instrucións. + Faga dobre clic no executábel do instalador de Tux Paint (ficheiro .EXE) e siga as instrucións.

+

First, you will be asked to read the license. (It is the GNU General Public License (GPL), which is also available as "COPYING.txt".)

@@ -528,12 +606,14 @@

Neste punto, pode premer en «Instalar» para instalar Tux Paint.

-
+
-
+
+
+

+ Changing the Settings Using the Shortcut

+
-

Cambiar os axustes usando o acceso directo:

-

Para cambiar os axustes do programa, prema co botón dereito no atallo de TuxPaint e seleccione «Propiedades» (na parte inferior).

@@ -566,31 +646,38 @@

Cando teña rematado, prema en «Aceptar».

-
+
-
+
+
+

+ If Something Goes Wrong

+
-

Se algo vai mal:

-

Se ao facer dobre clic no atallo para executar Tux Paint, non ocorre nada, probabelmente sexa porque algunhas destas opcións da liña de ordes son incorrectas. Abra un explorador de ficheiros coma antes e busque un ficheiro chamado «stderr.txt» no cartafol TuxPaint.

Conterá unha descrición do que estaba mal. Normalmente só se debe a maiúsculas e minúsculas incorrectas (maiúsculas «Z» no canto de minúsculas «z») ou a falta (ou exceso) de «-» (guións).

-
- +
+ -
+
+
+

+ + Linux/Unix +

+
-

- - Usuarios de Linux/Unix -

-
-

Compilación:

-
-

- Nota: Tux Paint non usa autoconf/automake, polo que non hai ningún script «./configure» para executar. Non obstante, a compilación debería ser directa, supoñendo que todo o que precisa Tux Paint está instalado.

+
+
+

+ Compilación:

+
+ +

+ 💡 Note: Tux Paint does not use autoconf/automake, so there is no "./configure" script to run. Compiling should be straight-forward though, assuming everything Tux Paint needs is installed.

Para compilar o programa dende o código fonte, simplemente execute a seguinte orde dende un indicador do sistema (p. ex.: «$»):

@@ -600,13 +687,14 @@ $ make
-
+
-
+
+
+

+ Desactivar a compatibilidade de «SVG» (e, polo tanto, as dependencias de «Cairo, libSVG, e svg-cairo»:

+
-

- Desactivar a compatibilidade de «SVG» (e, polo tanto, as dependencias de «Cairo, libSVG, e svg-cairo»:

-

Para desactivar a compatibilidade con SVG (por exemplo, se o seu sistema non é compatíbel coa biblioteca de Cairo ou outras dependencias relacionadas co SVG), pode executar «make» engadindo «SVG_LIB= SVG_CFLAGS= NOSVGFLAG=NOSVG»:

@@ -614,54 +702,64 @@ $ make SVG_LIB= SVG_CFLAGS=
-
+
-
+
+
+

+ Desactivar a compatibilidade de «Pango» (e, polo tanto, as dependencias de «Pango, Cairo, etc.»:

+
-

- Desactivar a compatibilidade de «Pango» (e, polo tanto, as dependencias de «Pango, Cairo, etc.»:

-
-

- Antes da versión 0.9.18, Tux Paint utilizaba a biblioteca libSDL_ttf para renderizar texto usando tipos de letra TrueType. Dende o 0.9.18 úsase libSDL_Pango, xa que ten unha mellor compatibilidade coa internacionalización. Non obstante, se quere desactivar o uso de SDL_Pango, pode facelo executando «make» engadindo «SDL_PANGO_LIB=»:

+

+ 📜 Antes da versión 0.9.18, Tux Paint utilizaba a biblioteca libSDL_ttf para renderizar texto usando tipos de letra TrueType. Dende o 0.9.18 úsase libSDL_Pango, xa que ten unha mellor compatibilidade coa internacionalización. Non obstante, se quere desactivar o uso de SDL_Pango, pode facelo executando «make» engadindo «SDL_PANGO_LIB=»:

$ make SDL_PANGO_LIB=
-
+
-
+
+
+

+ Disabling Sound at Compile-time

+
-

Desactivación do son en tempo de compilación:

-
- Se non te unha tarxeta de son ou prefire construír o programa sen asistencia de son (e polo tanto sen a dependencia SDL_mixer), pode executar «make» con «SDL_MIXER_LIB=» engadido:

+

+ Se non te unha tarxeta de son ou prefire construír o programa sen asistencia de son (e polo tanto sen a dependencia SDL_mixer), pode executar «make» con «SDL_MIXER_LIB=» engadido:

$ make SDL_MIXER_LIB=
-
+
-
+
+
+

+ Other options

+
-

Outras opcións:

-

Outras opcións (p. ex.: rutas de instalación) poden ser anuladas; véxaas en «Makefile» para máis detalles.

-
+
-
+
+
+

+ If you get errors

+
-

Se se producen erros:

-

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 «-dev» ou «-devel», se non, non poderá compilar Tux Paint (e outros programas) dende o código fonte.

-
+
-
+
+
+

+ Installng

+
-

Instalar:

-

Supoñendo que non se produciron erros graves, agora pode instalar o programa para que os usuarios do sistema poidan executalo. De xeito predeterminado, isto debe facelo o usuario «root» («superusuario»). Cambie a «root» escribindo a orde:

@@ -698,11 +796,15 @@
-

- Nota: De xeito predeterminado, «tuxpaint», o programa executábel, colócase en «/usr/local/bin/». Os ficheiros de datos (imaxes, sons, etc.) colócanse en «/usr/local/share/tuxpaint/».

+

+ 💡 Note: By default, "tuxpaint", the executable program, is placed in "/usr/local/bin/". The data files (images, sounds, etc.) are placed in "/usr/local/share/tuxpaint/".

+ +
+
+

+ Cambiar onde van as cousas

+
-
Cambiar onde van as cousas
-

Pode cambiar onde irán as cousas axustando as variábeis de «Makefile» na liña de ordes. «DESTDIR» úsase para colocar a saída nunha área de espera para a creación de paquetes. «PREFIX» é a base de onde van todos os demais ficheiros e, de xeito predeterminado, está estabelecido en «/usr/local».

@@ -737,30 +839,34 @@ Onde irán os ficheiros de tradución para Tux Paint e onde os buscará Tux Paint. (Estabelécese en «$(PREFIX)/share/locale/») (A localización final dun ficheiro de tradución estará no directorio da configuración local (por exemplo, «es» para o español), dentro do subdirectorio «LC_MESSAGES»). -

- Nota: Esta lista non está actualizada. Consulte «Makefile» e «Makefile-i18n» para ver unha lista completa.

-
- - +

+ 💡 Note: This list is out of date. See "Makefile" and "Makefile-i18n" for a complete list.

+
+
+ -
+
+
+

+ + macOS +

+

+ + 20 de Xaneiro de 2022 Mark Kim <markuskimius@gmail.com> + +

+
-

- - Usuarios de macOS -

-

- - 20 de Xaneiro de 2022 Mark 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

-
+
+
+

+ 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:

@@ -792,8 +898,13 @@
* Not available from MacPorts as of this writing, see below.

-
libimagequant
-
+
+
+

+ 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.

@@ -805,17 +916,18 @@

- -
+

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

+
-

How to Build

-

Simply, run:

@@ -827,12 +939,14 @@

Additional steps may be required when building for the Apple Silicon. See "Building for Apple Silicon" below.

-
+
-
+
+
+

+ Known Issues

+
-

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.
    @@ -841,12 +955,14 @@
    Alternatively, Tux Paint and all of its library dependencies may be compiled with appropriate options to be runnable on older versions of macOS. These options are already set on Tux Paint, so only its dependencies (from MacPorts) need to be recompiled. See "Recompiling MacPorts" below for the instructions.
-
+
-
+
+
+

+ Old Versions 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

@@ -870,11 +986,14 @@

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.

+
- +
+
+

+ Recompiling MacPorts

+
-

Recompiling MacPorts

-

To recompile MacPorts to be usable on older versions of macOS, set the following options in /opt/local/etc/macports/macports.conf:

@@ -897,18 +1016,21 @@

As of this writing, all libraries Tux Paint requires from MacPorts can be recompiled in this manner to run on macOS 10.10 Yosemite and later on Intel CPUs, and macOS 11.0 Big Sur and later on Apple Silicon. Unfortunately, although MacPorts has the option to enable the building of universal libraries, several libraries Tux Paint require cannot be built as universal libraries so they can only be built to run natively on the hardware on which they were built. See "Building a Universal Binary" below for instructions on how to build Tux Paint as a Universal Binary.

-
+
+ +
+
+

+ Building for Apple Silicon

+
-

Building for Apple Silicon

-

macOS for Applie Silicon requires all native Apple Silicon applications be signed, even if it is signed "ad-hoc" (anonymously). Because of this, compilers that produce native Apple Silicon applications sign all produced binaries and libraries as a part of the compilation process.* However, the Tux Paint compilation process modifies the libraries to be modular (using install_name_tool) so they can be added into the application bundle, which has the unfortunate side effect of breaking the signature. This can be addressed by signing the application bundle ad-hoc (example below) or using your own Apple Developer Identity if you have one. The DMG file, if needed, must be created after signing the App Bundle so the DMG file is created with signed App Bundle:

$ codesign -s - TuxPaint.app
$ make TuxPaint.dmg
- * For more information on the code signing requirements on the Apple Silicon, see https://developer.apple.com/documentation/macos-release-notes/macos-big-sur-11_0_1-universal-apps-release-notes#:~:text=New%20in%20macOS,pass%20through%20Gatekeeper. -

+ * For more information on the code signing requirements on the Apple Silicon, see https://developer.apple.com/documentation/macos-release-notes/macos-big-sur-11_0_1-universal-apps-release-notes#:~:text=New%20in%20macOS,pass%20through%20Gatekeeper.

If you get an error that the application bundle is already signed, remove it before signing::

$ codesign --remove-signature TuxPaint.app @@ -916,10 +1038,14 @@

If you plan to combine the Apple Silicon bundle with the Intel CPU bundle to produce the Universal bundle, the code signing must be done after they are combined. See "Building a Universal Binary" below.

-
+
+ +
+
+

+ Building a Universal Binary

+
-

Building a Universal Binary

-

To build Tux Paint as a Universal Binary, compile Tux Paint for the Intel CPU and the Apple Silicon separately first. Then rename the app bundle for the Intel CPU to TuxPaint-x86_64.app, and the bundle for the Apple Silicon to TuxPaint-arm64.app, copy the app bundle from the Intel machine to the Apple Silicon machine, then use the provided build-universal.sh script to combine the two application bundles as below. The produced bundle must be signed (see "Building for Apple Silicon" above for more details). The DMG file, if required, must be built after the signing:

@@ -929,71 +1055,87 @@

-
+
- + - + -
+
+
+

+ + Debugging +

+
-

- - Debugging -

-
- Debugging output — to "STDOUT" on Linux and Unix, to a "stdout.txt" file on Windows, and to the file "/tmp/tuxpaint.log" on macOS — can be enabled by setting "DEBUG" (and, if verbose logging is wanted, "VERBOSE") #defines in "src/debug.h" and (re)compiling Tux Paint.
+

+ ⚙ Debugging output — to "STDOUT" on Linux and Unix, to a "stdout.txt" file on Windows, and to the file "/tmp/tuxpaint.log" on macOS — can be enabled by setting "DEBUG" (and, if verbose logging is wanted, "VERBOSE") #defines in "src/debug.h" and (re)compiling Tux Paint.

+
-
+
+
+

+ + Uninstalling Tux Paint +

+
+ +
+
+

+ + Windows +

+
+ +
+
+

+ Uso do desinstalador

+
-

- - Uninstalling Tux Paint

- -
-

- - Windows -

-
-

Uso do desinstalador

-

Se instalou os atallos do menú Inicio (o predeterminado), vaia ao cartafol TuxPaint e seleccione «Desinstalar». Amosarase unha caixa que confirmará que está a piques de desinstalar Tux Paint e, se está seguro de que quere eliminar permanentemente Tux Paint, prema no botón «Desinstalar».

Cando remate, prema no botón pechar.

-
+
+ +
+
+

+ Usar o Panel de control

+
-

Usar o Panel de control

-

Tamén é posíbel usar a entrada «TuxPaint (só eliminar)« na sección Engadir/Eliminar programas do Panel de control.

-
- +
+
-
+
+
+

+ + macOS +

+
-

- - macOS -

- -

Delete "TuxPaint.app" from the "Applications" folder. Data files, including the configuration files, stamps, and saved pictures, may be found in "Library/Application Support/TuxPaint" (all users) and "/Users/USERNAME/Library/Application Support/TuxPaint" (individual users).

-
+
-
+
+
+

+ + Linux +

+
-

- - Linux -

-

Within the Tux Paint source directory (where you compiled Tux Paint), you can use the "make uninstall" target to uninstall Tux Paint. By default, this must be done by the "root" user ('superuser'), but if you installed Tux Paint somewhere else (e.g., using a "PREFIX=..." setting to "make" and "make install"), you may not, and will want to provide those same settings here. (See the installation instructions above for further information.)

-
-
+
+
diff --git a/docs/gl_ES.UTF-8/html/OPTIONS.html b/docs/gl_ES.UTF-8/html/OPTIONS.html index 11e5c273c..384046d30 100644 --- a/docs/gl_ES.UTF-8/html/OPTIONS.html +++ b/docs/gl_ES.UTF-8/html/OPTIONS.html @@ -21,15 +21,17 @@ } div.keeptogether { page-break-inside: avoid; } section h1 { font-size: 2em; } - h1, h2, h3, h4 { font-family: sans; } + h1, h2, h3, h4, h5 { font-family: sans; } h1 { color: #800; page-break-before: always; break-before: always; } h2 { color: #440; page-break-after: avoid; break-after: avoid; } h3 { color: #080; page-break-after: avoid; break-after: avoid; } h4 { color: #008; page-break-after: avoid; break-after: avoid; } + h5 { color: #808; page-break-after: avoid; break-after: avoid; } h1 + p { page-break-inside: avoid; } h2 + p { page-break-inside: avoid; } h3 + p { page-break-inside: avoid; } h4 + p { page-break-inside: avoid; } + h5 + p { page-break-inside: avoid; } dt { font-size: large; color: #404; diff --git a/docs/gl_ES.UTF-8/html/PNG.html b/docs/gl_ES.UTF-8/html/PNG.html index 2835acd3c..0a6779dc7 100644 --- a/docs/gl_ES.UTF-8/html/PNG.html +++ b/docs/gl_ES.UTF-8/html/PNG.html @@ -21,15 +21,17 @@ } div.keeptogether { page-break-inside: avoid; } section h1 { font-size: 2em; } - h1, h2, h3, h4 { font-family: sans; } + h1, h2, h3, h4, h5 { font-family: sans; } h1 { color: #800; page-break-before: always; break-before: always; } h2 { color: #440; page-break-after: avoid; break-after: avoid; } h3 { color: #080; page-break-after: avoid; break-after: avoid; } h4 { color: #008; page-break-after: avoid; break-after: avoid; } + h5 { color: #808; page-break-after: avoid; break-after: avoid; } h1 + p { page-break-inside: avoid; } h2 + p { page-break-inside: avoid; } h3 + p { page-break-inside: avoid; } h4 + p { page-break-inside: avoid; } + h5 + p { page-break-inside: avoid; } dt { font-size: large; color: #404; diff --git a/docs/gl_ES.UTF-8/html/README.html b/docs/gl_ES.UTF-8/html/README.html index 72b3b52dd..239c0681a 100644 --- a/docs/gl_ES.UTF-8/html/README.html +++ b/docs/gl_ES.UTF-8/html/README.html @@ -21,15 +21,17 @@ } div.keeptogether { page-break-inside: avoid; } section h1 { font-size: 2em; } - h1, h2, h3, h4 { font-family: sans; } + h1, h2, h3, h4, h5 { font-family: sans; } h1 { color: #800; page-break-before: always; break-before: always; } h2 { color: #440; page-break-after: avoid; break-after: avoid; } h3 { color: #080; page-break-after: avoid; break-after: avoid; } h4 { color: #008; page-break-after: avoid; break-after: avoid; } + h5 { color: #808; page-break-after: avoid; break-after: avoid; } h1 + p { page-break-inside: avoid; } h2 + p { page-break-inside: avoid; } h3 + p { page-break-inside: avoid; } h4 + p { page-break-inside: avoid; } + h5 + p { page-break-inside: avoid; } dt { font-size: large; color: #404; diff --git a/docs/gl_ES.UTF-8/html/SIGNALS.html b/docs/gl_ES.UTF-8/html/SIGNALS.html index 2e4fcbc22..3a2f1aa1d 100644 --- a/docs/gl_ES.UTF-8/html/SIGNALS.html +++ b/docs/gl_ES.UTF-8/html/SIGNALS.html @@ -21,15 +21,17 @@ } div.keeptogether { page-break-inside: avoid; } section h1 { font-size: 2em; } - h1, h2, h3, h4 { font-family: sans; } + h1, h2, h3, h4, h5 { font-family: sans; } h1 { color: #800; page-break-before: always; break-before: always; } h2 { color: #440; page-break-after: avoid; break-after: avoid; } h3 { color: #080; page-break-after: avoid; break-after: avoid; } h4 { color: #008; page-break-after: avoid; break-after: avoid; } + h5 { color: #808; page-break-after: avoid; break-after: avoid; } h1 + p { page-break-inside: avoid; } h2 + p { page-break-inside: avoid; } h3 + p { page-break-inside: avoid; } h4 + p { page-break-inside: avoid; } + h5 + p { page-break-inside: avoid; } dt { font-size: large; color: #404; diff --git a/docs/gl_ES.UTF-8/html/SVG.html b/docs/gl_ES.UTF-8/html/SVG.html index a6b378cd4..63a9ceda0 100644 --- a/docs/gl_ES.UTF-8/html/SVG.html +++ b/docs/gl_ES.UTF-8/html/SVG.html @@ -21,15 +21,17 @@ } div.keeptogether { page-break-inside: avoid; } section h1 { font-size: 2em; } - h1, h2, h3, h4 { font-family: sans; } + h1, h2, h3, h4, h5 { font-family: sans; } h1 { color: #800; page-break-before: always; break-before: always; } h2 { color: #440; page-break-after: avoid; break-after: avoid; } h3 { color: #080; page-break-after: avoid; break-after: avoid; } h4 { color: #008; page-break-after: avoid; break-after: avoid; } + h5 { color: #808; page-break-after: avoid; break-after: avoid; } h1 + p { page-break-inside: avoid; } h2 + p { page-break-inside: avoid; } h3 + p { page-break-inside: avoid; } h4 + p { page-break-inside: avoid; } + h5 + p { page-break-inside: avoid; } dt { font-size: large; color: #404; diff --git a/docs/ja_JP.UTF-8/INSTALL.txt b/docs/ja_JP.UTF-8/INSTALL.txt index 8fbf8beea..c9828027d 100644 --- a/docs/ja_JP.UTF-8/INSTALL.txt +++ b/docs/ja_JP.UTF-8/INSTALL.txt @@ -5,853 +5,783 @@ Copyright © 2002-2022 by various contributors; see AUTHORS.txt. https://tuxpaint.org/ - 2022年1月20日 + 2022年3月31日 - ---------------------------------------------------------------------- + +----------------------------------------------------+ + |目次 | + |----------------------------------------------------| + | * Requirements | + | * Simple DirectMedia Layer library (libSDL) | + | * Other Libraries | + | * Compiling and Installation | + | * Windows | + | * Linux/Unix | + | * macOS | + | * Debugging | + | * Uninstalling Tux Paint | + | * Windows | + | * macOS | + | * Linux | + +----------------------------------------------------+ - +----------------------------------------------------+ - |目次 | - |----------------------------------------------------| - | * Requirements | - | * Simple DirectMedia Layer library (libSDL) | - | * Other Libraries | - | * Compiling and Installation | - | * Windows のユーザー | - | * Linux または Unix のユーザー | - | * macOS のユーザー | - | * Debugging | - | * Uninstalling Tux Paint | - | * Windows | - | * macOS | - | * Linux | - +----------------------------------------------------+ + Requirements - ---------------------------------------------------------------------- +Simple DirectMedia Layer library (libSDL) -Requirements + Tux Paint requires the Simple DirectMedia Layer Library (libSDL), an Open + Source multimedia programming library available under the GNU Lesser + General Public License (LGPL). - Simple DirectMedia Layer library (libSDL) + Along with libSDL, Tux Paint depends on a number of other SDL 'helper' + libraries: SDL_Image (for graphics files), SDL_gfx (for some graphical + functions, like rotation), SDL_TTF and (optionally) SDL_Pango (for True + Type Font support) and, optionally, SDL_Mixer (for sound effects). - Tux Paint requires the Simple DirectMedia Layer Library (libSDL), an - Open Source multimedia programming library available under the GNU - Lesser General Public License (LGPL). + Linux/Unix - Along with libSDL, Tux Paint depends on a number of other SDL 'helper' - libraries: SDL_Image (for graphics files), SDL_gfx (for some graphical - functions, like rotation), SDL_TTF and (optionally) SDL_Pango (for - True Type Font support) and, optionally, SDL_Mixer (for sound - effects). + The SDL libraries are available as source-code, or as RPM or + Debian packages for various distributions of Linux. They can be + downloaded from: - Linux/Unix Users: + * libSDL: http://www.libsdl.org/ + * SDL_Image: http://www.libsdl.org/projects/SDL_image/ + * SDL_gfx: + https://www.ferzkopp.net/wordpress/2016/01/02/sdl_gfx-sdl2_gfx/ + (https://sourceforge.net/projects/sdlgfx/) + * SDL_TTF: http://www.libsdl.org/projects/SDL_ttf/ + * SDL_Pango: http://sourceforge.net/projects/sdlpango/ + (optional) + * SDL_Mixer: http://www.libsdl.org/projects/SDL_mixer/ + (optional) - The SDL libraries are available as source-code, or as RPM or Debian - packages for various distributions of Linux. They can be downloaded - from: + They are also typically available along with your Linux + distribution (e.g. on an installation media, or available via + package maintainance software like Debian's "apt"). - * libSDL: http://www.libsdl.org/ - * SDL_Image: http://www.libsdl.org/projects/SDL_image/ - * SDL_gfx: - https://www.ferzkopp.net/wordpress/2016/01/02/sdl_gfx-sdl2_gfx/ - (https://sourceforge.net/projects/sdlgfx/) - * SDL_TTF: http://www.libsdl.org/projects/SDL_ttf/ - * SDL_Pango: http://sourceforge.net/projects/sdlpango/ (optional) - * SDL_Mixer: http://www.libsdl.org/projects/SDL_mixer/ (optional) - - They are also typically available along with your Linux distribution - (e.g. on an installation media, or available via package - maintainance software like Debian's "apt"). - - Note: When installing libraries from packages, be sure to ALSO - install the development versions of the packages. (For example, - install both "SDL-1.2.4.rpm" and "SDL-1.2.4-devel.rpm".) + 💡 Note: When installing libraries from packages, be sure to ALSO + install the development versions of the packages. (For example, + install both "SDL-1.2.4.rpm" and "SDL-1.2.4-devel.rpm".) Other Libraries - Tux Paint also takes advantage of a number of other free, LGPL'd - libraries. Under Linux, just like SDL, they should either already be - installed, or are readily available for installation as part of your - Linux distribution. + Tux Paint also takes advantage of a number of other free, LGPL'd + libraries. Under Linux, just like SDL, they should either already be + installed, or are readily available for installation as part of your Linux + distribution. - libPNG + libPNG - Tux Paint uses PNG (Portable Network Graphics) format for its data - files. SDL_image will require libPNG be installed. + Tux Paint uses PNG (Portable Network Graphics) format for its data + files. SDL_image will require libPNG be installed. - http://www.libpng.org/pub/png/libpng.html + http://www.libpng.org/pub/png/libpng.html - gettext + gettext - Tux Paint uses your system's locale settings along with the - "gettext" library to support various languages (e.g., Spanish). - You'll need the gettext library installed. + Tux Paint uses your system's locale settings along with the + "gettext" library to support various languages (e.g., Spanish). + You'll need the gettext library installed. - http://www.gnu.org/software/gettext/ + http://www.gnu.org/software/gettext/ - libpaper (Linux/Unix only) + libpaper (Linux/Unix only) - As of Tux Paint 0.9.17, Tux Paint can determine your system's - default paper size (e.g., A4 or Letter), or can be told to use a - particular paper size, thanks to "libpaper". + As of Tux Paint 0.9.17, Tux Paint can determine your system's + default paper size (e.g., A4 or Letter), or can be told to use a + particular paper size, thanks to "libpaper". - https://github.com/naota/libpaper + https://github.com/naota/libpaper - FriBiDi + FriBiDi - Tux Paint's "Text" and also "Label" tools support bidirectional - languages, thanks to the "FriBiDi" library. + Tux Paint's "Text" and also "Label" tools support bidirectional + languages, thanks to the "FriBiDi" library. - http://fribidi.org/ + http://fribidi.org/ - SVG graphics support + SVG graphics support - As of Tux Paint 0.9.17, Tux Paint can load SVG (Scalable Vector - Graphics) images as stamps. Two sets of libraries are supported, and - SVG support can be completely disabled (via "make SVG_LIB:=") + As of Tux Paint 0.9.17, Tux Paint can load SVG (Scalable Vector + Graphics) images as stamps. Two sets of libraries are supported, + and SVG support can be completely disabled (via "make SVG_LIB:=") - librsvg-2 & libCairo2 (newer libraries) + librsvg-2 & libCairo2 (newer libraries) + * libRSVG 2: http://librsvg.sourceforge.net/ + * Cairo 2: http://www.cairographics.org/ + * These also depend on the following: + * GdkPixbuf & GLib: http://www.gtk.org/ + * Pango: http://www.pango.org/ - * libRSVG 2: http://librsvg.sourceforge.net/ - * Cairo 2: http://www.cairographics.org/ - * These also depend on the following: - * GdkPixbuf & GLib: http://www.gtk.org/ - * Pango: http://www.pango.org/ + Older SVG libraries + * libcairo1, libsvg1, & libsvg-cairo1: + http://www.cairographics.org/ + * These also depend on the following: + * libxml2: + https://gitlab.gnome.org/GNOME/libxml2 - Older SVG libraries + Animated GIF Export feature - * libcairo1, libsvg1, & libsvg-cairo1: - http://www.cairographics.org/ - * These also depend on the following: - * libxml2: https://gitlab.gnome.org/GNOME/libxml2 + To support export of animated GIFs (slideshows), the + "libimagequant" library (from the "pngquant2" project) is + required. - Animated GIF Export feature + https://github.com/ImageOptim/libimagequant - To support export of animated GIFs (slideshows), the "libimagequant" - library (from the "pngquant2" project) is required. + NetPBM Tools (optional) No longer used, by default - https://github.com/ImageOptim/libimagequant + 📜 Under Linux and Unix, earlier versions of Tux Paint used the + NetPBM tools to assist with printing. (A PNG is generated by Tux + Paint, and converted into a PostScript using the 'pngtopnm' and + 'pnmtops' NetPBM command-line tools.) - NetPBM Tools (optional) No longer used, by default + http://netpbm.sourceforge.net/ - Under Linux and Unix, earlier versions of Tux Paint used the NetPBM - tools to assist with printing. (A PNG is generated by Tux Paint, and - converted into a PostScript using the 'pngtopnm' and 'pnmtops' - NetPBM command-line tools.) + Compiling and Installation - http://netpbm.sourceforge.net/ + Tux Paint is released under the GNU General Public License (GPL) (see + "COPYING.txt" for details), and therefore the 'source code' to the program + is available freely. - ---------------------------------------------------------------------- +Windows -Compiling and Installation + 2021年11月 3日 Shin-ichi TOYAMA dolphin6k@wmail.plala.or.jp + - Tux Paint is released under the GNU General Public License (GPL) (see - "COPYING.txt" for details), and therefore the 'source code' to the - program is available freely. + Compiling Set-Up - Windows のユーザー + As of February 2005 (starting with Tux Paint 0.9.15), the "Makefile" + includes support for building on a Windows system using MinGW/MSYS + (https://sourceforge.net/projects/msys2/). - 2021年11月 3日 Shin-ichi TOYAMA dolphin6k@wmail.plala.or.jp - + Many tools and libraries are required to build Tux Paint. The package + management system "pacman" helps you install them automatically solving + complicated dependencies. - Compiling Set-Up + Download the latest MSYS2 environment from + https://sourceforge.net/projects/msys2/files/Base/ and install it where + you'd like (the default is "C:\msys64") - As of February 2005 (starting with Tux Paint 0.9.15), the "Makefile" - includes support for building on a Windows system using MinGW/MSYS - (https://sourceforge.net/projects/msys2/). + Open the MSYS2 shell from the "Start Menu" -> "MSYS2 64bit" -> "MSYS2 + MSYS" and execute following command (press [Enter] or [Return] to accept + the defaults for all questions): - Many tools and libraries are required to build Tux Paint. The - package management system "pacman" helps you install them - automatically solving complicated dependencies. + pacman -Syu - Download the latest MSYS2 environment from - https://sourceforge.net/projects/msys2/files/Base/ and install it - where you'd like (the default is "C:\msys64") + This will update core system and the window will close automatically. + Repeat the steps above one more time to finish the remaining update + process. - Open the MSYS2 shell from the "Start Menu" -> "MSYS2 64bit" -> - "MSYS2 MSYS" and execute following command (press [Enter] or - [Return] to accept the defaults for all questions): + Within the MSYS2 shell, run the following command to install basic + development tools: - pacman -Syu + pacman -S base-devel msys2-devel git - This will update core system and the window will close - automatically. Repeat the steps above one more time to finish the - remaining update process. - - Within the MSYS2 shell, run the following command to install basic - development tools: - - pacman -S base-devel msys2-devel git - - Proceed to the next "MinGW 64bit (x86_64) toolchains" section, or skip - to the "MinGW 32bit (i686) toolchains" section if you need only a - 32bit build environment. + Proceed to the next "MinGW 64bit (x86_64) toolchains" section, or skip 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 - 64bit development tools: + Within the MSYS2 shell, run the following command to install basic 64bit + development tools: - pacman -S mingw-w64-x86_64-toolchain + pacman -S mingw-w64-x86_64-toolchain 64bit (x86_64) dependency libraries for Tux Paint - You can install tools and libraries required for compiling Tux Paint - on MSYS2/MINGW using "pacman" except for SDL_Pango. + You can install tools and libraries required for compiling Tux Paint on + MSYS2/MINGW using "pacman" except for SDL_Pango. - "ntldd" is a small tool which examine windows executable files to - list Dynamic Link Library (.dll) files they depends on. Tux Paint's - packaging process for binary distribution uses it to find required - .dll files. + "ntldd" is a small tool which examine windows executable files to list + Dynamic Link Library (.dll) files they depends on. Tux Paint's packaging + process for binary distribution uses it to find required .dll files. - FLTK is a cross-platform GUI toolkit used by "Tux Paint Config.". - You can skip installing it if you are only building "Tux Paint". + FLTK is a cross-platform GUI toolkit used by "Tux Paint Config.". You can + skip installing it if you are only building "Tux Paint". - $ pacman -S mingw-w64-x86_64-SDL_{image,mixer,ttf,gfx} - $ pacman -S mingw-w64-x86_64-librsvg - $ pacman -S mingw-w64-x86_64-fribidi - $ pacman -S mingw-w64-x86_64-libimagequant - $ pacman -S mingw-w64-x86_64-fltk - $ pacman -S mingw-w64-x86_64-ntldd-git + $ pacman -S mingw-w64-x86_64-SDL_{image,mixer,ttf,gfx} + $ pacman -S mingw-w64-x86_64-librsvg + $ pacman -S mingw-w64-x86_64-fribidi + $ pacman -S mingw-w64-x86_64-libimagequant + $ pacman -S mingw-w64-x86_64-fltk + $ pacman -S mingw-w64-x86_64-ntldd-git - Note: Close the shell before proceeding to the remaining process. + 💡 Note: Close the shell before proceeding to the remaining process. Install SDL_Pango on the 64bit environment - SDL_Pango should be installed manually. + SDL_Pango should be installed manually. - This time, use the MinGW "64bit" shell. Open the shell from the - "Start Menu" -> "MSYS2 64bit" -> "MSYS2 MinGW 64-bit" + This time, use the MinGW "64bit" shell. Open the shell from the "Start + Menu" -> "MSYS2 64bit" -> "MSYS2 MinGW 64-bit" SDL_Pango - At first, you have to prepare source tar-ball and a required patch - in the same directory. + At first, you have to prepare source tar-ball and a required patch in the + same directory. + * Download source tar-ball of SDL_Pango-0.1.2 from SDL_Pango's page on + Sourceforge.net. + * Download a patch file from John Popplewell's "Tux Paint - MinGW/MSYS + build instructions" webpage. (This adds some extra (required) + functionality to SDL_Pango.) - * Download source tar-ball of SDL_Pango-0.1.2 from SDL_Pango's - page on Sourceforge.net. - * Download a patch file from John Popplewell's "Tux Paint - - MinGW/MSYS build instructions" webpage. (This adds some extra - (required) functionality to SDL_Pango.) + Build and install SDL_Pango as follows. - Build and install SDL_Pango as follows. + $ tar zxvf SDL_Pango-0.1.2.tar.gz + $ cd SDL_Pango-0.1.2/ + $ patch -p0 < ../SDL_Pango-configure-extra-api.patch + $ ./configure --prefix=/mingw64 && make && make install - $ tar zxvf SDL_Pango-0.1.2.tar.gz - $ cd SDL_Pango-0.1.2/ - $ patch -p0 < ../SDL_Pango-configure-extra-api.patch - $ ./configure --prefix=/mingw64 && make && make install - - Proceed to the next "MinGW 32bit (i686) toolchains" section, or skip - to the "ImageMagick" section if you need only a 64bit build - environment. + Proceed to the next "MinGW 32bit (i686) toolchains" section, or skip 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 - 32bit development tools: + Within the MSYS2 shell, run the following command to install basic 32bit + development tools: - pacman -S mingw-w64-i686-toolchain + pacman -S mingw-w64-i686-toolchain 32bit (i686) dependency libraries for Tux Paint - You can install tools and libraries required for compiling Tux Paint - on MSYS2/MINGW using "pacman" except for SDL_Pango. + You can install tools and libraries required for compiling Tux Paint on + MSYS2/MINGW using "pacman" except for SDL_Pango. - "ntldd" is a small tool which examine windows executable files to - list Dynamic Link Library (.dll) files they depends on. Tux Paint's - packaging process for binary distribution uses it to find required - .dll files. + "ntldd" is a small tool which examine windows executable files to list + Dynamic Link Library (.dll) files they depends on. Tux Paint's packaging + process for binary distribution uses it to find required .dll files. - FLTK is a cross-platform GUI toolkit used by "Tux Paint Config.". - You can skip installing it if you are only building "Tux Paint". + FLTK is a cross-platform GUI toolkit used by "Tux Paint Config.". You can + skip installing it if you are only building "Tux Paint". - $ pacman -S mingw-w64-i686-SDL_{image,mixer,ttf,gfx} - $ pacman -S mingw-w64-i686-librsvg - $ pacman -S mingw-w64-i686-fribidi - $ pacman -S mingw-w64-i686-libimagequant - $ pacman -S mingw-w64-i686-fltk - $ pacman -S mingw-w64-i686-ntldd-git + $ pacman -S mingw-w64-i686-SDL_{image,mixer,ttf,gfx} + $ pacman -S mingw-w64-i686-librsvg + $ pacman -S mingw-w64-i686-fribidi + $ pacman -S mingw-w64-i686-libimagequant + $ pacman -S mingw-w64-i686-fltk + $ pacman -S mingw-w64-i686-ntldd-git - Note: Close the shell before proceeding to the remaining process. + 💡 Note: Close the shell before proceeding to the remaining process. Install SDL_Pango on the 32bit environment - SDL_Pango should be installed manually. + SDL_Pango should be installed manually. - This time, use the MinGW "32bit" shell. Open the shell from the - "Start Menu" -> "MSYS2 64bit" -> "MSYS2 MinGW 32-bit" + This time, use the MinGW "32bit" shell. Open the shell from the "Start + Menu" -> "MSYS2 64bit" -> "MSYS2 MinGW 32-bit" SDL_Pango - At first, you have to prepare source tar-ball and a required patch - in the same directory. + At first, you have to prepare source tar-ball and a required patch in the + same directory. + * Download source tar-ball of SDL_Pango-0.1.2 from SDL_Pango's page on + Sourceforge.net. + * Download a patch file from John Popplewell's "Tux Paint - MinGW/MSYS + build instructions" webpage. (This adds some extra (required) + functionality to SDL_Pango.) - * Download source tar-ball of SDL_Pango-0.1.2 from SDL_Pango's - page on Sourceforge.net. - * Download a patch file from John Popplewell's "Tux Paint - - MinGW/MSYS build instructions" webpage. (This adds some extra - (required) functionality to SDL_Pango.) + Build and install SDL_Pango as follows. - Build and install SDL_Pango as follows. + $ tar zxvf SDL_Pango-0.1.2.tar.gz + $ cd SDL_Pango-0.1.2/ + $ patch -p0 < ../SDL_Pango-configure-extra-api.patch + $ ./configure --prefix=/mingw32 && make && make install - $ tar zxvf SDL_Pango-0.1.2.tar.gz - $ cd SDL_Pango-0.1.2/ - $ patch -p0 < ../SDL_Pango-configure-extra-api.patch - $ ./configure --prefix=/mingw32 && make && make install + ImageMagick - ------------------------------------------------------- + ImageMagick is a compilation of command line tools to create, edit, + compose, or convert bitmap images supporting quite a large number of image + formats. Tux Paint uses two functions ("convert" and "composite") in it to + generate thumbnails for startar images and templates during the build + process. - ImageMagick + Using official binary release available from "Windows Binary Release" is + recommended, due to the commands installed with "pacman" on MinGW/MSYS not + working as expected! - ImageMagick is a compilation of command line tools to create, edit, - compose, or convert bitmap images supporting quite a large number of - image formats. Tux Paint uses two functions ("convert" and - "composite") in it to generate thumbnails for startar images and - templates during the build process. + Do not forget to enable "Install legacy utilities (e.g. convert)" while + installing it, because Tux Paint's build process uses them. - Using official binary release available from "Windows Binary - Release" is recommended, due to the commands installed with "pacman" - on MinGW/MSYS not working as expected! + Add the path to the directory in which ImageMagick is installed at the top + of your "PATH" environment variable. For example: - Do not forget to enable "Install legacy utilities (e.g. convert)" - while installing it, because Tux Paint's build process uses them. + $ export PATH=/c/Program\ Files/ImageMagick-7.0.10-Q16-HDRI:$PATH - Add the path to the directory in which ImageMagick is installed at - the top of your "PATH" environment variable. For example: + You can make this permanent by adding the above to your the BASH shell + configuration file, "~/.bash_profile". - $ export PATH=/c/Program\ Files/ImageMagick-7.0.10-Q16-HDRI:$PATH + Tux Paint - You can make this permanent by adding the above to your the BASH - shell configuration file, "~/.bash_profile". + You can compile 64bit binaries using MSYS2 64bit shell, and 32bit binaries + using MSYS2 32bit shell, respectively. - ------------------------------------------------------- + * Select "MSYS2 64bit" -> "MSYS2 MinGW 64-bit" from the "Start Menu" to + open the 64bit shell. + * Select "MSYS2 64bit" -> "MSYS2 MinGW 32-bit" from the "Start Menu" to + open the 32bit shell. - Tux Paint + Compile Tux Paint with the following command: - You can compile 64bit binaries using MSYS2 64bit shell, and 32bit - binaries using MSYS2 32bit shell, respectively. + $ make bdist-win32 - * Select "MSYS2 64bit" -> "MSYS2 MinGW 64-bit" from the "Start - Menu" to open the 64bit shell. - * Select "MSYS2 64bit" -> "MSYS2 MinGW 32-bit" from the "Start - Menu" to open the 32bit shell. + 💡 Note: At this point, you will want to build "Tux Paint Config." for + Windows, so it can be included along with "Tux Paint", if you're making an + official (or test) release. The build process will look for it in a + directory named "tuxpaint-config" (with no version number, e.g., + "tuxpaint-config-X.Y.Z"). See "Tux Paint Config."'s INSTALL.txt + documentation for details. - Compile Tux Paint with the following command: + All the files needed for starting Tux Paint (and Tux Paint Config.) are + collected in the directory for binary distribution "bdist" directory under + "win32". You can start them by double-clicking their executable (.exe) + files in the "bdist" directory. - $ make bdist-win32 + Building the Tux Paint Windows Installer - Note: At this point, you will want to build "Tux Paint Config." for - Windows, so it can be included along with "Tux Paint", if you're - making an official (or test) release. The build process will look - for it in a directory named "tuxpaint-config" (with no version - number, e.g., "tuxpaint-config-X.Y.Z"). See "Tux Paint Config."'s - INSTALL.txt documentation for details. + Inno Setup is used to build executable installer for Tux Paint. Therefore + you have to install it in the first place. - All the files needed for starting Tux Paint (and Tux Paint Config.) - are collected in the directory for binary distribution "bdist" - directory under "win32". You can start them by double-clicking their - executable (.exe) files in the "bdist" directory. + Inno Setup officially supports translations for only about 20 languages. + However, one of the great points of Tux Paint is it supports so many + languages. Therefore, the set up script "tuxpaint.iss" to build the + installer is written to use much more translations including unofficial + one which are available on "Inno Setup Translations". You have to download + translation files (.isl) required and put them in "Languages" directory + under the directory in which Inno Setup is installed. - ------------------------------------------------------- + Before building an installer, edit the "tuxpaint.iss" file and enable one + of the lines starting with "#define BuildTarget=", depending on the + architecture of the installer you want to create. - Building the Tux Paint Windows Installer: + Then, you can easily build an executable installer by right-clicking on + the "tuxpaint.iss" icon in the "win32" directory and selecting "Compile" + on the list. It will run for a while, and eventually you will find a + "tuxpaint-X.Y.Z-windows--installer.exe" file in the same directory. - Inno Setup is used to build executable installer for Tux Paint. - Therefore you have to install it in the first place. + Running the Tux Paint Windows Installer - Inno Setup officially supports translations for only about 20 - languages. However, one of the great points of Tux Paint is it - supports so many languages. Therefore, the set up script - "tuxpaint.iss" to build the installer is written to use much more - translations including unofficial one which are available on "Inno - Setup Translations". You have to download translation files (.isl) - required and put them in "Languages" directory under the directory - in which Inno Setup is installed. + Double-click the Tux Paint installer executable (.EXE file) and follow the + instructions. - Before building an installer, edit the "tuxpaint.iss" file and - enable one of the lines starting with "#define BuildTarget=", - depending on the architecture of the installer you want to create. + First, you will be asked to read the license. (It is the GNU General + Public License (GPL), which is also available as "COPYING.txt".) - Then, you can easily build an executable installer by right-clicking - on the "tuxpaint.iss" icon in the "win32" directory and selecting - "Compile" on the list. It will run for a while, and eventually you - will find a "tuxpaint-X.Y.Z-windows--installer.exe" file in - the same directory. + You will then be asked whether you want to install shortcuts to Tux Paint + in your Windows Start Menu and on your Windows Desktop. (Both options are + set by default.) - ------------------------------------------------------- + Then you will be asked where you wish to install Tux Paint. The default + should be suitable, as long as there is space available. Otherwise, pick a + different location. - Running the Tux Paint Windows Installer: + At this point, you can click 'Install' to install Tux Paint! - Double-click the Tux Paint installer executable (.EXE file) and - follow the instructions. + Changing the Settings Using the Shortcut - First, you will be asked to read the license. (It is the GNU General - Public License (GPL), which is also available as "COPYING.txt".) + To change program settings, right-click on the TuxPaint shortcut and + select 'Properties' (at the bottom). - You will then be asked whether you want to install shortcuts to Tux - Paint in your Windows Start Menu and on your Windows Desktop. (Both - options are set by default.) + Make sure the 'Shortcut' tab is selected in the window that appears, and + examine the 'Target:' field. You should see something like this: - Then you will be asked where you wish to install Tux Paint. The - default should be suitable, as long as there is space available. - Otherwise, pick a different location. + "C:\Program Files\TuxPaint\TuxPaint.exe" - At this point, you can click 'Install' to install Tux Paint! + You can now add command-line options which will be enabled when you + double-click the icon. - ------------------------------------------------------- + For example, to make the game run in fullscreen mode, with simple shapes + (no rotation option) and in French, add the options (after + 'TuxPaint.exe'), like so: - Changing the Settings Using the Shortcut: + "C:\Program Files\TuxPaint\TuxPaint.exe" -f -s --lang french - To change program settings, right-click on the TuxPaint shortcut and - select 'Properties' (at the bottom). + (See the main documentation for a full list of available command-line + options.) - Make sure the 'Shortcut' tab is selected in the window that appears, - and examine the 'Target:' field. You should see something like this: + If you make a mistake or it all disappears use [Ctrl] + [Z] to undo or + just hit the [Esc] key and the box will close with no changes made (unless + you pushed the "Apply" button!). - "C:\Program Files\TuxPaint\TuxPaint.exe" + When you have finished, click "OK." - You can now add command-line options which will be enabled when you - double-click the icon. + If Something Goes Wrong - For example, to make the game run in fullscreen mode, with simple - shapes (no rotation option) and in French, add the options (after - 'TuxPaint.exe'), like so: + If, when you double-click on the shortcut to run Tux Paint, nothing + happens, it is probably because some of these command-line options are + wrong. Open an Explorer like before, and look for a file called + "stderr.txt" in the TuxPaint folder. - "C:\Program Files\TuxPaint\TuxPaint.exe" -f -s --lang french + It will contain a description of what was wrong. Usually it will just be + due to incorrect character-case (capital 'Z' instead of lowercase 'z') or + a missing (or extra) '-' (dash). - (See the main documentation for a full list of available - command-line options.) +Linux/Unix - If you make a mistake or it all disappears use [Ctrl] + [Z] to undo - or just hit the [Esc] key and the box will close with no changes - made (unless you pushed the "Apply" button!). + Compiling: - When you have finished, click "OK." + 💡 Note: Tux Paint does not use autoconf/automake, so there is no + "./configure" script to run. Compiling should be straight-forward though, + assuming everything Tux Paint needs is installed. - ------------------------------------------------------- + To compile the program from source, simply run the following command from + a shell prompt (e.g., "$"): - If Something Goes Wrong: + $ make - If, when you double-click on the shortcut to run Tux Paint, nothing - happens, it is probably because some of these command-line options - are wrong. Open an Explorer like before, and look for a file called - "stderr.txt" in the TuxPaint folder. + Disabling SVG support (and hence Cairo, libSVG, and svg-cairo dependencies): - It will contain a description of what was wrong. Usually it will - just be due to incorrect character-case (capital 'Z' instead of - lowercase 'z') or a missing (or extra) '-' (dash). + To disable SVG support (e.g., if your system is not currently supported by + the Cairo library or other SVG-related dependencies), you can run "make" + with "SVG_LIB= SVG_CFLAGS= NOSVGFLAG=NOSVG" added: - ---------------------------------------------------------------------- + $ make SVG_LIB= SVG_CFLAGS= - Linux または Unix のユーザー + Disabling Pango support (and hence Pango, Cairo, etc. dependencies): - Compiling: + 📜 Prior to version 0.9.18, Tux Paint used the libSDL_ttf library for + rendering text using TrueType Fonts. Since 0.9.18, libSDL_Pango is used, + as it has much greater support for internationalization. However, if you + wish to disable the use of SDL_Pango, you may do so running "make" with + "SDL_PANGO_LIB=" added: - Note: Tux Paint does not use autoconf/automake, so there is no - "./configure" script to run. Compiling should be straight-forward - though, assuming everything Tux Paint needs is installed. + $ make SDL_PANGO_LIB= - To compile the program from source, simply run the following command - from a shell prompt (e.g., "$"): + Disabling Sound at Compile-time - $ make + If you don't have a sound card, or would prefer to build the program with + no sound support (and therefore without a the SDL_mixer dependency), you + can run "make" with "SDL_MIXER_LIB=" added: - ------------------------------------------------------- + $ make SDL_MIXER_LIB= - Disabling SVG support (and hence Cairo, libSVG, and svg-cairo dependencies): + Other options - To disable SVG support (e.g., if your system is not currently - supported by the Cairo library or other SVG-related dependencies), - you can run "make" with "SVG_LIB= SVG_CFLAGS= NOSVGFLAG=NOSVG" - added: + Various other options (e.g., installation paths) may be overridden; see + them in "Makefile" for further details. - $ make SVG_LIB= SVG_CFLAGS= + If you get errors - ------------------------------------------------------- + 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 "-dev" or "-devel" packages as well, otherwise you + won't be able to compile Tux Paint (and other programs) from source! - Disabling Pango support (and hence Pango, Cairo, etc. dependencies): + Installng - Prior to version 0.9.18, Tux Paint used the libSDL_ttf library for - rendering text using TrueType Fonts. Since 0.9.18, libSDL_Pango is - used, as it has much greater support for internationalization. - However, if you wish to disable the use of SDL_Pango, you may do so - running "make" with "SDL_PANGO_LIB=" added: + Assuming no fatal errors occured, you can now install the program so that + it can be run by users on the system. By default, this must be done by the + "root" user ('superuser'). Switch to "root" by typing the command: - $ make SDL_PANGO_LIB= + $ su - ------------------------------------------------------- + Enter "root"'s password at the prompt. You should now be "root" (with a + prompt like "#"). To install the program and its data files, type: - Disabling Sound at Compile-time: + # make install - If you don't have a sound card, or would prefer to build the program - with no sound support (and therefore without a the SDL_mixer - dependency), you can run "make" with "SDL_MIXER_LIB=" added: + Finally, you can switch back to your regular user by exiting superuser + mode: - $ make SDL_MIXER_LIB= + # exit - ------------------------------------------------------- + Alternatively, you may be able to simply use the "sudo" command (e.g., on + Ubuntu Linux): - Other options: + $ sudo make install - Various other options (e.g., installation paths) may be overridden; - see them in "Makefile" for further details. + 💡 Note: By default, "tuxpaint", the executable program, is placed in + "/usr/local/bin/". The data files (images, sounds, etc.) are placed in + "/usr/local/share/tuxpaint/". - ------------------------------------------------------- + Changing Where Things Go - If you get errors: + You can change where things will go by setting "Makefile"variables on the + command line. "DESTDIR" is used to place output in a staging area for + package creation. "PREFIX" is the basis of where all other files go, and + is, by default, set to "/usr/local". - 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 "-dev" or "-devel" - packages as well, otherwise you won't be able to compile Tux Paint - (and other programs) from source! + Other variables are: - ------------------------------------------------------- + BIN_PREFIX + Where the "tuxpaint" binary will be installed. (Set to + "$(PREFIX)/bin" by default - e.g., "/usr/local/bin") - Installng: + DATA_PREFIX + Where the data files (sound, graphics, brushes, stamps, fonts) + will go, and where Tux Paint will look for them when it's run. + (Set to "$(PREFIX)/share/tuxpaint") - Assuming no fatal errors occured, you can now install the program so - that it can be run by users on the system. By default, this must be - done by the "root" user ('superuser'). Switch to "root" by typing - the command: + DOC_PREFIX + Where the documentation text files (the "docs" directory) will go. + (Set to "$(PREFIX)/share/doc/tuxpaint") - $ su + MAN_PREFIX + Where the manual page for Tux Paint will go. (Set to + "$(PREFIX)/share/man") - Enter "root"'s password at the prompt. You should now be "root" - (with a prompt like "#"). To install the program and its data files, - type: + ICON_PREFIX — $(PREFIX)/share/pixmaps - # make install + X11_ICON_PREFIX — $(PREFIX)/X11R6/include/X11/pixmaps - Finally, you can switch back to your regular user by exiting - superuser mode: + GNOME_PREFIX — $(PREFIX)/share/gnome/apps/Graphics - # exit + KDE_PREFIX — $(PREFIX)/share/applnk/Graphics + Where the icons and launchers (for GNOME and KDE) will go. - Alternatively, you may be able to simply use the "sudo" command - (e.g., on Ubuntu Linux): + LOCALE_PREFIX + Where the translation files for Tux Paint will go, and where Tux + Paint will look for them. (Set to "$(PREFIX)/share/locale/") + (Final location of a translation file will be under the locale's + directory (e.g., "es" for Spanish), within the "LC_MESSAGES" + subdirectory.) - $ sudo make install + 💡 Note: This list is out of date. See "Makefile" and "Makefile-i18n" for a + complete list. - Note: By default, "tuxpaint", the executable program, is placed in - "/usr/local/bin/". The data files (images, sounds, etc.) are placed - in "/usr/local/share/tuxpaint/". +macOS - Changing Where Things Go + 2022年1月20日 Mark Kim - You can change where things will go by setting "Makefile"variables - on the command line. "DESTDIR" is used to place output in a - staging area for package creation. "PREFIX" is the basis of where - all other files go, and is, by default, set to "/usr/local". + 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. - Other variables are: + Prerequisites - BIN_PREFIX - Where the "tuxpaint" binary will be installed. (Set to - "$(PREFIX)/bin" by default - e.g., "/usr/local/bin") + 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: - DATA_PREFIX - Where the data files (sound, graphics, brushes, stamps, - fonts) will go, and where Tux Paint will look for them - when it's run. (Set to "$(PREFIX)/share/tuxpaint") + xcode-select --install - DOC_PREFIX - Where the documentation text files (the "docs" directory) - will go. (Set to "$(PREFIX)/share/doc/tuxpaint") + 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 + * libsdl_gfx + * pkgconfig + * zlib + ... but you should install any package that is required by the latest + version of Tux Paint. - MAN_PREFIX - Where the manual page for Tux Paint will go. (Set to - "$(PREFIX)/share/man") + ^* Not available from MacPorts as of this writing, see below. - ICON_PREFIX — $(PREFIX)/share/pixmaps + libimagequant - X11_ICON_PREFIX — $(PREFIX)/X11R6/include/X11/pixmaps + 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. - GNOME_PREFIX — $(PREFIX)/share/gnome/apps/Graphics + $ sudo port install rust cargo + $ git clone https://github.com/ImageOptim/libimagequant.git + $ cd libimagequant/imagequant-sys + $ cargo build --release # Must use cargo from MacPorts + $ sudo make PREFIX=/opt/local install - KDE_PREFIX — $(PREFIX)/share/applnk/Graphics - Where the icons and launchers (for GNOME and KDE) will go. + 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. - LOCALE_PREFIX - Where the translation files for Tux Paint will go, and - where Tux Paint will look for them. (Set to - "$(PREFIX)/share/locale/") (Final location of a - translation file will be under the locale's directory - (e.g., "es" for Spanish), within the "LC_MESSAGES" - subdirectory.) + How to Build - Note: This list is out of date. See "Makefile" and "Makefile-i18n" - for a complete list. + Simply, run: + + % make + % make install + + ... to create the TuxPaint.app application bundle that can be run in-place + or copied to /Applications. To create the DMG file for distribution, use + 'make TuxPaint.dmg'. + + Additional steps may be required when building for the Apple Silicon. See + "Building for Apple Silicon" below. + + 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. + + Alternatively, Tux Paint and all of its library dependencies may be + compiled with appropriate options to be runnable on older versions of + macOS. These options are already set on Tux Paint, so only its + dependencies (from MacPorts) need to be recompiled. See "Recompiling + MacPorts" below for the instructions. + + 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 for Intel CPU does allow dual booting of multiple versions of the + OS, but it's safer and easier to install the old macOS onto a flash drive. + Wherever you're installing it, the target drive's partitioniong scheme and + partition type must match what the old macOS expects, so use the Disk + Utility to partition and format the flash drive accordingly. + + Dual booting multiple versions of macOS for Apple Silicon has been so far + unsuccessful. Instead of installing an older version of macOS for Apple + Silicon to build Tux Paint to run on the old version of macOS for Apple + Silicon, use the instructions found in the "Recompiling MacPorts" section + to build Tux Paint to run on older versions of macOS for Apple Silicon. + + 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 + + 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. - macOS のユーザー + Recompiling MacPorts - 2022年1月20日 Mark Kim + To recompile MacPorts to be usable on older versions of macOS, set the + following options in /opt/local/etc/macports/macports.conf: - 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. + buildfromsource always + macosx_deployment_target 10.10 - Prerequisites + Then uninstall all MacPorts packages: - 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: + $ sudo port -fp uninstall installed - xcode-select --install + Then reinstall all MacPorts packages needed by Tux Paint. Also rebuild + libimagequant using the updated Cargo package from MacPorts. - 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 - * libsdl_gfx - * pkgconfig - * zlib - ... but you should install any package that is required by the - latest version of Tux Paint. + As of this writing, all libraries Tux Paint requires from MacPorts can be + recompiled in this manner to run on macOS 10.10 Yosemite and later on + Intel CPUs, and macOS 11.0 Big Sur and later on Apple Silicon. + Unfortunately, although MacPorts has the option to enable the building of + universal libraries, several libraries Tux Paint require cannot be built + as universal libraries so they can only be built to run natively on the + hardware on which they were built. See "Building a Universal Binary" below + for instructions on how to build Tux Paint as a Universal Binary. - ^* Not available from MacPorts as of this writing, see below. + Building for Apple Silicon - libimagequant + macOS for Applie Silicon requires all native Apple Silicon applications be + signed, even if it is signed "ad-hoc" (anonymously). Because of this, + compilers that produce native Apple Silicon applications sign all produced + binaries and libraries as a part of the compilation process.^* However, + the Tux Paint compilation process modifies the libraries to be modular + (using install_name_tool) so they can be added into the application + bundle, which has the unfortunate side effect of breaking the signature. + This can be addressed by signing the application bundle ad-hoc (example + below) or using your own Apple Developer Identity if you have one. The DMG + file, if needed, must be created after signing the App Bundle so the DMG + file is created with signed App Bundle: - 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. + $ codesign -s - TuxPaint.app + $ make TuxPaint.dmg - $ sudo port install rust cargo - $ git clone https://github.com/ImageOptim/libimagequant.git - $ cd libimagequant/imagequant-sys - $ cargo build --release # Must use cargo from MacPorts - $ sudo make PREFIX=/opt/local install + ^* For more information on the code signing requirements on the Apple + Silicon, see + https://developer.apple.com/documentation/macos-release-notes/macos-big-sur-11_0_1-universal-apps-release-notes#:~:text=New%20in%20macOS,pass%20through%20Gatekeeper. - 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. + If you get an error that the application bundle is already signed, remove + it before signing:: - ------------------------------------------------------- + $ codesign --remove-signature TuxPaint.app - How to Build + If you plan to combine the Apple Silicon bundle with the Intel CPU bundle + to produce the Universal bundle, the code signing must be done after they + are combined. See "Building a Universal Binary" below. - Simply, run: - - % make - % make install + Building a Universal Binary - ... to create the TuxPaint.app application bundle that can be run - in-place or copied to /Applications. To create the DMG file for - distribution, use 'make TuxPaint.dmg'. + To build Tux Paint as a Universal Binary, compile Tux Paint for the Intel + CPU and the Apple Silicon separately first. Then rename the app bundle for + the Intel CPU to TuxPaint-x86_64.app, and the bundle for the Apple Silicon + to TuxPaint-arm64.app, copy the app bundle from the Intel machine to the + Apple Silicon machine, then use the provided build-universal.sh script to + combine the two application bundles as below. The produced bundle must be + signed (see "Building for Apple Silicon" above for more details). The DMG + file, if required, must be built after the signing: - Additional steps may be required when building for the Apple - Silicon. See "Building for Apple Silicon" below. - - ------------------------------------------------------- - - 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. - - Alternatively, Tux Paint and all of its library dependencies may - be compiled with appropriate options to be runnable on older - versions of macOS. These options are already set on Tux Paint, - so only its dependencies (from MacPorts) need to be recompiled. - See "Recompiling MacPorts" below for the instructions. - - ------------------------------------------------------- - - 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 for Intel CPU does allow dual booting of multiple versions of - the OS, but it's safer and easier to install the old macOS onto a - flash drive. Wherever you're installing it, the target drive's - partitioniong scheme and partition type must match what the old - macOS expects, so use the Disk Utility to partition and format the - flash drive accordingly. - - Dual booting multiple versions of macOS for Apple Silicon has been - so far unsuccessful. Instead of installing an older version of macOS - for Apple Silicon to build Tux Paint to run on the old version of - macOS for Apple Silicon, use the instructions found in the - "Recompiling MacPorts" section to build Tux Paint to run on older - versions of macOS for Apple Silicon. - - 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 - - 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/ + $ macos/build-universal.sh + $ codesign -s - TuxPaint.app + $ make TuxPaint.dmg - 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 + Debugging - 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 output — to "STDOUT" on Linux and Unix, to a "stdout.txt" file + on Windows, and to the file "/tmp/tuxpaint.log" on macOS — can be enabled + by setting "DEBUG" (and, if verbose logging is wanted, "VERBOSE") #defines + in "src/debug.h" and (re)compiling Tux Paint. - Recompiling MacPorts + Uninstalling Tux Paint - To recompile MacPorts to be usable on older versions of macOS, set - the following options in /opt/local/etc/macports/macports.conf: +Windows - buildfromsource always - macosx_deployment_target 10.10 + Using the Uninstaller - Then uninstall all MacPorts packages: + If you installed the Start Menu shortcuts (the default), then go to the + TuxPaint folder and select "Uninstall". A box will be displayed that will + confirm that you are about to uninstall Tux Paint and, if you are certain + that you want to permanently remove Tux Paint, click on the 'Uninstall' + button. - $ sudo port -fp uninstall installed + When it has finished, click on the close button. - Then reinstall all MacPorts packages needed by Tux Paint. Also - rebuild libimagequant using the updated Cargo package from MacPorts. + Using the Control Panel - As of this writing, all libraries Tux Paint requires from MacPorts - can be recompiled in this manner to run on macOS 10.10 Yosemite and - later on Intel CPUs, and macOS 11.0 Big Sur and later on Apple - Silicon. Unfortunately, although MacPorts has the option to enable - the building of universal libraries, several libraries Tux Paint - require cannot be built as universal libraries so they can only be - built to run natively on the hardware on which they were built. See - "Building a Universal Binary" below for instructions on how to build - Tux Paint as a Universal Binary. + It is also possible to use the entry "TuxPaint (remove only)" in the + Control Panel Add/Remove programs section. - Building for Apple Silicon +macOS - macOS for Applie Silicon requires all native Apple Silicon - applications be signed, even if it is signed "ad-hoc" (anonymously). - Because of this, compilers that produce native Apple Silicon - applications sign all produced binaries and libraries as a part of - the compilation process.^* However, the Tux Paint compilation - process modifies the libraries to be modular (using - install_name_tool) so they can be added into the application bundle, - which has the unfortunate side effect of breaking the signature. - This can be addressed by signing the application bundle ad-hoc - (example below) or using your own Apple Developer Identity if you - have one. The DMG file, if needed, must be created after signing the - App Bundle so the DMG file is created with signed App Bundle: + Delete "TuxPaint.app" from the "Applications" folder. Data files, + including the configuration files, stamps, and saved pictures, may be + found in "Library/Application Support/TuxPaint" (all users) and + "/Users/USERNAME/Library/Application Support/TuxPaint" (individual users). - $ codesign -s - TuxPaint.app - $ make TuxPaint.dmg +Linux - ^* For more information on the code signing requirements on the - Apple Silicon, see - https://developer.apple.com/documentation/macos-release-notes/macos-big-sur-11_0_1-universal-apps-release-notes#:~:text=New%20in%20macOS,pass%20through%20Gatekeeper. - - If you get an error that the application bundle is already signed, - remove it before signing:: - - $ codesign --remove-signature TuxPaint.app - - If you plan to combine the Apple Silicon bundle with the Intel CPU - bundle to produce the Universal bundle, the code signing must be - done after they are combined. See "Building a Universal Binary" - below. - - Building a Universal Binary - - To build Tux Paint as a Universal Binary, compile Tux Paint for the - Intel CPU and the Apple Silicon separately first. Then rename the - app bundle for the Intel CPU to TuxPaint-x86_64.app, and the bundle - for the Apple Silicon to TuxPaint-arm64.app, copy the app bundle - from the Intel machine to the Apple Silicon machine, then use the - provided build-universal.sh script to combine the two application - bundles as below. The produced bundle must be signed (see "Building - for Apple Silicon" above for more details). The DMG file, if - required, must be built after the signing: - - $ macos/build-universal.sh - $ codesign -s - TuxPaint.app - $ make TuxPaint.dmg - - ---------------------------------------------------------------------- - -Debugging - - Debugging output — to "STDOUT" on Linux and Unix, to a "stdout.txt" file - on Windows, and to the file "/tmp/tuxpaint.log" on macOS — can be - enabled by setting "DEBUG" (and, if verbose logging is wanted, - "VERBOSE") #defines in "src/debug.h" and (re)compiling Tux Paint. - - ---------------------------------------------------------------------- - -Uninstalling Tux Paint - - Windows - - Using the Uninstaller - - If you installed the Start Menu shortcuts (the default), then go to - the TuxPaint folder and select "Uninstall". A box will be displayed - that will confirm that you are about to uninstall Tux Paint and, if - you are certain that you want to permanently remove Tux Paint, click - on the 'Uninstall' button. - - When it has finished, click on the close button. - - Using the Control Panel - - It is also possible to use the entry "TuxPaint (remove only)" in the - Control Panel Add/Remove programs section. - - ---------------------------------------------------------------------- - - macOS - - Delete "TuxPaint.app" from the "Applications" folder. Data files, - including the configuration files, stamps, and saved pictures, may be - found in "Library/Application Support/TuxPaint" (all users) and - "/Users/USERNAME/Library/Application Support/TuxPaint" (individual - users). - - ---------------------------------------------------------------------- - - Linux - - Within the Tux Paint source directory (where you compiled Tux Paint), - you can use the "make uninstall" target to uninstall Tux Paint. By - default, this must be done by the "root" user ('superuser'), but if - you installed Tux Paint somewhere else (e.g., using a "PREFIX=..." - setting to "make" and "make install"), you may not, and will want to - provide those same settings here. (See the installation instructions - above for further information.) + Within the Tux Paint source directory (where you compiled Tux Paint), you + can use the "make uninstall" target to uninstall Tux Paint. By default, + this must be done by the "root" user ('superuser'), but if you installed + Tux Paint somewhere else (e.g., using a "PREFIX=..." setting to "make" and + "make install"), you may not, and will want to provide those same settings + here. (See the installation instructions above for further information.) diff --git a/docs/ja_JP.UTF-8/html/EXTENDING.html b/docs/ja_JP.UTF-8/html/EXTENDING.html index e35a9d6bd..ab40472bc 100644 --- a/docs/ja_JP.UTF-8/html/EXTENDING.html +++ b/docs/ja_JP.UTF-8/html/EXTENDING.html @@ -21,15 +21,17 @@ } div.keeptogether { page-break-inside: avoid; } section h1 { font-size: 2em; } - h1, h2, h3, h4 { font-family: sans; } + h1, h2, h3, h4, h5 { font-family: sans; } h1 { color: #800; page-break-before: always; break-before: always; } h2 { color: #440; page-break-after: avoid; break-after: avoid; } h3 { color: #080; page-break-after: avoid; break-after: avoid; } h4 { color: #008; page-break-after: avoid; break-after: avoid; } + h5 { color: #808; page-break-after: avoid; break-after: avoid; } h1 + p { page-break-inside: avoid; } h2 + p { page-break-inside: avoid; } h3 + p { page-break-inside: avoid; } h4 + p { page-break-inside: avoid; } + h5 + p { page-break-inside: avoid; } dt { font-size: large; color: #404; diff --git a/docs/ja_JP.UTF-8/html/INSTALL.html b/docs/ja_JP.UTF-8/html/INSTALL.html index 0286a286e..b035ed3c8 100644 --- a/docs/ja_JP.UTF-8/html/INSTALL.html +++ b/docs/ja_JP.UTF-8/html/INSTALL.html @@ -5,249 +5,312 @@ Tux Paint Installation Documentation + -
-

- Tux Paint
- バージョン 0.9.28
- Installation Documentation

+
+
+
+

+ Tux Paint
+ バージョン 0.9.28
+ Installation Documentation

-

- Copyright © 2002-2022 by various contributors; see AUTHORS.txt.
- https://tuxpaint.org/ -

+

+ Copyright © 2002-2022 by various contributors; see AUTHORS.txt.
+ https://tuxpaint.org/ +

-

- 2022年1月20日

-
+

+ 2022年3月31日

+
+ -
+ + + + -
+ 目次
- - - + + + +
- 目次
+ +
+ - - - - - - +
+
+

+ + Requirements +

+
-
+
+
+

+ + Simple DirectMedia Layer library (libSDL) +

+
-

- - Requirements -

-
- -

- - Simple DirectMedia Layer library (libSDL) -

-

Tux Paint requires the Simple DirectMedia Layer Library (libSDL), an Open Source multimedia programming library available under the GNU Lesser General Public License (LGPL).

Along with libSDL, Tux Paint depends on a number of other SDL 'helper' libraries: SDL_Image (for graphics files), SDL_gfx (for some graphical functions, like rotation), SDL_TTF and (optionally) SDL_Pango (for True Type Font support) and, optionally, SDL_Mixer (for sound effects).

-

Linux/Unix Users:

-
-

- The SDL libraries are available as source-code, or as RPM or Debian packages for various distributions of Linux. They can be downloaded from:

- +
+
Linux/Unix
+
+

+ The SDL libraries are available as source-code, or as RPM or Debian packages for various distributions of Linux. They can be downloaded from:

+ -

- They are also typically available along with your Linux distribution (e.g. on an installation media, or available via package maintainance software like Debian's "apt").

+

+ They are also typically available along with your Linux distribution (e.g. on an installation media, or available via package maintainance software like Debian's "apt").

-

- Note: When installing libraries from packages, be sure to ALSO install the development versions of the packages. (For example, install both "SDL-1.2.4.rpm" and "SDL-1.2.4-devel.rpm".)

-
-
+

+ 💡 Note: When installing libraries from packages, be sure to ALSO install the development versions of the packages. (For example, install both "SDL-1.2.4.rpm" and "SDL-1.2.4-devel.rpm".)

+ + +
+ +
+
+

+ + Other Libraries +

+
-

- - Other Libraries -

-

Tux Paint also takes advantage of a number of other free, LGPL'd libraries. Under Linux, just like SDL, they should either already be installed, or are readily available for installation as part of your Linux distribution.

-

libPNG

-
-

- Tux Paint uses PNG (Portable Network Graphics) format for its data files. SDL_image will require libPNG be installed.

+
+
libPNG
+
+

+ Tux Paint uses PNG (Portable Network Graphics) format for its data files. SDL_image will require libPNG be installed.

-

- http://www.libpng.org/pub/png/libpng.html -

-
+

+ http://www.libpng.org/pub/png/libpng.html +

+ -

gettext

-
-

- Tux Paint uses your system's locale settings along with the "gettext" library to support various languages (e.g., Spanish). You'll need the gettext library installed.

+
gettext
+
+

+ Tux Paint uses your system's locale settings along with the "gettext" library to support various languages (e.g., Spanish). You'll need the gettext library installed.

-

- http://www.gnu.org/software/gettext/ -

-
+

+ http://www.gnu.org/software/gettext/ +

+ -

libpaper (Linux/Unix only)

-
-

- As of Tux Paint 0.9.17, Tux Paint can determine your system's default paper size (e.g., A4 or Letter), or can be told to use a particular paper size, thanks to "libpaper".

+
libpaper (Linux/Unix only)
+
+

+ As of Tux Paint 0.9.17, Tux Paint can determine your system's default paper size (e.g., A4 or Letter), or can be told to use a particular paper size, thanks to "libpaper".

-

- https://github.com/naota/libpaper -

-
+

+ https://github.com/naota/libpaper +

+ -

FriBiDi

-
-

- Tux Paint's "Text" and also "Label" tools support bidirectional languages, thanks to the "FriBiDi" library.

+
FriBiDi
+
+

+ Tux Paint's "Text" and also "Label" tools support bidirectional languages, thanks to the "FriBiDi" library.

-

- http://fribidi.org/ -

-
+

+ http://fribidi.org/ +

+ -

SVG graphics support

-
-

- As of Tux Paint 0.9.17, Tux Paint can load SVG (Scalable Vector Graphics) images as stamps. Two sets of libraries are supported, and SVG support can be completely disabled (via "make SVG_LIB:=")

+
SVG graphics support
+
+

+ As of Tux Paint 0.9.17, Tux Paint can load SVG (Scalable Vector Graphics) images as stamps. Two sets of libraries are supported, and SVG support can be completely disabled (via "make SVG_LIB:=")

-
librsvg-2 & libCairo2 (newer libraries)
- +
+
librsvg-2 & libCairo2 (newer libraries)
+
+ +
-
Older SVG libraries
- -
+
Older SVG libraries
+
+ +
+ + -

Animated GIF Export feature

-
-

- To support export of animated GIFs (slideshows), the "libimagequant" library (from the "pngquant2" project) is required.

+
Animated GIF Export feature
+
+

+ To support export of animated GIFs (slideshows), the "libimagequant" library (from the "pngquant2" project) is required.

-

- https://github.com/ImageOptim/libimagequant -

-
+

+ https://github.com/ImageOptim/libimagequant +

+ -

NetPBM Tools (optional) No longer used, by default

-
-

- Under Linux and Unix, earlier versions of Tux Paint used the NetPBM tools to assist with printing. (A PNG is generated by Tux Paint, and converted into a PostScript using the 'pngtopnm' and 'pnmtops' NetPBM command-line tools.)

+
NetPBM Tools (optional) No longer used, by default
+
+

+ 📜 Under Linux and Unix, earlier versions of Tux Paint used the NetPBM tools to assist with printing. (A PNG is generated by Tux Paint, and converted into a PostScript using the 'pngtopnm' and 'pnmtops' NetPBM command-line tools.)

-

- http://netpbm.sourceforge.net/ -

-
-
- +

+ http://netpbm.sourceforge.net/ +

+ + +
+
-
+
+
+

+ + Compiling and Installation +

+
-

- - Compiling and Installation -

-

Tux Paint is released under the GNU General Public License (GPL) (see "COPYING.txt" for details), and therefore the 'source code' to the program is available freely.

-

- - Windows のユーザー -

-

- - 2021年11月 3日 Shin-ichi TOYAMA dolphin6k@wmail.plala.or.jp <dolphin6k@wmail.plala.or.jp> - -

-
-

Compiling Set-Up

-
+
+
+

+ + Windows +

+ +

+ + 2021年11月 3日 Shin-ichi TOYAMA dolphin6k@wmail.plala.or.jp <dolphin6k@wmail.plala.or.jp> + +

+
+ +
+
+

Compiling Set-Up

+
+

As of February 2005 (starting with Tux Paint 0.9.15), the "Makefile" includes support for building on a Windows system using MinGW/MSYS (https://sourceforge.net/projects/msys2/).

@@ -276,183 +339,194 @@

-
+

+ + Proceed to the next "MinGW 64bit (x86_64) toolchains" section, or skip to the "MinGW 32bit (i686) toolchains" section if you need only a 32bit build environment. +

-

- - Proceed to the next "MinGW 64bit (x86_64) toolchains" section, or skip 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 64bit development tools:

- - pacman -S mingw-w64-x86_64-toolchain - -
-

- -
- -

- 64bit (x86_64) dependency libraries for Tux Paint

- -
-

- You can install tools and libraries required for compiling Tux Paint on MSYS2/MINGW using "pacman" except for SDL_Pango.

-

- "ntldd" is a small tool which examine windows executable files to list Dynamic Link Library (.dll) files they depends on. Tux Paint's packaging process for binary distribution uses it to find required .dll files.

-

- FLTK is a cross-platform GUI toolkit used by "Tux Paint Config.". You can skip installing it if you are only building "Tux Paint".

-

-

- - $ pacman -S mingw-w64-x86_64-SDL_{image,mixer,ttf,gfx}
- $ pacman -S mingw-w64-x86_64-librsvg
- $ pacman -S mingw-w64-x86_64-fribidi
- $ pacman -S mingw-w64-x86_64-libimagequant
- $ pacman -S mingw-w64-x86_64-fltk
- $ pacman -S mingw-w64-x86_64-ntldd-git - -
-

-

- Note: Close the shell before proceeding to the remaining process.

- -
- -

- Install SDL_Pango on the 64bit environment

- -
-

- SDL_Pango should be installed manually.

-

- This time, use the MinGW "64bit" shell. Open the shell from the "Start Menu" -> "MSYS2 64bit" -> "MSYS2 MinGW 64-bit"

- -
SDL_Pango
- -
- -

- At first, you have to prepare source tar-ball and a required patch in the same directory.

- -

- Build and install SDL_Pango as follows.

- - $ tar zxvf SDL_Pango-0.1.2.tar.gz
- $ cd SDL_Pango-0.1.2/
- $ patch -p0 < ../SDL_Pango-configure-extra-api.patch
- $ ./configure --prefix=/mingw64 && make && make install - -
-

-
- -
- -

- - Proceed to the next "MinGW 32bit (i686) toolchains" section, or skip 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 32bit development tools:

- - pacman -S mingw-w64-i686-toolchain - -
-

- -
- -

- 32bit (i686) dependency libraries for Tux Paint

- -
-

- You can install tools and libraries required for compiling Tux Paint on MSYS2/MINGW using "pacman" except for SDL_Pango.

-

- "ntldd" is a small tool which examine windows executable files to list Dynamic Link Library (.dll) files they depends on. Tux Paint's packaging process for binary distribution uses it to find required .dll files.

-

- FLTK is a cross-platform GUI toolkit used by "Tux Paint Config.". You can skip installing it if you are only building "Tux Paint".

-

-

- - $ pacman -S mingw-w64-i686-SDL_{image,mixer,ttf,gfx}
- $ pacman -S mingw-w64-i686-librsvg
- $ pacman -S mingw-w64-i686-fribidi
- $ pacman -S mingw-w64-i686-libimagequant
- $ pacman -S mingw-w64-i686-fltk
- $ pacman -S mingw-w64-i686-ntldd-git - -
-

-

- Note: Close the shell before proceeding to the remaining process.

- -
- -

- Install SDL_Pango on the 32bit environment

- -
-

- SDL_Pango should be installed manually.

-

- This time, use the MinGW "32bit" shell. Open the shell from the "Start Menu" -> "MSYS2 64bit" -> "MSYS2 MinGW 32-bit"

- -
SDL_Pango
- -
+
+
+

+ + MinGW 64bit (x86_64) toolchains +

+

- At first, you have to prepare source tar-ball and a required patch in the same directory.

- -

- Build and install SDL_Pango as follows.

+ Within the MSYS2 shell, run the following command to install basic 64bit development tools:
- $ tar zxvf SDL_Pango-0.1.2.tar.gz
- $ cd SDL_Pango-0.1.2/
- $ patch -p0 < ../SDL_Pango-configure-extra-api.patch
- $ ./configure --prefix=/mingw32 && make && make install + pacman -S mingw-w64-x86_64-toolchain

-
+
-
+
+
+

+ 64bit (x86_64) dependency libraries for Tux Paint

+
- -
+

+ You can install tools and libraries required for compiling Tux Paint on MSYS2/MINGW using "pacman" except for SDL_Pango.

+

+ "ntldd" is a small tool which examine windows executable files to list Dynamic Link Library (.dll) files they depends on. Tux Paint's packaging process for binary distribution uses it to find required .dll files.

+

+ FLTK is a cross-platform GUI toolkit used by "Tux Paint Config.". You can skip installing it if you are only building "Tux Paint".

+

+

+ + $ pacman -S mingw-w64-x86_64-SDL_{image,mixer,ttf,gfx}
+ $ pacman -S mingw-w64-x86_64-librsvg
+ $ pacman -S mingw-w64-x86_64-fribidi
+ $ pacman -S mingw-w64-x86_64-libimagequant
+ $ pacman -S mingw-w64-x86_64-fltk
+ $ pacman -S mingw-w64-x86_64-ntldd-git + +
+

+

+ 💡 Note: Close the shell before proceeding to the remaining process.

+
-

- ImageMagick -

+
+
+

+ Install SDL_Pango on the 64bit environment

+
+ +

+ SDL_Pango should be installed manually.

+

+ This time, use the MinGW "64bit" shell. Open the shell from the "Start Menu" -> "MSYS2 64bit" -> "MSYS2 MinGW 64-bit"

+ +
+
+
SDL_Pango
+
+ +

+ At first, you have to prepare source tar-ball and a required patch in the same directory.

+

+

+ Build and install SDL_Pango as follows.

+ + $ tar zxvf SDL_Pango-0.1.2.tar.gz
+ $ cd SDL_Pango-0.1.2/
+ $ patch -p0 < ../SDL_Pango-configure-extra-api.patch
+ $ ./configure --prefix=/mingw64 && make && make install + +
+

+
+ +

+ + Proceed to the next "MinGW 32bit (i686) toolchains" section, or skip 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 32bit development tools:

+ + pacman -S mingw-w64-i686-toolchain + +
+

+
+ +
+
+

+ 32bit (i686) dependency libraries for Tux Paint

+
+ +

+ You can install tools and libraries required for compiling Tux Paint on MSYS2/MINGW using "pacman" except for SDL_Pango.

+

+ "ntldd" is a small tool which examine windows executable files to list Dynamic Link Library (.dll) files they depends on. Tux Paint's packaging process for binary distribution uses it to find required .dll files.

+

+ FLTK is a cross-platform GUI toolkit used by "Tux Paint Config.". You can skip installing it if you are only building "Tux Paint".

+

+

+ + $ pacman -S mingw-w64-i686-SDL_{image,mixer,ttf,gfx}
+ $ pacman -S mingw-w64-i686-librsvg
+ $ pacman -S mingw-w64-i686-fribidi
+ $ pacman -S mingw-w64-i686-libimagequant
+ $ pacman -S mingw-w64-i686-fltk
+ $ pacman -S mingw-w64-i686-ntldd-git + +
+

+

+ 💡 Note: Close the shell before proceeding to the remaining process.

+
+ +
+
+

+ Install SDL_Pango on the 32bit environment

+
+ +

+ SDL_Pango should be installed manually.

+

+ This time, use the MinGW "32bit" shell. Open the shell from the "Start Menu" -> "MSYS2 64bit" -> "MSYS2 MinGW 32-bit"

+ +
+
+
SDL_Pango
+
+ +

+ At first, you have to prepare source tar-ball and a required patch in the same directory.

+

+

+ Build and install SDL_Pango as follows.

+ + $ tar zxvf SDL_Pango-0.1.2.tar.gz
+ $ cd SDL_Pango-0.1.2/
+ $ patch -p0 < ../SDL_Pango-configure-extra-api.patch
+ $ ./configure --prefix=/mingw32 && make && make install + +
+

+
+ + +
+ +
+ +
+
+

+ ImageMagick +

+
-

ImageMagick is a compilation of command line tools to create, edit, compose, or convert bitmap images supporting quite a large number of image formats. Tux Paint uses two functions ("convert" and "composite") in it to generate thumbnails for startar images and templates during the build process.

@@ -468,13 +542,13 @@

You can make this permanent by adding the above to your the BASH shell configuration file, "~/.bash_profile".

-
+
-
+
+
+

Tux Paint

+
-

Tux Paint

- -

You can compile 64bit binaries using MSYS2 64bit shell, and 32bit binaries using MSYS2 32bit shell, respectively.

    @@ -490,16 +564,17 @@

-

- Note: At this point, you will want to build "Tux Paint Config." for Windows, so it can be included along with "Tux Paint", if you're making an official (or test) release. The build process will look for it in a directory named "tuxpaint-config" (with no version number, e.g., "tuxpaint-config-X.Y.Z"). See "Tux Paint Config."'s INSTALL.txt documentation for details.

+

+ 💡 Note: At this point, you will want to build "Tux Paint Config." for Windows, so it can be included along with "Tux Paint", if you're making an official (or test) release. The build process will look for it in a directory named "tuxpaint-config" (with no version number, e.g., "tuxpaint-config-X.Y.Z"). See "Tux Paint Config."'s INSTALL.txt documentation for details.

All the files needed for starting Tux Paint (and Tux Paint Config.) are collected in the directory for binary distribution "bdist" directory under "win32". You can start them by double-clicking their executable (.exe) files in the "bdist" directory.

- +
-
- -

Building the Tux Paint Windows Installer:

-
+
+
+

+ Building the Tux Paint Windows Installer

+

Inno Setup is used to build executable installer for Tux Paint. Therefore you have to install it in the first place.

@@ -509,14 +584,17 @@ Before building an installer, edit the "tuxpaint.iss" file and enable one of the lines starting with "#define BuildTarget=", depending on the architecture of the installer you want to create.

Then, you can easily build an executable installer by right-clicking on the "tuxpaint.iss" icon in the "win32" directory and selecting "Compile" on the list. It will run for a while, and eventually you will find a "tuxpaint-X.Y.Z-windows-<arch>-installer.exe" file in the same directory.

-
+ -
+
+
+

+ Running the Tux Paint Windows Installer

+
-

Running the Tux Paint Windows Installer:

-

- Double-click the Tux Paint installer executable (.EXE file) and follow the instructions. + Double-click the Tux Paint installer executable (.EXE file) and follow the instructions.

+

First, you will be asked to read the license. (It is the GNU General Public License (GPL), which is also available as "COPYING.txt".)

@@ -528,12 +606,14 @@

At this point, you can click 'Install' to install Tux Paint!

-
+
-
+
+
+

+ Changing the Settings Using the Shortcut

+
-

Changing the Settings Using the Shortcut:

-

To change program settings, right-click on the TuxPaint shortcut and select 'Properties' (at the bottom).

@@ -566,31 +646,38 @@

When you have finished, click "OK."

-
+
-
+
+
+

+ If Something Goes Wrong

+
-

If Something Goes Wrong:

-

If, when you double-click on the shortcut to run Tux Paint, nothing happens, it is probably because some of these command-line options are wrong. Open an Explorer like before, and look for a file called "stderr.txt" in the TuxPaint folder.

It will contain a description of what was wrong. Usually it will just be due to incorrect character-case (capital 'Z' instead of lowercase 'z') or a missing (or extra) '-' (dash).

-
- +
+ -
+
+
+

+ + Linux/Unix +

+
-

- - Linux または Unix のユーザー -

-
-

Compiling:

-
-

- Note: Tux Paint does not use autoconf/automake, so there is no "./configure" script to run. Compiling should be straight-forward though, assuming everything Tux Paint needs is installed.

+
+
+

+ Compiling:

+
+ +

+ 💡 Note: Tux Paint does not use autoconf/automake, so there is no "./configure" script to run. Compiling should be straight-forward though, assuming everything Tux Paint needs is installed.

To compile the program from source, simply run the following command from a shell prompt (e.g., "$"):

@@ -600,13 +687,14 @@ $ make
-
+
-
+
+
+

+ Disabling SVG support (and hence Cairo, libSVG, and svg-cairo dependencies):

+
-

- Disabling SVG support (and hence Cairo, libSVG, and svg-cairo dependencies):

-

To disable SVG support (e.g., if your system is not currently supported by the Cairo library or other SVG-related dependencies), you can run "make" with "SVG_LIB= SVG_CFLAGS= NOSVGFLAG=NOSVG" added:

@@ -614,54 +702,64 @@ $ make SVG_LIB= SVG_CFLAGS=
-
+
-
+
+
+

+ Disabling Pango support (and hence Pango, Cairo, etc. dependencies):

+
-

- Disabling Pango support (and hence Pango, Cairo, etc. dependencies):

-
-

- Prior to version 0.9.18, Tux Paint used the libSDL_ttf library for rendering text using TrueType Fonts. Since 0.9.18, libSDL_Pango is used, as it has much greater support for internationalization. However, if you wish to disable the use of SDL_Pango, you may do so running "make" with "SDL_PANGO_LIB=" added:

+

+ 📜 Prior to version 0.9.18, Tux Paint used the libSDL_ttf library for rendering text using TrueType Fonts. Since 0.9.18, libSDL_Pango is used, as it has much greater support for internationalization. However, if you wish to disable the use of SDL_Pango, you may do so running "make" with "SDL_PANGO_LIB=" added:

$ make SDL_PANGO_LIB=
-
+
-
+
+
+

+ Disabling Sound at Compile-time

+
-

Disabling Sound at Compile-time:

-
- If you don't have a sound card, or would prefer to build the program with no sound support (and therefore without a the SDL_mixer dependency), you can run "make" with "SDL_MIXER_LIB=" added:

+

+ If you don't have a sound card, or would prefer to build the program with no sound support (and therefore without a the SDL_mixer dependency), you can run "make" with "SDL_MIXER_LIB=" added:

$ make SDL_MIXER_LIB=
-
+
-
+
+
+

+ Other options

+
-

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 get errors:

-

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 "-dev" or "-devel" packages as well, otherwise you won't be able to compile Tux Paint (and other programs) from source!

-
+
-
+
+
+

+ Installng

+
-

Installng:

-

Assuming no fatal errors occured, you can now install the program so that it can be run by users on the system. By default, this must be done by the "root" user ('superuser'). Switch to "root" by typing the command:

@@ -698,11 +796,15 @@
-

- Note: By default, "tuxpaint", the executable program, is placed in "/usr/local/bin/". The data files (images, sounds, etc.) are placed in "/usr/local/share/tuxpaint/".

+

+ 💡 Note: By default, "tuxpaint", the executable program, is placed in "/usr/local/bin/". The data files (images, sounds, etc.) are placed in "/usr/local/share/tuxpaint/".

+ +
+
+

+ Changing Where Things Go

+
-
Changing Where Things Go
-

You can change where things will go by setting "Makefile"variables on the command line. "DESTDIR" is used to place output in a staging area for package creation. "PREFIX" is the basis of where all other files go, and is, by default, set to "/usr/local".

@@ -737,30 +839,34 @@ Where the translation files for Tux Paint will go, and where Tux Paint will look for them. (Set to "$(PREFIX)/share/locale/") (Final location of a translation file will be under the locale's directory (e.g., "es" for Spanish), within the "LC_MESSAGES" subdirectory.) -

- Note: This list is out of date. See "Makefile" and "Makefile-i18n" for a complete list.

-
- - +

+ 💡 Note: This list is out of date. See "Makefile" and "Makefile-i18n" for a complete list.

+
+
+ -
+
+
+

+ + macOS +

+

+ + 2022年1月20日 Mark Kim <markuskimius@gmail.com> + +

+
-

- - macOS のユーザー -

-

- - 2022年1月20日 Mark 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

-
+
+
+

+ 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:

@@ -792,8 +898,13 @@
* Not available from MacPorts as of this writing, see below.

-
libimagequant
-
+
+
+

+ 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.

@@ -805,17 +916,18 @@

- -
+

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

+
-

How to Build

-

Simply, run:

@@ -827,12 +939,14 @@

Additional steps may be required when building for the Apple Silicon. See "Building for Apple Silicon" below.

-
+
-
+
+
+

+ Known Issues

+
-

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.
    @@ -841,12 +955,14 @@
    Alternatively, Tux Paint and all of its library dependencies may be compiled with appropriate options to be runnable on older versions of macOS. These options are already set on Tux Paint, so only its dependencies (from MacPorts) need to be recompiled. See "Recompiling MacPorts" below for the instructions.
-
+
-
+
+
+

+ Old Versions 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

@@ -870,11 +986,14 @@

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.

+
- +
+
+

+ Recompiling MacPorts

+
-

Recompiling MacPorts

-

To recompile MacPorts to be usable on older versions of macOS, set the following options in /opt/local/etc/macports/macports.conf:

@@ -897,18 +1016,21 @@

As of this writing, all libraries Tux Paint requires from MacPorts can be recompiled in this manner to run on macOS 10.10 Yosemite and later on Intel CPUs, and macOS 11.0 Big Sur and later on Apple Silicon. Unfortunately, although MacPorts has the option to enable the building of universal libraries, several libraries Tux Paint require cannot be built as universal libraries so they can only be built to run natively on the hardware on which they were built. See "Building a Universal Binary" below for instructions on how to build Tux Paint as a Universal Binary.

-
+
+ +
+
+

+ Building for Apple Silicon

+
-

Building for Apple Silicon

-

macOS for Applie Silicon requires all native Apple Silicon applications be signed, even if it is signed "ad-hoc" (anonymously). Because of this, compilers that produce native Apple Silicon applications sign all produced binaries and libraries as a part of the compilation process.* However, the Tux Paint compilation process modifies the libraries to be modular (using install_name_tool) so they can be added into the application bundle, which has the unfortunate side effect of breaking the signature. This can be addressed by signing the application bundle ad-hoc (example below) or using your own Apple Developer Identity if you have one. The DMG file, if needed, must be created after signing the App Bundle so the DMG file is created with signed App Bundle:

$ codesign -s - TuxPaint.app
$ make TuxPaint.dmg
- * For more information on the code signing requirements on the Apple Silicon, see https://developer.apple.com/documentation/macos-release-notes/macos-big-sur-11_0_1-universal-apps-release-notes#:~:text=New%20in%20macOS,pass%20through%20Gatekeeper. -

+ * For more information on the code signing requirements on the Apple Silicon, see https://developer.apple.com/documentation/macos-release-notes/macos-big-sur-11_0_1-universal-apps-release-notes#:~:text=New%20in%20macOS,pass%20through%20Gatekeeper.

If you get an error that the application bundle is already signed, remove it before signing::

$ codesign --remove-signature TuxPaint.app @@ -916,10 +1038,14 @@

If you plan to combine the Apple Silicon bundle with the Intel CPU bundle to produce the Universal bundle, the code signing must be done after they are combined. See "Building a Universal Binary" below.

-
+
+ +
+
+

+ Building a Universal Binary

+
-

Building a Universal Binary

-

To build Tux Paint as a Universal Binary, compile Tux Paint for the Intel CPU and the Apple Silicon separately first. Then rename the app bundle for the Intel CPU to TuxPaint-x86_64.app, and the bundle for the Apple Silicon to TuxPaint-arm64.app, copy the app bundle from the Intel machine to the Apple Silicon machine, then use the provided build-universal.sh script to combine the two application bundles as below. The produced bundle must be signed (see "Building for Apple Silicon" above for more details). The DMG file, if required, must be built after the signing:

@@ -929,71 +1055,87 @@

-
+
- + - + -
+
+
+

+ + Debugging +

+
-

- - Debugging -

-
- Debugging output — to "STDOUT" on Linux and Unix, to a "stdout.txt" file on Windows, and to the file "/tmp/tuxpaint.log" on macOS — can be enabled by setting "DEBUG" (and, if verbose logging is wanted, "VERBOSE") #defines in "src/debug.h" and (re)compiling Tux Paint.
+

+ ⚙ Debugging output — to "STDOUT" on Linux and Unix, to a "stdout.txt" file on Windows, and to the file "/tmp/tuxpaint.log" on macOS — can be enabled by setting "DEBUG" (and, if verbose logging is wanted, "VERBOSE") #defines in "src/debug.h" and (re)compiling Tux Paint.

+
-
+
+
+

+ + Uninstalling Tux Paint +

+
+ +
+
+

+ + Windows +

+
+ +
+
+

+ Using the Uninstaller

+
-

- - Uninstalling Tux Paint

- -
-

- - Windows -

-
-

Using the Uninstaller

-

If you installed the Start Menu shortcuts (the default), then go to the TuxPaint folder and select "Uninstall". A box will be displayed that will confirm that you are about to uninstall Tux Paint and, if you are certain that you want to permanently remove Tux Paint, click on the 'Uninstall' button.

When it has finished, click on the close button.

-
+
+ +
+
+

+ Using the Control Panel

+
-

Using the Control Panel

-

It is also possible to use the entry "TuxPaint (remove only)" in the Control Panel Add/Remove programs section.

-
- +
+
-
+
+
+

+ + macOS +

+
-

- - macOS -

- -

Delete "TuxPaint.app" from the "Applications" folder. Data files, including the configuration files, stamps, and saved pictures, may be found in "Library/Application Support/TuxPaint" (all users) and "/Users/USERNAME/Library/Application Support/TuxPaint" (individual users).

-
+
-
+
+
+

+ + Linux +

+
-

- - Linux -

-

Within the Tux Paint source directory (where you compiled Tux Paint), you can use the "make uninstall" target to uninstall Tux Paint. By default, this must be done by the "root" user ('superuser'), but if you installed Tux Paint somewhere else (e.g., using a "PREFIX=..." setting to "make" and "make install"), you may not, and will want to provide those same settings here. (See the installation instructions above for further information.)

-
-
+
+
diff --git a/docs/ja_JP.UTF-8/html/OPTIONS.html b/docs/ja_JP.UTF-8/html/OPTIONS.html index 09a8f39b2..19a4af737 100644 --- a/docs/ja_JP.UTF-8/html/OPTIONS.html +++ b/docs/ja_JP.UTF-8/html/OPTIONS.html @@ -21,15 +21,17 @@ } div.keeptogether { page-break-inside: avoid; } section h1 { font-size: 2em; } - h1, h2, h3, h4 { font-family: sans; } + h1, h2, h3, h4, h5 { font-family: sans; } h1 { color: #800; page-break-before: always; break-before: always; } h2 { color: #440; page-break-after: avoid; break-after: avoid; } h3 { color: #080; page-break-after: avoid; break-after: avoid; } h4 { color: #008; page-break-after: avoid; break-after: avoid; } + h5 { color: #808; page-break-after: avoid; break-after: avoid; } h1 + p { page-break-inside: avoid; } h2 + p { page-break-inside: avoid; } h3 + p { page-break-inside: avoid; } h4 + p { page-break-inside: avoid; } + h5 + p { page-break-inside: avoid; } dt { font-size: large; color: #404; diff --git a/docs/ja_JP.UTF-8/html/PNG.html b/docs/ja_JP.UTF-8/html/PNG.html index 09e5ec6cc..a005bb405 100644 --- a/docs/ja_JP.UTF-8/html/PNG.html +++ b/docs/ja_JP.UTF-8/html/PNG.html @@ -21,15 +21,17 @@ } div.keeptogether { page-break-inside: avoid; } section h1 { font-size: 2em; } - h1, h2, h3, h4 { font-family: sans; } + h1, h2, h3, h4, h5 { font-family: sans; } h1 { color: #800; page-break-before: always; break-before: always; } h2 { color: #440; page-break-after: avoid; break-after: avoid; } h3 { color: #080; page-break-after: avoid; break-after: avoid; } h4 { color: #008; page-break-after: avoid; break-after: avoid; } + h5 { color: #808; page-break-after: avoid; break-after: avoid; } h1 + p { page-break-inside: avoid; } h2 + p { page-break-inside: avoid; } h3 + p { page-break-inside: avoid; } h4 + p { page-break-inside: avoid; } + h5 + p { page-break-inside: avoid; } dt { font-size: large; color: #404; diff --git a/docs/ja_JP.UTF-8/html/README.html b/docs/ja_JP.UTF-8/html/README.html index 7bfc78e4e..fb0ffae27 100644 --- a/docs/ja_JP.UTF-8/html/README.html +++ b/docs/ja_JP.UTF-8/html/README.html @@ -21,15 +21,17 @@ } div.keeptogether { page-break-inside: avoid; } section h1 { font-size: 2em; } - h1, h2, h3, h4 { font-family: sans; } + h1, h2, h3, h4, h5 { font-family: sans; } h1 { color: #800; page-break-before: always; break-before: always; } h2 { color: #440; page-break-after: avoid; break-after: avoid; } h3 { color: #080; page-break-after: avoid; break-after: avoid; } h4 { color: #008; page-break-after: avoid; break-after: avoid; } + h5 { color: #808; page-break-after: avoid; break-after: avoid; } h1 + p { page-break-inside: avoid; } h2 + p { page-break-inside: avoid; } h3 + p { page-break-inside: avoid; } h4 + p { page-break-inside: avoid; } + h5 + p { page-break-inside: avoid; } dt { font-size: large; color: #404; diff --git a/docs/ja_JP.UTF-8/html/SIGNALS.html b/docs/ja_JP.UTF-8/html/SIGNALS.html index 70374ddf2..02647529a 100644 --- a/docs/ja_JP.UTF-8/html/SIGNALS.html +++ b/docs/ja_JP.UTF-8/html/SIGNALS.html @@ -21,15 +21,17 @@ } div.keeptogether { page-break-inside: avoid; } section h1 { font-size: 2em; } - h1, h2, h3, h4 { font-family: sans; } + h1, h2, h3, h4, h5 { font-family: sans; } h1 { color: #800; page-break-before: always; break-before: always; } h2 { color: #440; page-break-after: avoid; break-after: avoid; } h3 { color: #080; page-break-after: avoid; break-after: avoid; } h4 { color: #008; page-break-after: avoid; break-after: avoid; } + h5 { color: #808; page-break-after: avoid; break-after: avoid; } h1 + p { page-break-inside: avoid; } h2 + p { page-break-inside: avoid; } h3 + p { page-break-inside: avoid; } h4 + p { page-break-inside: avoid; } + h5 + p { page-break-inside: avoid; } dt { font-size: large; color: #404; diff --git a/docs/ja_JP.UTF-8/html/SVG.html b/docs/ja_JP.UTF-8/html/SVG.html index 0d047e4c3..5f0d5d98a 100644 --- a/docs/ja_JP.UTF-8/html/SVG.html +++ b/docs/ja_JP.UTF-8/html/SVG.html @@ -21,15 +21,17 @@ } div.keeptogether { page-break-inside: avoid; } section h1 { font-size: 2em; } - h1, h2, h3, h4 { font-family: sans; } + h1, h2, h3, h4, h5 { font-family: sans; } h1 { color: #800; page-break-before: always; break-before: always; } h2 { color: #440; page-break-after: avoid; break-after: avoid; } h3 { color: #080; page-break-after: avoid; break-after: avoid; } h4 { color: #008; page-break-after: avoid; break-after: avoid; } + h5 { color: #808; page-break-after: avoid; break-after: avoid; } h1 + p { page-break-inside: avoid; } h2 + p { page-break-inside: avoid; } h3 + p { page-break-inside: avoid; } h4 + p { page-break-inside: avoid; } + h5 + p { page-break-inside: avoid; } dt { font-size: large; color: #404;