libmypaint - MyPaint brush engine library
This is the brush library used by MyPaint. A number of other painting programs use it too.
License: ISC, see COPYING for details.
- All configurations and builds:
- json-c (>= 0.11)
- C compiler,
- Most configurations (all except
- When building from
git(developer package names vary by distribution):
--enable-gegl(GIMP does not require this):
Install dependencies (Debian and derivatives)
On recent Debian-like systems, you can type the following to get started with a standard configuration:
$ sudo apt install -y build-essential $ sudo apt install -y libjson-c-dev libgirepository1.0-dev libglib2.0-dev
When building from git:
$ sudo apt install -y python2.7 autotools-dev intltool gettext libtool
Install dependencies (Red Hat and derivatives)
The following works on a minimal CentOS 7 installation:
# yum install -y gcc gobject-introspection-devel json-c-devel glib2-devel
When building from git, you'll want to add:
# yum install -y git python autoconf intltool gettext libtool
Build and install
The traditional setup works just fine.
$ ./autogen.sh # Only needed when building from git. $ ./configure $ make install $ sudo ldconfig
We don't ship a
configure script in our git repository. If you're
building from git, you have to kickstart the build environment with:
$ git clone https://github.com/mypaint/libmypaint.git $ cd libmypaint $ ./autogen.sh
This script generates
configure.ac, after running a
few checks to make sure your build environment is broadly OK. It also
regenerates certain important generated headers if they need it.
Folks building from a release tarball don't need to do this: they will
configure script from the start.
$ ./configure $ ./configure --prefix=/tmp/junk/example
There are several MyPaint-specific options. These can be shown by running
$ ./configure --help
Once MyPaint is built, you can run the test suite and/or install it.
$ make check
This runs all the unit tests.
$ make install
Uninstall libmypaint with
Make sure that pkg-config can see libmypaint before trying to build with it.
$ pkg-config --list-all | grep -i mypaint
If it's not found, you'll need to add the relevant pkgconfig directory to
pkg-config search path. For example, on CentOS, with a default install:
$ echo PKG_CONFIG_PATH=/usr/local/lib/pkgconfig >>/etc/environment
The MyPaint project welcomes and encourages participation by everyone. We want our community to be skilled and diverse, and we want it to be a community that anybody can feel good about joining. No matter who you are or what your background is, we welcome you.
Please note that MyPaint is released with a Contributor Code of Conduct. By participating in this project you agree to abide by its terms.
Please see the file CONTRIBUTING.md for details of how you can begin contributing.
The distribution release can be generated with:
$ make dist
And it should be checked before public release with:
$ make distcheck
Contribute translations here: https://hosted.weblate.org/engage/mypaint/.
The list of languages is maintained in po/LINGUAS. Currently this file lists all the languages we have translations for. It can be regenerated with:
$ ls po/*.po | sed 's$^.*po/\([^.]*\).po$\1$' | sort > po/LINGUAS
You can also disable languages by removing them from the list if needed.
A list of files where localizable strings can be found is maintained
You can update the .po files when translated strings in the code change using:
$ cd po && make update-po
When the results of this are pushed, Weblate translators will see the new strings immediately.
Further documentation can be found in the libmypaint wiki: https://github.com/mypaint/libmypaint/wiki.