[sane-devel] backend naming conventions/constraints

2003-03-01 Thread Olaf Meeuwissen
Henning Meier-Geinitz writes: > On Fri, Feb 28, 2003 at 08:50:44PM +0900, Olaf Meeuwissen wrote: > > I tried getting things to work with a hyphenated backend name, but to > > no avail. The dll backend uses the literal name in dll.conf to check > > for functions in the backend :-( > > What would

[sane-devel] backend naming conventions/constraints

2003-02-28 Thread Olaf Meeuwissen
I tried getting things to work with a hyphenated backend name, but to no avail. The dll backend uses the literal name in dll.conf to check for functions in the backend :-( Here's part of the output of running iscan with SANE_DEBUG_DLL=128: [dll] load: dlopen()ing `/usr/lib/sane/libsane-epson-ko

[sane-devel] backend naming conventions/constraints

2003-02-28 Thread Henning Meier-Geinitz
Hi, On Fri, Feb 28, 2003 at 08:50:44PM +0900, Olaf Meeuwissen wrote: > I tried getting things to work with a hyphenated backend name, but to > no avail. The dll backend uses the literal name in dll.conf to check > for functions in the backend :-( What would be the alternative? How should it get

[sane-devel] backend naming conventions/constraints

2003-02-28 Thread Olaf Meeuwissen
Hi, Henning Meier-Geinitz writes: > On Thu, Feb 27, 2003 at 09:16:35AM +0900, Olaf Meeuwissen wrote: > > Yup, backends/Makefile.in uses > > > > %-s.lo: %-s.c > > @$(LIBTOOL) $(MCOMP) $(COMPILE) -DSTUBS -DBACKEND_NAME=$* $< > > > > %.lo: %.c > > @$(LIBTOOL) $(MCOMP) $(C

[sane-devel] backend naming conventions/constraints

2003-02-27 Thread Henning Meier-Geinitz
Hi, On Thu, Feb 27, 2003 at 09:16:35AM +0900, Olaf Meeuwissen wrote: > Yup, backends/Makefile.in uses > > %-s.lo: %-s.c > @$(LIBTOOL) $(MCOMP) $(COMPILE) -DSTUBS -DBACKEND_NAME=$* $< > > %.lo: %.c > @$(LIBTOOL) $(MCOMP) $(COMPILE) -DBACKEND_NAME=$* \ > -

[sane-devel] backend naming conventions/constraints

2003-02-27 Thread Olaf Meeuwissen
Henning Meier-Geinitz writes: > On Wed, Feb 26, 2003 at 03:12:24PM +0900, Olaf Meeuwissen wrote: > > Silly question but are there any constraints on the name of a backend? > > It shouldn't be too long, but epson_kowa is ok in this respect. It > shouldn't contain any characters that can't be used

[sane-devel] backend naming conventions/constraints

2003-02-26 Thread Olaf Meeuwissen
Hi, Silly question but are there any constraints on the name of a backend? I am in the middle of switching "Image Scan!"s backend from epson to epson-kowa and ran into the BACKEND_NAME macro ;-) Is there any harm in calling the backend library libsane-epson-kowa.* while defining the macro to epso

[sane-devel] backend naming conventions/constraints

2003-02-26 Thread Henning Meier-Geinitz
Hi, On Wed, Feb 26, 2003 at 03:12:24PM +0900, Olaf Meeuwissen wrote: > Silly question but are there any constraints on the name of a backend? It shouldn't be too long, but epson_kowa is ok in this respect. It shouldn't contain any characters that can't be used in the filesystem. And it should be