Not true.  I'm a software developer at Rhythm and Hues.  We're 
actively maintaining and developing the 16bit GIMP for use in our
studio.  There is something a little funky with the autoconf/automake
setup that we never fully debugged, and the code is a little unstable
right now.

There are a couple of extra steps because of the weirdness, but it can be
built:

aclocal;
automake -a;
autoconf;
./configure --disable-shared --disable-debug --bindir=<blah>
--datadir=<blah> --prefix=<directory above include directory>
--exec-prefix=<directory above bin which contains gnu tools>;
ltconfig --disable-shared ltmain.sh; # have to do this separately for some
reason
gmake all;

New features include things like improved UI, frame manager for editing
and painting on multiple frames from an animation clip, and save/restore
layout.

-Jon

On 18 Jan 2002, Sven Neumann wrote:

> Hi,
> 
> Marcin Skubiszewski <[EMAIL PROTECTED]> writes:
> 
> > Last time I checked, I was unable to autoconf;./configure the version
> > in the CVS.
> 
> as fas as I know the Hollywood GIMP branch is unmaintained. Our plan
> is to add 16bit depth per color channel and other colorspaces with
> GIMP-2.0. Development on this stuff takes place in the GEGL module
> while GIMP itself is still on the road to GIMP-1.4. This is explained
> more detailed in http://developer.gimp.org/gimp-future.
> 
> 
> Salut, Sven
> _______________________________________________
> Gimp-developer mailing list
> [EMAIL PROTECTED]
> http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
> 

_______________________________________________
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer

Reply via email to