Hello, here's a variant to make SANE 1/SANE 2 coexist in the case of dynamic linking. dll.c is modified to search for backend with a soname of 2 first, and in case of failure, it searches backend a a 1 soname. This way if an out-of-tree backend in installed, it will still be usable by a SANE 2, and automaticaly searched and found. To allow SANE 1 frontends using SANE 2 backends, there is still a sane2 meta backend that is linked and installed with a 1 soname by the SANE 2 build system. This meta backend takes care of the SANE 1/SANE 2 API differences. I have also tested that copying this libsane-sane2.so.1 library as libsane.so.1 (overwriting the one from sane-1.0.19) allowed a SANE 1 frontend to detect and use SANE 2 backends installed without prefixing the device name with 'sane2'. So by tweaking the install process of SANE 2, SANE 1 installation would be able to use SANE 2 backends without any change.
Regards, Stef -------------- next part -------------- A non-text attachment was scrubbed... Name: demo2.gz Type: application/x-gzip Size: 12163 bytes Desc: not available Url : http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20081118/18bb7ecc/attachment-0001.bin