On Nov 22, 2008, at 3:54 AM, Spen wrote:
Hi, I think its about time openocd made a release 1.0.I propose we create a openocd_rel_1_0 branch that will be frozen (except formajor bugs) after a month we make a release. Any objections/comments? release will be for both x86 win32 (mingw) and linux suggested build options will be (win32): --enable-parport --enable-jlink --enable-ft2232_ftd2xx and linux --enable-parport --enable-parport_ppdev --enable-jlink --enable-ft2232_ftd2xx Cheers Spen _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
I agree. A release is definitely worthwhile. It will certainly allow new users to find the source more easily. By enabling ftd2xx support, will openocd run even if the user doesn't have ftd2xx installed? Can we also enable libftdi support since a number of linux users will not wish to install close sourced libraries?
-- Rick Altherr [EMAIL PROTECTED]"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