scanimage -L does not load my backend

On Mon, 2006-08-14 at 21:30 -0700, Tabor Kelly wrote:
> I am in the process of writing a backend for my CANON
CanoScan FS2720U 
> slide and film scanner. My backend is no where near
functional, but I 
> noticed that if I run 'scanimage -L' my backend is
not loaded. However, 
> if I run 'scanimage -d canonfs2720u' my backend is
loaded. What am I 
> missing?
I think you need to add your backend name to your
/etc/sane.d/dll.conf
file.

HTH


-- 
sane-devel mailing list: sane-devellists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/sane-d
evel
Unsubscribe: Send mail with subject "unsubscribe
your_password"
             to sane-devel-requestlists.alioth.debian.org

James Liggett wrote:
> On Mon, 2006-08-14 at 21:30 -0700, Tabor Kelly wrote:
> 
>>I am in the process of writing a backend for my
CANON CanoScan FS2720U 
>>slide and film scanner. My backend is no where near
functional, but I 
>>noticed that if I run 'scanimage -L' my backend is
not loaded. However, 
>>if I run 'scanimage -d canonfs2720u' my backend is
loaded. What am I 
>>missing?
> 
> I think you need to add your backend name to your
/etc/sane.d/dll.conf
> file.
> 
> HTH
> 

Excellent. I had actually done that in my build directory, I
guess 'make 
install' will not overwrite existing .conf files (for good
reason).

Thanks,

Tabor


-- 
sane-devel mailing list: sane-devellists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/sane-d
evel
Unsubscribe: Send mail with subject "unsubscribe
your_password"
             to sane-devel-requestlists.alioth.debian.org

Hi Tabor,

On Mon, 14 Aug 2006, Tabor Kelly wrote:
> Excellent. I had actually done that in my build
directory, I guess 'make 
> install' will not overwrite existing .conf files (for
good reason).

Out of interest: when you mention your build directory, do
you mean the 
directory structure created when you unzip the package (or
cvs checkout) 
or do you mean an alternative build directory such as one
created by 
kdevelop?

If the latter, then I have also found that the conf files do
not get 
installed.  The reason is that in backend/Makefile(.in) the
source 
directory for the <backend>.conf is specified:

install-becfg:
 	list="$(CONFIGS)"; for cfg in $$list; do
\
 	  if test ! -r $(srcdir)/$$; then continue; fi; \
 	  if test -f $(DESTDIR)$(configdir)/$$; then \
 	    echo NOT overwriting $$ in $(configdir)...; \
 	  else \
 	    echo installing $$ in $(configdir)/$$...; \
 	    $(INSTALL_DATA) $(srcdir)/$$ 
$(DESTDIR)$(configdir)/$$ \
               || exit 1; \
 	  fi; \
 	done
If your working directory is elsewhere then your
<backend>.conf files will 
have been generated in the current directory, not in
$(srcdir).

This can be rectified by replacing  $(srcdir)/$$ with
$$ in the 
above rule.

Unless someone can see a downside to doing this then I will
make this 
modification and check it in?

cheers,
Jon

====================== Jon Chambers =====================
  http://www.jon.demon.co.uk
, 020 8575 7097, 07931 961669
=========================================================

-- 
sane-devel mailing list: sane-devellists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/sane-d
evel
Unsubscribe: Send mail with subject "unsubscribe
your_password"
             to sane-devel-requestlists.alioth.debian.org