Previous | Contents | Next
In order to compile and run mtPixy you must have several packages already present on your system:
These must also include library headers, which some operating systems provide in separate packages.
mtPixy then requires various libraries that I have created:
|libmtKit||zlib, libsqlite3||Low level C/C++ routines, including strings, UTF-8, ZIP file handling, preferences, trees, databases.|
|libmtPixy||libmtKit, libpng, libjpeg, giflib, FreeType, Pango, Cairo||The core pixel engine, including all file handling and general operations.|
|libmtPixyUI||libmtKit, libmtPixy||Toolkit agnostic UI code, e.g. undo.|
|libmtQEX||libmtKit, Qt5||Various Qt function utilities including preferences editor.|
The other optional parts of the suite have these dependencies:
|mtPixyCLI||libmtKit, libmtPixy, libmtPixyUI, readline||Command line pixel editor|
|mtPixyUtils||libmtKit, libmtPixy||Command line pixel tools|
As outlined above you must build and install the packages in this order:
In all cases you use these commands to compile the programs:
Don't forget to study the makefile and configure script before doing anything. For the complete set of configure options use:
The build system I have created uses simple hand built scripts and makefiles. I find this the best way to build the various components of the project. More elaborate systems like GNU Autotools are of no interest to me as they do not solve any problems I have (portability outside the GNU/Linux ecosystem is of no interest to me).
Once compilation is completed, use this to install (you must have root user rights):
You can change the destination directory at this stage if you are creating a package by using:
make install DESTDIR=/my/chosen/directory/
mtPixy has usage information contained in the associated man page. This can be read in the usual way using the man program, such as this example:
You can uninstall the program and libraries by using (you must have root user rights):
You will also need to remove any preferences files which are kept in the user directories such as /home/user/.config/mtpixy/prefs.txt
I aim to get my software working on as many different GNU/Linux systems as possible. To achieve this rationally without testing on hundreds of systems, I work towards compatibility with these system types: Debian, Fedora, and Arch. In doing so I will also achieve compatibility with similar systems.
To achieve these goals as quickly and as easily as possible I use various scripts in the /pkg/ directory to install and test the software (including how I package the software using native package management tools such as pacman, dpkg and rpm). The README.txt file in /pkg/ documents how I do these things, step by step.
The scripts for the different systems all do very different jobs but their interface at the command line is identical. For example to build and install on different platforms using the native package management system you could use:
./build_arch.sh --preconf "CC=clang" ./build_debian.sh --conf "debug" ./build_fedora.sh --conf "--libdir=/usr/lib64"
If your system doesn't use pacman, dpkg, or rpm then you can always use the classic ./configure, make, make install based script using the same arguments:
./build_install.sh --preconf "CC=clang" --conf "--libdir=/usr/lib64"
And if you want to remove all of the installed packages from your system, just use one of these:
./build_arch.sh remove ./build_debian.sh remove ./build_fedora.sh remove ./build_install.sh remove
Here are the options that are available to these 4 scripts:
|flush||Clear out the temporary files after a compilation.|
|remove||Remove all installed files from a previous build and install.|
|--preconf ARG||Add environment variable settings such as CC or CFLAGS.|
|--conf ARG||Pass arguments to the configure script such as --libdir or debug.|
|--bcfile ARG||If you want to pass different configure lines to different packages you would use a custom built bcfile. See /pkg/ for a few examples example of this. When using --bcfile the options --preconf and --conf do nothing.|
Normally all of the different packages are built in sequence. However you can also pass specific package names to build and install just those items, such as:
./build_install.sh libmtkit libmtpixy
To remove these items you would use:
./build_install.sh libmtkit libmtpixy remove
Previous | Contents | Next