[sane-devel] Re: Frontends and Mac OS X

[Karl Heinz Kremer]

--17pEHd4RhPHOinZp
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sun, Oct 27, 2002 at 03:17:50PM +0100, Henning Meier-Geinitz wrote:
> Hi,
>=20
> On Sun, Oct 27, 2002 at 08:05:19AM -0500, Karl Heinz Kremer wrote:
> > Finally... I got X11 running on the iMac and did some more testing.
> > I installed XDarwin (the XF86 port to Darwin, which is the BSD base
> > Mac OS X is built on). Then I tried to intall gtk-2.0, and I=20
> > found myself in dependency hell :-) So I opted for gtk-1.2.10 instead,
> > which installed almost without problems. After that, compiling the
> > sane-frontends package was no problem anymore. It compiled, linked
> > and installed just fine. xscanimage works with the test backend.=20
>=20
> That's fine. Oliver, can you change the "???" on the platforms page to
> "yes", please?

Make it a yes(*) - with a footnote. There are problems with the preview.
In my first tests, I never brought up the preview window, and just saved
files, which I then displayed on my Linux box (so far I don't have a pnm
viewer for the Mac). The preview does however work, when I run the
appliations remotely (run on Mac and display on Linux). It is possible
that this is a problem with the the version of GTK that I'm using (1.2.10).

=2E.. and the xscanimage is too big, the scan button is off the screen.

>=20
> > I still have some problems with xsane: It needs some source tweaking
> > to make it compile, and then it requires a correction in it's
> > rc file after it is started for the first time.
>=20
> I guess Oliver is interested in the exact details :-)

As soon as I have everything figured out, I will of course forward this
information. At this time, I am still lerning. It looks like the gcc 3.2
on Darwin behaves slighly  different than what I am used to. The stringify
operator for example introduces spaces.=20

>=20
> > After that it
> > behaves the same way as it does on my Linux system (that is,=20
> > black and white scanning with the test backend results in an
> > error, but it works with the color test mode).
>=20
> I have never seen this before. But now, xsane really prints something
> about an i/o error sometimes. The fread in sane_read gets EINTR
> (interrupted system call). If I just ignore the error, xsane waits for
> ever. That problem occurs since xsane 0.87.

That's exactly what I see.=20

Karl Heinz

--=20
Karl Heinz Kremer                                  khk@khk.net
PGP Key at                 http://www.khk.net/download/khk.asc
EPSON Sane Backend:                         http://www.khk.net

--17pEHd4RhPHOinZp
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE9vAHWxejv3RfKrhsRAuY8AKCrFgCcMiJwHYydRSYFUzhikqJWJQCgl/0u
aoade0aCbULKH1o9NhbZyZM=
=xEvQ
-----END PGP SIGNATURE-----

--17pEHd4RhPHOinZp--