On Wed, 2009-07-01 at 07:45 -0700, Joseph Kuss wrote:
[snip]
> 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 copied and rephrased that statement from the User's Guide, but I did
not originate it or try to confirm it. The in-tree documentation
remains woefully incomplete when it comes to Win32 build support.
While we have multiple indications that the SparkFun instructions can be
made to work, I have seen repeated indications that they also fail to
cover some of the extenuating circumstances that are encountered in the
real world. It seems that some details are missing, or you would be
able to find and resolve your problems by using those instructions.
That said, the SparkFun forum is NOT an acceptable place to distribute
build instructions for OpenOCD. In-tree documentation should be
produced and included for users, as this will eliminate the requirement
for these users to visit the internet in order to build this project.
I have grown baffled that this has not been remedied before now, since I
made an explicit request to this effect on the list recently.
As you mentioned, the SparkFun instructions were written by "mifi"; that
user, Michael Fischer, is also subscribed here, and he should have the
copyright for the forum-based instructions. It should be easy enough
for him to add those instructions to the repository, so others can then
provide patches to clarify and improve them. I have added him to the CC
line for this message to ensure he is aware of this request.
Myself, I want README.CygWin for this purpose, but I would like us to
develop instructions to put into README.MinGW32 as well. These days, a
solution that avoids CygWin entirely would be to run a VM on Windows
with a Linux image that builds the mingw32 cross-compiler and compiles
suitable Windows binaries of the required packages. I have worked on
projects that provided an in-tree MinGW32 build script that produced
tools and all dependencies from source. Such a script can even produce
a standard installer (using Nullsoft's tools), from what I remember.
Cheers,
Zach
_______________________________________________
Openocd-development mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/openocd-development
