kopia lustrzana https://gitlab.com/sane-project/backends
2000-11-12 Henning Meier-Geinitz <hmg@gmx.de>
* doc/sane.tex: Fixed a typo. * doc/.cvsignore: Added the files produced by make ps. * README: Removed X-frontends. Point to sane-frontends and website. Some reformatting. * TODO: Updated concerning frontends split. * PROJECTS: Removed entries about frontends (now in sane-frontends/README) * PROBLEMS: Removed entries about frontends (now in sane-frontends/PROBLEMS)DEVEL_2_0_BRANCH-1
rodzic
4f0b378b80
commit
7306f94ea7
7
PROBLEMS
7
PROBLEMS
|
@ -1,4 +1,4 @@
|
|||
Last update: Sun Jul 30 22:24:27 CEST 2000
|
||||
Last update: Sun Nov 12 16:47:01 CET 2000
|
||||
|
||||
- Compiling SANE aborts with error "virtual memory exhausted" on Slackware
|
||||
linux with gcc. What goes wrong?
|
||||
|
@ -49,11 +49,6 @@ Last update: Sun Jul 30 22:24:27 CEST 2000
|
|||
SG_BIG_BUFF from /proc/sys/kernel/sg-big-buff which is
|
||||
available with newer linux kernels (>= v2.2).
|
||||
|
||||
- xscanimage/xcam crashes X server on Linux/Alpha
|
||||
Older versions of the TGA X server (such as version 3.1.2) are known
|
||||
to fail when creating shared images of certain sizes. This can be
|
||||
avoided by invoking xscanimage and xcam with option --no-shm.
|
||||
|
||||
- Missing /usr/include/scsi on Linux systems
|
||||
Older Linux distributions are missing the /usr/include/scsi directory.
|
||||
In such a case, it is necessary to copy the relevant files from
|
||||
|
|
19
PROJECTS
19
PROJECTS
|
@ -1,10 +1,10 @@
|
|||
Sat Aug 5 17:57:45 CEST 2000
|
||||
Sun Nov 12 16:44:11 CET 2000
|
||||
|
||||
Here is a list of projects that various people have expressed interest
|
||||
in. Before starting working on one of these projects, it may be a
|
||||
good idea to get in touch with the relevant people. Please also read
|
||||
the files AUTHORS and README for projects that are included into the
|
||||
SANE-package.
|
||||
SANE-package. For frontends, look at the sane-frontends package.
|
||||
|
||||
Status description
|
||||
--------- ----------------------------------------------------------------
|
||||
|
@ -13,21 +13,6 @@ planned Only plans but no code yet.
|
|||
wip Work in progress. There is (more or less) working code. For details,
|
||||
look at the web page or contact the author.
|
||||
|
||||
|
||||
Frontends:
|
||||
----------
|
||||
|
||||
sanecgi: web interface to all SANE-compatible scanners (wip)
|
||||
http://www.boutell.com/sanecgi/
|
||||
|
||||
scanadf: a command-line frontend that offers additional capabilities that are
|
||||
suited towards document scanners with automatic document feeders (wip)
|
||||
http://www.martoneconsulting.com/sane-scanadf.html
|
||||
|
||||
xsane (wip)
|
||||
http://www.wolfsburg.de/~rauch/sane/sane-xsane.html
|
||||
|
||||
|
||||
Backends:
|
||||
---------
|
||||
|
||||
|
|
80
README
80
README
|
@ -17,31 +17,21 @@ In order to build SANE, the following tools and libraries are required:
|
|||
- ANSI C compiler: GNU C (gcc) is recommended for best performance,
|
||||
but any ANSI-compliant compiler should do
|
||||
|
||||
- To build the graphical frontends (xscanimage and xcam), it is
|
||||
necessary to have the GTK libraries (libgtk, libgdk, and
|
||||
libglib) and associated header files installed. In
|
||||
addition, if you want to use xscanimage from within GIMP,
|
||||
you'll need to make sure libgimp (version 0.99.13 or newer)
|
||||
and its header files are installed as well. The GTK libraries and
|
||||
GIMP can be obtained from:
|
||||
|
||||
ftp://ftp.gimp.org/pub/
|
||||
|
||||
SANE should build on most Unix-like systems. Support for OS/2 is also
|
||||
available. For more details look at the operating system specific
|
||||
README.* files. For a detailed support matrix, see:
|
||||
available. For more details look at the operating system specific README.*
|
||||
files. For a detailed support matrix, see:
|
||||
|
||||
http://www.mostang.com/sane/sane-support.html
|
||||
|
||||
This table may be out of date. Please send any corrections or additions
|
||||
to sane-devel@mostang.com together with your platform, os and version.
|
||||
This table may be out of date. Please send any corrections or additions to
|
||||
sane-devel@mostang.com together with your platform, os and version.
|
||||
|
||||
|
||||
Configuration
|
||||
=============
|
||||
|
||||
Simply invoke configure in the top-level directory. Besides the usual
|
||||
GNU configure options, there are the following SANE specific options:
|
||||
Simply invoke configure in the top-level directory. Besides the usual GNU
|
||||
configure options, there are the following SANE specific options:
|
||||
|
||||
--disable-shared
|
||||
Don't use shared libraries. Useful for debugging or when there
|
||||
|
@ -107,9 +97,7 @@ below:
|
|||
----------------- ------------------------------------------
|
||||
Frontends:
|
||||
scanimage scanimage(1)
|
||||
xscanimage xscanimage(1)
|
||||
saned saned(1)
|
||||
xcam xcam(1)
|
||||
|
||||
Backends for scanners:
|
||||
Abaton sane-abaton(5)
|
||||
|
@ -151,28 +139,32 @@ below:
|
|||
Networking sane-net(5) and saned(1)
|
||||
SCSI configuration sane-scsi(5)
|
||||
|
||||
For more details on supported scanners and cameras look at the SANE
|
||||
website: http://www.mostang.com/sane/sane-backends.html
|
||||
For more details on supported scanners and cameras look at the SANE website:
|
||||
http://www.mostang.com/sane/sane-backends.html.
|
||||
|
||||
Please note that the default configuration uses sane-dll as the
|
||||
top-level backend. Hence it is probably a good idea to start with
|
||||
reading sane-dll(5). The top-level backend is determined by the
|
||||
libsane.* symlinks in /usr/local/lib/.
|
||||
Concerning frontends (applications): Starting from SANE 1.0.4, only scanimage
|
||||
is included in the package. Some of the available frontends can be found in
|
||||
the separate package sane-frontends. For more information about frontends and
|
||||
where to get them look at http://www.mostang.com/sane/sane-frontends.html.
|
||||
|
||||
Please note that the default configuration uses sane-dll as the top-level
|
||||
backend. Hence it is probably a good idea to start with reading sane-dll(5).
|
||||
The top-level backend is determined by the libsane.* symlinks in
|
||||
/usr/local/lib/.
|
||||
|
||||
For SCSI scanners reading of sane-scsi(5) is recommended.
|
||||
|
||||
Please also read the file PROJECTS for projects that are planned or
|
||||
not yet included into the SANE distribution.
|
||||
Please also read the file PROJECTS for projects that are planned or not yet
|
||||
included into the SANE distribution.
|
||||
|
||||
If you encounter any problems with getting your device(s) recognized,
|
||||
try setting the various environment variables that are there to assist
|
||||
in debugging such problems. The environment variables are documented
|
||||
in the relevant manual pages. For example, to get the maximum amount
|
||||
of debug information when testing a Mustek scanner, set environment
|
||||
variables SANE_DEBUG_DLL, SANE_DEBUG_MUSTEK, and SANE_DEBUG_SANEI_SCSI
|
||||
to 128 and then invoke scanimage or whatever program you're trying to
|
||||
debug. For a Mustek scanner at /dev/scanner, you might want to invoke
|
||||
scanimage as follows:
|
||||
If you encounter any problems with getting your device(s) recognized, try
|
||||
setting the various environment variables that are available to assist in
|
||||
debugging such problems. The environment variables are documented in the
|
||||
relevant manual pages. For example, to get the maximum amount of debug
|
||||
information when testing a Mustek scanner, set environment variables
|
||||
SANE_DEBUG_DLL, SANE_DEBUG_MUSTEK, and SANE_DEBUG_SANEI_SCSI to 128 and then
|
||||
invoke scanimage or whatever program you're trying to debug. For a Mustek
|
||||
scanner at /dev/scanner, you might want to invoke scanimage as follows:
|
||||
|
||||
scanimage -d mustek:/dev/scanner -h
|
||||
|
||||
|
@ -180,22 +172,20 @@ If this works, you could try to acquire an image with:
|
|||
|
||||
scanimage -d mustek:/dev/scanner >t.pnm
|
||||
|
||||
If you are not sure what generic SCSI device your scanner is connected
|
||||
to, try the command tools/find-scanner. It is normally sufficient to
|
||||
invoke the program without any arguments. Invoking this command
|
||||
should produce output similar to this:
|
||||
If you are not sure what generic SCSI device your scanner is connected to, try
|
||||
the command tools/find-scanner. It is normally sufficient to invoke the
|
||||
program without any arguments. Invoking this command should produce output
|
||||
similar to this:
|
||||
|
||||
$ tools/find-scanner
|
||||
find-scanner: found "MUSTEK MFC-06000CZ 1.01" at device /dev/scanner
|
||||
find-scanner: found "MUSTEK MFC-06000CZ 1.01" at device /dev/sge
|
||||
|
||||
Note that find-scanner will find any scanner that is connected to a
|
||||
SCSI bus. It will even find scanners that are not supported at all
|
||||
by SANE.
|
||||
Note that find-scanner will find any scanner that is connected to a SCSI bus.
|
||||
It will even find scanners that are not supported at all by SANE.
|
||||
|
||||
There may be several causes for the following messages from the
|
||||
frontends: "scanimage: no SANE devices found" or "xscanimage: no
|
||||
devices available.".
|
||||
There may be several causes for the following messages from the frontends:
|
||||
"scanimage: no SANE devices found" or "xscanimage: no devices available.".
|
||||
|
||||
* Your scanner is not recognized by any backend. It is not supported.
|
||||
You may ask the maintainer of your backend (see AUTHORS) or
|
||||
|
|
|
@ -14,7 +14,7 @@
|
|||
|
||||
\title{\huge SANE Standard Version 1.01}
|
||||
\author{}
|
||||
\date{October 17, 2000}
|
||||
\date{November 12, 2000}
|
||||
|
||||
\makeindex
|
||||
|
||||
|
@ -555,7 +555,7 @@ characters is currently fixed as ISO LATIN-1. Future versions of this
|
|||
standard may map this type to a wider type and allow multi-byte
|
||||
encodings to support internationalization. As a result of this, care
|
||||
should be taken to avoid the assumption that
|
||||
\verb|sizeof(SANE\_Char)==sizeof(char)|.
|
||||
\verb|sizeof(SANE_Char)==sizeof(char)|.
|
||||
\begin{quote}
|
||||
\begin{verbatim}
|
||||
typedef char SANE_Char;
|
||||
|
|
Ładowanie…
Reference in New Issue