[sane-devel] LIDE 60. configure scanner - Mac Terminal
greenb1 at mac.com
Wed Feb 16 00:33:32 UTC 2011
Look I've done some poking around to implement these changes that you stated - its a bit like an elephant with a bazooka in a china shop.
I have libsub installed and the backends. I've gone through M. Ellerts site - but it only takes you through simple command-line scanning.
What I cant get into is the genesys_devices.c file.. From the abandoned backend help pages of Henning Meier-Geinitz they state there are three files in the backend..
The backend configuration file (see also description of SANE_CONFIG_DIR below).
The static library implementing this backend.
The shared library implementing this backend (present on systems that support dynamic loading).
Is one of these files the genesys_devices.c file you are taliking about? Or is it inside one of these files? If so - can I use "emac" in terminal to pull up the flagged file and change it?
Also, do you know the equivalent of 'make' and 'run' in terminal?
On 11 Feb 2011, at 21:25, m. allan noah wrote:
> Stop talking about prefs. We are talking about source code :)
> I've never compiled sane on a mac before (M. Ellert might have more
> about that on his site) But i can give you the general idea:
> 1. install the libusb-dev package (or libusb-devel, not sure what your
> OS calls it)
> 2. install gcc package and it's required dependencies (and 'make' too)
> 3. download latest sane-backends from http://www.sane-project.org/snapshots/
> 4. tar xzf sane-backends......tgz
> 6. cd sane-backends.....
> 7. edit the lide_60 section of the genesys_devices.c file. You'll see
> the flags in there.
> 8. run (all on one line):
> BACKENDS=genesys ./configure --prefix=/usr --sysconfdir=/etc --disable-locking
> 9. make (then wait awhile)
> 10. copy the file backend/.libs/libsane-genesys.so.1.0.22 over top of
> the copy provided by your distro, not sure where it is on a Mac.
> You can save the old one before you overwrite it if you want.
> 11. test with scanimage or xsane and various options.
> Only step #10 needs to be done as root.
> Now, those are basically Linux directions, and I'm sure the Mac has
> lots of differences, others might chime in here :)
> On Fri, Feb 11, 2011 at 4:12 PM, Ben Green <greenb1 at mac.com> wrote:
>> Allan, Thanks very much - Following is a lot of "How to" questions?
>> I can't try any of this now as I have to go to work - but I'll try these suggestions later tonight -
>> Just to clarify (here's my programming prowess coming to the fore!) -
>> This is all done in terminal (not sane prefs?) --
>> How do I open this file : backend/genesys_devices.c ?
>> once i see this file - it might make it all more clear for me..
>> How do I set GENESYS_FLAG_NO_CALIBRATION?
>> How do I remove existing flags?
>> and how do I rebuild the backend?
>> once this is done, I can scan again from the TWAIN-SANE interface (without calibration)? as this code will affect the actual backend coding is that correct?
>> ALso - if i screw it all up, can i re-insall and start again?
>> Thanks a million for your help -- I'm never sure if these things work, but there's only one way to find out ..
>> On 11 Feb 2011, at 20:46, m. allan noah wrote:
>>> I did a bit of digging in the source, and it appears that you could
>>> set GENESYS_FLAG_NO_CALIBRATION in the Lide60 entry in
>>> backend/genesys_devices.c (along with removing the existing
>>> calibration flags), and rebuild sane-backends. That should bypass the
>>> calibration code.
>>> On Fri, Feb 11, 2011 at 3:34 PM, m. allan noah <kitno455 at gmail.com> wrote:
>>>> On Fri, Feb 11, 2011 at 3:18 PM, Ben Green <greenb1 at mac.com> wrote:
>>>>> Fair enough Allan, it's not much use just putting out vague questions really
>>>>> i'm sure its still possible, i just need to find the way!!
>>>> You have no clue how to use the command line or write code, yet you
>>>> are sure this scanner is suitable :)
>>>> Many scanners do the calibration automatically, and will choke when
>>>> you gut them like this. Fortunately, the Genesys chips require the
>>>> software to initialize the calibration, so it should be possible to
>>>> bypass that. Unfortunately, the data will look bad. You really need to
>>>> do a scan with the assembled scanner, and cache the calibration
>>>> values, like genesys backend does for ADF machines. Then you could
>>>> re-use that calibration data.
>>>> You might have to hack some code to make these things happen.
>>>> "The truth is an offense, but not a sin"
>>> "The truth is an offense, but not a sin"
> "The truth is an offense, but not a sin"
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the sane-devel