i compiled sane, but not xsane.
where do i stick that #define in xsane?
On Tue, 26 Sep 2000, Dave Hill wrote:
> Date: Tue, 26 Sep 2000 07:39:17 +0100
> To: email@example.com
> From: Dave Hill <firstname.lastname@example.org>
> Reply-To: email@example.com
> Subject: Re: problems compling sane 1.0.3 xscanimage/xsane
> Yes, you will have problems compiling against the latest development
> 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 firstname.lastname@example.org
> davehill at users.sourceforge.net
> Sicth munce ago, I cutn't evun spel enjuneer, and now I are one!
-- http://www.davidcougle.com ICQ #3795561 Lunarbard on AOL(Instant Messenger) Proverbs 15:3 www.algoreisaliar.com
-- Source code, list archive, and docs: http://www.mostang.com/sane/ To unsubscribe: echo unsubscribe sane-devel | mail email@example.com
This archive was generated by hypermail 2b29 : Tue Sep 26 2000 - 22:23:57 PDT