Re: CMake update

Michel,

Thank you for the CMake info. Would you mind copying that and expanding 
on it as a README.CMake how-to file for programmers who want to add a 
file or plug-in to CinePaint? Put it in the cinepaint-project directory.

Don't forgot to add description, copyright and license info to the top 
of each of the files you've added, something like this...

Description: CMake build file that creates most plug-ins except OpenEXR
Copyright 2008/03/01 Michel Lesoinne <[email protected]>
License: BSD <http://opensource.org/licenses/bsd-license.php>

> With the exception of openexr, all the plug-ins are configured inside
> the plug-ins/CMakeList.txt
> A simple example is:
> 
> ADD_EXECUTABLE(sgi sgi/sgi.c  sgi/sgilib.c)
> TARGET_LINK_LIBRARIES(sgi lib wire ${GTK_LIBRARIES})

I thought you might need a CMakeList.txt in each plug-in directory, like 
Makefile.am. If you had a plug-ins/blur/CMakeList.txt for blur, for 
example, I could write a little Perl script to iterate across the 
plug-in directories and write CMakeList.txt files. (I created something 
like that to generate VC++ project files when a plug-in is added, using 
the blur project file as input.) If you can define most of the plug-ins 
in one file I guess you don't need a script.

> Looking at the installation that the "configured" based filmgimp
> installs, I see a bunch of directories
> I have not even touched: curves, gradients, palettes, patterns, scripts,
> iol  and then a few files: gimprc_user,
> gtkrc, gtkrc.forest2, printrc_user, ps-menurc, spot.splash.ppm.

CinePaint installs some settings files in the user's home directory on 
first-load. The directories contain data files. They get copied whole.

Robin
-- 
Robin Rowe
CinePaint Project Leader
Beverly Hills, California
www.CinePaint.org

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/