> -----Original Message----- > From: > [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] > rg] On Behalf Of Joerg Wunsch > Sent: Friday, March 14, 2008 2:07 PM > To: [email protected] > Subject: [avrdude-dev] Initial STK600 support committed to CVS > > > Last time we've been discussing it, the only/main concern with > per-device configuration files was that scattering several dozens of > files on the target system contributes to wasted disk space due to > file system fragmentation.
This has got to be a complete non-issue. What with hard disk sizes per cost these days, it shouldn't matter if there is some wasted space due to fragmentation. I would much rather have a file organization that makes sense. > If that's the only point, I'd propose a > scheme where there are separate XML files (one per device, one per > programmer) within the development tree, but they will then be > combined into a single avrdude-conf.xml during the build, so the > target system will still have just one configuration file. This just adds another unnecessary step to the build process. Please don't. > > Are there any preferences for an XML parser library to use? Something that will work cross-platform. Last I saw, libxml is used in the xmlstar project (sourceforge) successfully on multiple platforms. > > Any other things to consider? I definitely lean towards one xml file per device or per programmer. It makes it simpler to add support (just add a new file). These files should probably be kept in a standardized named subdirectory tree, relative to where the avrdude executable is located. Thanks for doing all the great work for supporting the STK600! :-) Eric Weddington _______________________________________________ avrdude-dev mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/avrdude-dev
