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 platform(s). > > > > > > > > > > > > > > Any reason why as it breaks win32 build - why not leave as > > disabled by > > > default? > > > > My understanding is that both x86 Linux and Darwin require it enabled; > > moreover, it is forced enabled on all non-x86 platforms. Nico pointed > > out that the help text was wrong. > > > > Or do you mean to say that --disable-parport-ppdev does not work?? > > > > No --disable-parport-ppdev does work but my point is why does it need > enabling by default?
The configure script should provide "sensible" defaults for options. This option seems to either be required or forced for most platforms, so it seems "sensible" for this option to be enabled by default. 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 users to simply run './configure' without having to give any messy options. Everything should be detected automatically, picking "sane" default settings if possible. While that may not be 100% possible, we should be able to do _much_ better than the 0.2.0 configure script manages to accomplish. > Surely let the developer enable what he wants? The non-x86 developer does not have a choice; the configure script always forced it to be enabled. The developer still has the choice to disable it, so a choice is still there -- it's just backwards now. It's broken either way, really. Clearly, the configure script needs to be revisited during 0.3.0. We need to figure out when and where these options are required, and we can test in the script for those required conditions. These is are easy to script, once we know what they are. Cheers, Zach _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
