On Wed, Oct 16, 2002 at 10:16:46PM +0100, Major A wrote:
> Can't you just check for the existence of certain symbols in the
> gphoto2 library etc.? Maybe that would be a better idea than
> maintaining a list of version strings...
Unfortunately, at the time I was having these problems, it wasn't t
> They did it again!?!? gphoto2 has been pretty frustrating. For
> a while, the API was changing on a weekly basis, and gphoto2 backend had
> to scramble to keep up. Whenever the API changed, I had to modify the
> code, and change the configure script to check just for those specific
> version
They did it again!?!? gphoto2 has been pretty frustrating. For
a while, the API was changing on a weekly basis, and gphoto2 backend had
to scramble to keep up. Whenever the API changed, I had to modify the
code, and change the configure script to check just for those specific
versions of the b
"configure" line 3515 of 9200
To not get the "echo "Sorry, can't use GPHOTO2"" I had to modify configure.
Maybe "gphoto2-config --version" used to give "gphoto2*" but it must have been
changed to give "libgphoto2*".
GPVERSION=`gphoto2-config --version`
case "$
Hi,
On Thu, Jan 17, 2002 at 03:12:21PM +, jim.geo...@blueyonder.co.uk wrote:
> Finally, and worst of all, if I attempt to access my scanner remotely
> gphoto2 reports the Bad Parameters error and then saned exits
saned shouldn't exit. The gphoto2 backend should just return from the sane API
c
Hi,
On Thu, Jan 17, 2002 at 03:12:21PM +, jim.geo...@blueyonder.co.uk wrote:
> Finally, and worst of all, if I attempt to access my scanner remotely
> gphoto2 reports the Bad Parameters error and then saned exits
> taking the dial-up connection with it!?
Huh? This shouldn't happen anywa
Folks,
I was successful in compiling gphoto2 support with sane (both latest
cvs versions). However I have had to unconfigure it for the following reasons.
When I specify the device on the scanimage command line it reports
[gphoto2] Camera does not support image c
