On Mon, Apr 12, 2010 at 8:31 AM, Joerg Wunsch <[email protected]> wrote: >> Probably a better approach would be to provide a >> configure option or something to enable/disable this programmer if >> needed. > > That's fine with me. There are already some examples for --enable/ > --disable switches in the existing configure.ac file.
OK, I looked at how the parport enable/disable is done in configure.ac. Just one question - only the body of par.c is inside #if HAVE_PARPORT macros. The parts about the config file parsing, extern function declaration in par.h and other are always included, even if HAVE_PARPORT is not defined.. Is this the correct way, or should I put everything inside #if HAVE_GPIO macros? _______________________________________________ avrdude-dev mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/avrdude-dev
