Hi, Yes, I've seen your mail too late as I wasn't subscribed to the user mailing list (and to be honest a separate user list seems to be a bad idea in general).
Please see inline. On Sun, Mar 30, 2014 at 11:50:05AM +0200, Markus Mayer wrote: > I was recently doing some cleanup at the fedora openocd package and run > into some issues. Your feedback is much appreciated. > - the latest jimtcl (0.75) slightly changed its API. A patch to adapt > openocd to the new API is attached. Are you sure it's better in the long run to use a separately packaged jimtcl rather than the specific version from the openocd sources? I'm afraid I can see how it can cause issues, e.g. when OpenOCD might rely on some JimTcl fix that wouldn't be officially released yet. > - openocd ships with an udev file (contrib/openocd.udev), but its not > installed into the required udev directory. Is there any reason for this? It's now called 99-openocd.rules, and yes, it's installed to /usr/share/openocd/contrib by default. Do you know of a good way to make autotools copy udev rules files in a distro-specific way? > - openocd ships firmware for the ulink (OpenULINK/ulink_firmware.hex). > What's the license of the firmware? Where can the sources be gatherd > from? Should be in src/jtag/drivers/OpenULINK/src, and it's GPLv2+ > - ulink_firmware.hex is installed to /usr/lib/openocd. As this file is > not meant to be executed on the host system, /usr/share/openocd would be > a better place. Hm, strange, dist_ulink_DATA = $(ULINK_FIRMWARE)/ulink_firmware.hex should use an appropriate directory by default. Will take a look on it, thanks. -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:[email protected] ------------------------------------------------------------------------------ _______________________________________________ OpenOCD-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openocd-devel
