Bug#327043: [sane-devel] LiDE 25 issues

2005-09-08 Thread Julien BLACHE
Gerhard Jaeger [EMAIL PROTECTED] wrote:

Hi,

 well that what I was afraid of. The driver needs
 some tweaking either at the overall clock-divider settings
 or the motor-speed stuff. I have no possibility to check
 as I don't have that device.

Thanks Gerhard, maybe the submitter can do some tests ?

JB.

-- 
Julien BLACHE   http://www.jblache.org 
[EMAIL PROTECTED]  GPG KeyID 0xF5D65169


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#327043: [sane-devel] LiDE 25 issues

2005-09-08 Thread Rogier Wolff
On Thu, Sep 08, 2005 at 04:30:40PM +0200, Julien BLACHE wrote:
 Gerhard Jaeger [EMAIL PROTECTED] wrote:
 
 Hi,
 
  well that what I was afraid of. The driver needs
  some tweaking either at the overall clock-divider settings
  or the motor-speed stuff. I have no possibility to check
  as I don't have that device.
 
 Thanks Gerhard, maybe the submitter can do some tests ?

Sure, I could do that. 

One of you needs to help me a bit in how to easily and quickly compile
and test a new version. 

I have the debian sources in ~/xxx/sane-backends-1.0.16 and when I
typed something like debbuild I got a libsane_1.0.16-1_i386.deb
. However, I have the impression that if I go and change a source file
in there, and do the debbuild again, it will untar and patch the
source files again, and undo my changes. Moreover, the build takes
quite a while, even though I have a reasonably powerful
workstation. So I would like to do make somewhere, so that make
will figure out that only backends/plustek-usb.c has been changed, and
that it only needs to rebuild from there. I'm happy then manuall
copying over the .so file into my system directory.

Tell me which parameters are most likely to need tweaking 

Roger. 

-- 
** [EMAIL PROTECTED] ** http://www.BitWizard.nl/ ** +31-15-2600998 **
*-- BitWizard writes Linux device drivers for any device you may have! --*
Q: It doesn't work. A: Look buddy, doesn't work is an ambiguous statement. 
Does it sit on the couch all day? Is it unemployed? Please be specific! 
Define 'it' and what it isn't doing. - Adapted from lxrbot FAQ


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#327043: [sane-devel] LiDE 25 issues

2005-09-08 Thread Julien BLACHE
Rogier Wolff [EMAIL PROTECTED] wrote:

 One of you needs to help me a bit in how to easily and quickly compile
 and test a new version. 

 I have the debian sources in ~/xxx/sane-backends-1.0.16 and when I
 typed something like debbuild I got a libsane_1.0.16-1_i386.deb
 . However, I have the impression that if I go and change a source file
 in there, and do the debbuild again, it will untar and patch the

debuild builds the sources it finds in the current directory, and
doesn't proceed to untarring + patching the sources, so your
modifications are safe.

 source files again, and undo my changes. Moreover, the build takes
 quite a while, even though I have a reasonably powerful
 workstation. So I would like to do make somewhere, so that make

You can edit debian/rules and add BACKENDS=plustek just before
./configure (on the same line). Only the plustek backend will be
built, which will considerably speed up the build :)

 will figure out that only backends/plustek-usb.c has been changed, and
 that it only needs to rebuild from there. I'm happy then manuall
 copying over the .so file into my system directory.

cd backend  make ;) Be aware that most backends #include other .c
files, and the Makefiles currently don't take that into account. In
this case, you need to manually touch the main source file for the
backend (plustek.c in this case).

 Tell me which parameters are most likely to need tweaking 

I'll leave that part up to Gerhard :)

JB.

-- 
 Julien BLACHE - Debian  GNU/Linux Developer - [EMAIL PROTECTED] 
 
 Public key available on http://www.jblache.org - KeyID: F5D6 5169 
 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]