On Jan 22, 2009, at 7:57 AM, Freddie Chopin wrote:
Rick Altherr pisze:Package maintainers: If you wish to have a set of binaries placed on theproject site, please build the package and send it to me.i don't mean to get in anyone's way (I'm new here, don't know whether there are any designated people to do that), but as there are nomovements in this field, I can provide the 'package' for windows, whichI compiled yesterday for starters, the compilation options were: --enable-parport --enable-parport_giveio --enable-ft2232_ftd2xx --enable-ep93xx --enable-at91rm9200 --enable-usbprog --enable-presto_ftd2xx --enable-jlink --enable-vsllink --enable-rlink --enable-dummy -enable-gw16012 --enable-amtjtagaccel --with-ftd2xx-win32-zipdir=[path to ftd2xx] if noone is willing to do that, I can, but I'd like to know what a 'package' exactly is? is it just the executable, or maybe I shouldattach the target, interface, board cfg files? how about documentation? drivers (rlink special driver, turtelizer driver)? source code? maybe acomplete installer like the one on yagarto.de website? 4\/3!! _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Since we've never done a release before, you won't be getting in anyone's way. I'm not sure what the best package format for Window would be. Probably the most familiar to end users would be an MSI installer. You should include the openocd.exe, the config files, and the documentation at a minimum. As for where to install them to, I have no idea.
-- Rick Altherr kc8...@kc8apf.net"He said he hadn't had a byte in three days. I had a short, so I split it with him."
-- Unsigned
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development