Dear Devepment and support people,

On "sparkfun"  I am following "mifi's" instrutions to a tee.
http://forum.sparkfun.com/viewtopic.php?t=11221
never the less:

I took another shot at attempting to compile my own version
of openOCD with ftd2xx.  Both attemps on my work laptop (Vista)
and my home PC (XP) resulted in identical failure.

>>> This is important and relates,
to a bunch of people who would like to be able to succesfully use
openOCD with ftd2xx, right now <<<<:

http://forum.sparkfun.com/viewtopic.php?t=16172

Fact of the matter is we can not get the compile to work and get stuck
trying to use the unix like commands "./bootstrap" and "./configure"
One nice and impressive thing is that subversion was able to
properly download all the source files for openOCD via cygwin,
as advertised, so we are almost there.

This is a plea for help.

Here is an excerpt from openOCDs own website, that indicates
they may admit that using cygwin is not easy. It would sure help
if someone would come to our rescue and prove to us that it can
be done.

Building OpenOCD from a repository requires a recent version of the GNU
autotools (autoconf >= 2.59 and automake >= 1.9).  For building on
Windows, you have to use Cygwin. Make sure that your @env{PATH}
environment variable contains no other locations with Unix utils (like
UnxUtils) - these can't handle the Cygwin paths, resulting in obscure
dependency errors.  This was an observation gathered from the logs of
one user; please correct us if this is wrong.
Ref bottom of page here:
http://svn.berlios.de/svnroot/repos/openocd/trunk/README

It seem this statement is saying "We have not figured it out yet, either"
So the community is still looking for more guidance.
I think there is someone out there who is more unix savy than me
that can get us un-stuck. Cygwin is more like unix than windows.


"A penny will get you on the subway, but garlic will get you a seat"

Sincerely,
Joe
_______________________________________________
Openocd-development mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/openocd-development

Reply via email to