> I agree that scripting does add functionality, but what i also like > about openocd is that it can be standalone.
Please define standalone. OpenOCD needs the executable + some other files it ships with, but it does not depend on any other modules to be installed. Is that standalone? > commands.tcl embedded into openocd binary - i like that idea. > > How about using a similar concept to gcc's specs file, if commands.tcl is > found in the tcl dir it is used otherwise the internal one is used? This sounds like work for no benefit if we have to cross the bridge that OpenOCD needs the executable + some other files to work correctly. > I know a lot of people who use openocd with a single script and the binary > for > production programming, reproducing the dir structure does not suit > everybody. What's the downside to duplicating the entire directory structure? > embedding commands.tcl would suit everybody would it not? I believe that we'll have to cross the bridge that OpenOCD requires the executable + other files it ships with, sooner rather than later anyway. I'd especially like all OpenOCD distributions out there to ship with the target library to help get the target library known and get target config files contributed back. If someone must(why?) minimize the # of files OpenOCD ships with, they still can. They can even embed commands.tcl into the single config file, though this doesn't really strike me as a killer feature. -- Øyvind Harboe http://www.zylin.com/zy1000.html ARM7 ARM9 XScale Cortex JTAG debugger and flash programmer _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
