Yes, you will have problems compiling against the latest development
GIMP.
A temporary fix is to insert
#define GIMP_ENABLE_COMPAT_CRUFT
into frontends/xscanimage.c
Xsane also suffers similarly. The problem in both cases is that
the Gimp API changed a long time ago, but now the default is
to disable the old API unless you specifically enable it.
Defining GIMP_ENABLE_COMPAT_CRUFT is only temporary - apparently
once gimp 1.2 is out, the next development release (1.3.x) will
remove the old API altogether, so someone(?) will have to go through
xsane/xscanimage and re-code all the API calls (mostly a global
editing job), which will stop it compiling with Gimp 1.0.4.
Temporary Patches attached.
Dave Hill
--Dave Hill, Kempston, Bedford UK dave@minnie.demon.co.uk davehill at users.sourceforge.net Sicth munce ago, I cutn't evun spel enjuneer, and now I are one!
--- sane-1.0.3_20000824/frontend/xscanimage.c.orig Tue Aug 22 22:08:41 2000 +++ sane-1.0.3_20000824/frontend/xscanimage.c Tue Sep 26 07:31:32 2000 @@ -56,7 +56,7 @@ #define OUTFILENAME "out.pnm" #ifdef HAVE_LIBGIMP_GIMP_H - +#define GIMP_ENABLE_COMPAT_CRUFT #include <libgimp/gimp.h> static void query (void);
--- xsane-0.60/src/xsane.h.orig Thu Jul 13 21:15:30 2000 +++ xsane-0.60/src/xsane.h Sun Sep 24 18:04:13 2000 @@ -113,6 +113,7 @@ /* ---------------------------------------------------------------------------------------------------------------------- */ #ifdef HAVE_LIBGIMP_GIMP_H +#define GIMP_ENABLE_COMPAT_CRUFT # include <libgimp/gimp.h> # ifdef HAVE_LIBGIMP_GIMPFEATURES_H
-- Source code, list archive, and docs: http://www.mostang.com/sane/ To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com
This archive was generated by hypermail 2b29 : Tue Sep 26 2000 - 12:49:46 PDT