[sane-devel] Thoughts on compilation

[jim.george@blueyonder.co.uk]

Henning,

	thanks for this it made a great deal of difference in the compilation time
and still gave me the results I wanted.

	I know the group have taken the decision to not allow the configure option
to select which drivers are used but I have to say that the reasoning I've heard so
far doesn't stand-up at all well.

	Nevertheless with the option of removing them from the Makefile in backend
I can live with it. :)

Thanks,

Jim
On Mon, 14 Jan 2002, Henning Meier-Geinitz wrote:

> Hi,
>
> On Mon, Jan 14, 2002 at 10:21:25AM +0000, jim.george@blueyonder.co.uk wrote:
> > 	Would it not be possible to have the same option in sane so that I
> > didn't have to compile all back-ends and man pages but could instead enter
> > ./configure --with-backends=mustek_pp,pnm,gphoto2 ?  Or have I missed the
> > existing option;)?
>
> Yes and no. You can select the backends in backend/Makefile.in (before
> running configure) or backend/Makefile (after configure). See SANE FAQ:
> http://www.xs4all.nl/~ljm/SANE-faq.html#42
>
> Concerning an option for configure: The absence of this option is
> intentional. This was discussed quite some times in the past. If I
> remember correctly, the majority was of the opinion that the
> disadvantages outweigh the advantages. Not everybody knows which
> scanner is supported by which backend (yes you can read in
> sane-backends.html, but...). E.g. somebody owns a Mustek BearPaw 1200
> and may try configure --with-backends=mustek_usb (because it's a
> Mustek USB scanner). In reality, it's supported by the Plustek backend.
> So when everyone starts to compile his own collection of backends, we
> will probably get more question about "Why my scanner is not detected".
>
> Bye,
>   Henning
> _______________________________________________
> Sane-devel mailing list
> Sane-devel@www.mostang.com
> http://www.mostang.com/mailman/listinfo/sane-devel
>