> > Ø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. 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? 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. embedding commands.tcl would suit everybody would it not? Cheers Spen _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
