Hello Øyvind, >1. The directory structure decided by "make install" must be respected, >otherwise e.g. the target library is broken. In the moment I do not use the target library. The problem with the library is that a new user had no "fix" examples. The target library is a "floating feature" in the moment.
With the old way, I have an example for the beginners where all the information where stored in only one file. Here I can say please use this file for your interface/target and it will work. With the target library it can be a problem (not must be a problem). Even I do not use "make install" here if I create a windows installer. I think the primary use of OpenOCD is for debugging, and do we need the script language for debugging? I think for the beginners we need some more description and examples how to use OpenOCD with the target library. Therefore it would be nice to have some description into the openocd.pdf (texi). But here I think we need a pdf file too and not only the texi version. Perhaps Dominic can add one version of the openocd.pdf at a central place like here: http://openocd.berlios.de/web/ Best regards, Michael _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
