>> If so, please don't start yet another AVRDUDE command-line wrapper. Obviously that's the easiest way to go. It would be nice to reuse the some of the file parsers included in avrdude anyway.
>> library<->CLI split I wasn't aware of this split, but I don't have the code on me. Unless the split is "main.c" (the CLI) vs all other files (the libraries)? >> I'm aware there are too many potential calls to exit() in the library ... Additionally, all status messages are through fprintf(stderr,...), which I assume should be changed. Also, '-x' parameters are decoded in the 'library' part of the code. Is the configuration file to be converted to XML at some stage? And can we turf out the lexer/parser?!?! :) On 11 May 2010 19:11, Joerg Wunsch <[email protected]> wrote: > As Doug Brown wrote: > > > Ok, thanks. I guess it could be a little project for me to teach me > > how to use wxWidgets when I get some time then. > > If so, please don't start yet another AVRDUDE command-line wrapper. > Instead, try setting up a GUI based on the (internal) AVRDUDE library. > If anything is still missing in the library<->CLI split, tell us here. > (I'm aware there are too many potential calls to exit() in the library > code, patches welcome.) > > -- > cheers, J"org .-.-. --... ...-- -.. . DL8DTL > > http://www.sax.de/~joerg/ NIC: JW11-RIPE > Never trust an operating system you don't have sources for. ;-) > _______________________________________________ avrdude-dev mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/avrdude-dev
