On Thu, Jul 10, 2008 at 10:06:06PM +0100, Spen wrote: > > Øyvind Harboe wrote: > > > 2. commands.tcl requires (1), but we *could* embed it into the > > > executable instead but that addresses the symptom and not > > the disease, > > > it will only help us short-term. > > > > I consider this a goo idea if OOCD functions are changed to > > be scripting friendly with a TCL frontend like in flash banks > > example, so that basic commands are kept completely inside > > OOCD to reduce hassle for end users, especially those not > > much familiar with OOCD yet. > > I agree that scripting does add functionality, but what i also like > about openocd is that it can be standalone.
Full Ack. Please make sure that the tcl stuff remains completely optional/standalone, which is desirable for various reasons IMO. One nice thing about openocd is that it has almost no requirements and can thus work on very small, stripped-down systems. > embedding commands.tcl would suit everybody would it not? How would that work and would it still require users to install tcl? Uwe. -- http://www.hermann-uwe.de | http://www.holsham-traders.de http://www.crazy-hacks.org | http://www.unmaintained-free-software.org _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
