# Re: sane-0.62 released

David Mosberger-Tang (davidm@azstarnet.com)
Sun, 27 Jul 1997 08:21:45 -0700

- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
- Next message: David Mosberger: "Re: Problems with xscanimage"
- Previous message: David Mosberger-Tang: "Re: sane-0.62 released"
- In reply to: Rogier Wolff: "Re: sane-0.62 released"
- Next in thread: becka@sunserver1.rz.uni-duesseldorf.de: "Re: sane-0.62 released"
- Reply: becka@sunserver1.rz.uni-duesseldorf.de: "Re: sane-0.62 released"

>>>>> On Sun, 27 Jul 1997 13:57:46 +0200 (MET DST), R.E.Wolff@BitWizard.nl (Rogier Wolff) said:

Rogier> David Mosberger-Tang wrote:

>> I'd appreciate if people could give it a shot and let me know if
>> there is anything that's confusing with respect to building and
>> installing SANE.

Rogier> I'll figure it out by myself in the following few hours, but
Rogier> I would have appreciated something in the doc about making a
Rogier> static "scanimage-mustek" (Actually I need
Rogier> scanimage-tamarack :-). It might be nice to simply build
Rogier> that binary (as an example for people developing a backend
Rogier> like me), but not install it, as the dll-version is actually
Rogier> more useful.

Rogier> As far as I understand the framework, this would be easy to
Rogier> make.

Are you asking for a statically linked frontend that includes just one
backend or are you simply looking for an easy way to debug backends
(without having to deal with dynamic loading etc.)?

If it's the latter, you can simply invoke ./configure with option
--disable-shared. Not only does this turn off shared libraries, but
implicitly it also turns off dynamic loading. This means that all
backends will be preloaded into dll and nothing dynamic will happen.

If you want to bypass dll completely, simply replace the libsane.a
symlink by a symlink that points to libsane-tamarack.a (and build with
"./configure --disable-shared)."

I'll think about adding more info on this, though I'm kind of
reluctant to burden the "casual" user with it since it's something
that's likely to be relevant for developers only. Maybe I should add
a seperate "developers only" section to the README.

>> This means that no other SCSI device on the same bus can be
>> accessed while a scan is in progress. With
Rogier> ^^^^ ????

Duh, I must have gotten distracted by lunch or something... ;-)
I fixed that now---thanks for catching it!

>> Transparency adapter and automatic document feeder support is
>> severly lacking (due to absence of equipment to test this with).

Rogier> I saw lots of references to the transparency bits in the
Rogier> backend. Is the documentation outdated, or has that simply
Rogier> not been tested....

Rogier> I have a transparency adapter. It is pretty simple: the bit
Rogier> in the doc labelled "transparency adapter" turns the
Rogier> external light-source on, and the internal one off. Simple.

Rogier> I'm simply making a boolean SANE_OPTION that toggles this
Rogier> bit.

It's probably easy to add whatever transparancy-adapter support is
missing in the Mustek backend. But since I have never seen such a
beast, I couldn't debug it myself, so I didn't bother spending time on
something that may not work at all. So, the docs are not out of date,
but as you say, the TA support is probably easy to get working.

--david

    --
    Source code, list archive, and docs: http://www.azstarnet.com/~axplinux/sane/
    To unsubscribe: mail -s unsubscribe sane-devel-request@listserv.azstarnet.com

- Next message: David Mosberger: "Re: Problems with xscanimage"
- Previous message: David Mosberger-Tang: "Re: sane-0.62 released"
- In reply to: Rogier Wolff: "Re: sane-0.62 released"
- Next in thread: becka@sunserver1.rz.uni-duesseldorf.de: "Re: sane-0.62 released"
- Reply: becka@sunserver1.rz.uni-duesseldorf.de: "Re: sane-0.62 released"