Modified:
trunk/configure.in
Log:
Make the parport-ppdev option enabled by default. This may
require giving --disable-parport-ppdev to configure on some
platform(s).
Any reason why as it breaks win32 build - why not leave as disabled by
default?
Cheers
Spen
On Tue, 2009-07-14 at 10:11 +0100, Spencer Oliver wrote:
Modified:
trunk/configure.in
Log:
Make the parport-ppdev option enabled by default. This may
require giving --disable-parport-ppdev to configure on some
platform(s).
Any reason why as it breaks win32 build - why
On Tue, 2009-07-14 at 10:11 +0100, Spencer Oliver wrote:
Modified:
trunk/configure.in
Log:
Make the parport-ppdev option enabled by default. This
may require
giving --disable-parport-ppdev to configure on some platform(s).
Any reason why as it breaks win32 build
Or do you mean to say that --disable-parport-ppdev does not work??
I had to specify --disable-parport-ppdev before my parport interface
would work under Ubuntu 9.04.
--
Øyvind Harboe
Embedded software and hardware consulting services
http://www.zylin.com
On Tue, 2009-07-14 at 10:24 +0100, Spencer Oliver wrote:
On Tue, 2009-07-14 at 10:11 +0100, Spencer Oliver wrote:
Modified:
trunk/configure.in
Log:
Make the parport-ppdev option enabled by default. This
may require
giving --disable-parport-ppdev to configure on some
In this respect, I think all of the drivers should be enabled
by default. Developers could disable them by choice, but
their underlying libraries are being detected such that we
can add new checks to disable the drivers when their
dependencies are missing.
The goal is to allow our
On Tue, Jul 14, 2009 at 11:46:59AM +0200, Øyvind Harboe wrote:
Or do you mean to say that --disable-parport-ppdev does not work??
I had to specify --disable-parport-ppdev before my parport interface
would work under Ubuntu 9.04.
Hm, that would be strange. Did you do 'modprobe ppdev'?
On Tue, 2009-07-14 at 12:21 +0100, Spencer Oliver wrote:
In this respect, I think all of the drivers should be enabled
by default. Developers could disable them by choice, but
their underlying libraries are being detected such that we
can add new checks to disable the drivers when
