CinePaint Spot Logo by Christian Deister
| Blog | Gallery | Team | Docs | Magazines | Download | Plug-ins | SourceForge | Contact | About |

Support This Project The CinePaint Project

Downloading CinePaint

Free open source deep paint application available for Linux, Mac and BSD

by Robin Rowe

BEVERLY HILLS, CA (CinePaint.org) 10/18/2008 - CinePaint is a deep paint application that edits EXR, DPX, 16-bit TIFF, JPEG, PNG and many other types of image files. CinePaint is available as a native application for Linux, Mac OS X, and BSD. There's currently no Windows version, sorry.

Installing CinePaint on Linux

Keeping packages up to date across the many Linux distros is a challenge. If you want the latest, install from source instead.

  • CentOS
    ?
  • Debian - Currently unavailable due to maintainer issues. Should be back with next release.
    # aptitude install CinePaint
  • Gentoo
    ?
  • Mandriva
    ?
  • OpenSUSE - currently unavailable
    # yum install CinePaint
  • Puppy
    ?
  • Redhat
    # yum install CinePaint
  • Ubuntu - Currently unavailable due to Debian issues. Working on it.
    # aptitude install CinePaint

Installing CinePaint on Mac OS X

Double-click on the DMG file and drag where you wish

Installing CinePaint on BSD

You can install CinePaint for FreeBSD, OpenBSD and NetBSD.

Installing CinePaint from Source Tarball

CinePaint runs on multiple operating systems. It builds with autotools or CMake. Before you can build CinePaint, you need the dependency developer libraries installed. Each operating system and distro has somewhat different names for its developer libraries.

First, download the latest source tarball from SourceForge.net. Next unpack it:

% tar xvfz filename.gz

Installing CinePaint from Source CVS

Installing from CVS is often best. This has the latest bug fixes and features. Sometimes the CVS version won't build or has bugs because it is bleeding edge. However, it's usually fine. If you encounter a problem, post to cinepaint-developers.

  • cvs-dev.sh - Script for CinePaint developers
  • cvs-read.sh - Script for ordinary users to get CinePaint from CVS
  • ubuntu-cvs.sh - Script to install CinePaint on Ubuntu from CVS

Potentially Useful CVS Files

Building Linux CinePaint with Autotools

 $ cd cinepaint-project/cinepaint
 $ ./configure
 $ make
 # make install
 $ cinepaint

Building Linux CinePaint with CMAKE

 $ cd cinepaint-project
 $ cmake .
 $ make
 # make install
 $ cinepaint

Building CinePaint Packages

Building Mac CinePaint

See CVS for work-in-progress notes. Still ironing out how to do this cleanly. Can be built with GTK1 X11, GTK+OSX Aqua, or GTK2 Aqua.

Building Windows CinePaint

We had a Windows version, but it's currently broken. Sorry.

Version Numbers

With CinePaint, the latest version should be the best. There is no stable/unstable branch numbering.

/opt

CinePaint is installed in Linux in the traditional way sprinkled across various directories in /usr. Doing so can make CinePaint components difficult to find, and requires being root during installation. An alternative is to install as user in the directory /opt or /opt/version# if you want to install multiple versions of CinePaint side-by-side.

./configure --prefix=/opt

Configure Errors

Configure is a script that checks the proper packages are installed for CinePaint to be able to build. The autotools error messages can seem cryptic. The most common problem is trying to build CinePaint without having the "developer" copies of the necessary libraries installed. Programs that build, as opposed to those that merely are run, need versions of libraries that include the library header files. If you don't normally build programs from source you won't have those installed and will need to do so.

CinePaint Debugging

Download CinePaint from CVS. You'll want to build with debugging info and may want to place CinePaint in opt so you can keep it separate if you have the release version installed:

$ ./configure --prefix=/opt --enable-debug

Start CinePaint from a console so you can see its warning message output.

Debugging for GUI isn't so different from debugging with any 3rd party lib. You can't trace into GTK usefully.

Something that may surprise you is plug-ins are run as a separate process instead of as a dso. The original developers made it that way because they didn't trust plug-ins not to crash the program.

Posting to cinepaint-developers is preferred communication channel.

Release Manager Notes

$ make clean
$ rm -R *.gz
[ Edit configure.in to have the correct version# ]
$ sh autogen.sh
$ ./configure --prefix=/opt --enable-debug --with-openexr-prefix=/opt --enable-openexrtest
[by the way, this needs to display version#, makes cinepaint.spec from cinepaint.spec.in]
$ make
$ make install 
$ make distcheck
$ make distclean
$ sh remove_bak.sh
$ sh remove_debug_dir.sh
$ tar cvvpzf cinepaint.x.tar.gz cinepaint.x
$ gzip -t cinepaint.x.tar.gz 
$ make rpm
$ fakeroot alien -k cinepaint-0.18.i386.rpm
# dpkg -i cinepaint_0.18_i386.deb
$ fakeroot alien -k --to-tgz cinepaint-0.18.i386.rpm

 SourceForge.net Questions to robin.rowe@cinepaint.org
Created Oct. 18, 2008; updated Oct. 22, 2008