home contents changes options help

by Robin Rowe 11/20/02

Typical users building CinePaint follow this procedure:

 $ ./configure
 $ make
 # make install
 $ cinepaint

Version Numbers

The naming convention for CinePaint versions is to number sequentially x.x (e.g., 0.3 is the third release). This is a simpler scheme than GIMP, that uses a triple x.x.x numbering methodology similar to the Linux kernel. With CinePaint, the latest version should be the best. There is no stable/unstable branch numbering. Using a different naming format avoids confusion between CinePaint and GIMP version numbers.


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. Sometimes the error messages seem a little 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.

Each operating system distro may have somewhat different names for its developer libraries, but not too different. Here are the needed libraries for different distributions.



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

Questions to rower@movieeditor.com Created November 20, 2002; updated July 27, 2003


Not finding installed libs -- Tue, 07 Jun 2005 14:28:14 -0700 reply

my Redhat workstation 3 should be able to build this. i have gtk+-1.2.10-31 already installed, so why is the configure not finding it?

Probably because you have gtk1 installed but not gtk1-devel.

For compiling programs, as opposed to simply running them, you need the developer libs. If you installed RH from the full disk set the dev libs you need should be included somewhere, but may not be installed by default. If installed from a minimal CD or net you can use urpmi or a similar tool to fetch and install it. Or, go to http://www.userfriendly.net/rpmfinder.html and search on gtk1 to download the rpm manually.