On Tuesday 12 January 2010, David Brownell wrote:
> On Tuesday 12 January 2010, Thomas Kindler wrote:
> > David Brownell wrote:
> > >
> > > Could you give the appended patch a try?
> >
> > I'd love to!
> >
> > But right now, I'm stuck with building libftdi under cygwin. In the
> > past, I only managed to built it myself using ftd2xx. But since I'm
> > using Freddie Chopin's libftdi based packages, I don't want to switch
> > the system drivers just for testing.
> >
> > I can't get libftdi (git version) to build under cygwin:
Just for the record, I had only one issue building:
- current OpenOCD git
- libftdi 0.17 (latest, tarball not GIT)
- current cygwin including its libusb-win32 and boost
to build under cygwin. That issue was needing to #include <limits.h>
in the main libftdi file, to get PATHLEN. It started up OK, but I
didn't try to use any USB devices there. It's MS-Windows, after all,
and requires crazy driver-related voodoo incantations to get that
stuff working. And not only do we not have a full moon here, I have
neither alligator teeth nor virgin's blood to use. Or brick dust. ;)
I don't know how close that really is to a *usable* build, but it
was at least a successful build.
- Dave
> >
> > $ cmake .
>
> Yeah, I saw they switched to cmake ... didn't seem to me like a
> net win, I figured there would be problems.
>
>
> > -- Build type: Debug
> > CMake Error at src/CMakeLists.txt:29 (install):
> > install Library TARGETS given no DESTINATION!
> >
> >
> > -- Boost not found, won't build libftdi++
> > -- SWIG was not found. Please specify Swig executable location
> > -- Doxygen found.
> > -- Configuring incomplete, errors occurred!
> >
> > best regards,
>
> Darn ...
>
> I'm feeling inclined to merge that patch anyway -- it made several
> things work a bunch better for me -- but I'll hold off for a while.
>
> If I do merge without test feedback from you, that'll bias me towards
> having an RC2 for this release ... Freddie's fairly on-top-of-things,
> maybe he'd create an RC2 build you can test. ;)
>
> - Dave
>
>
_______________________________________________
Openocd-development mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/openocd-development
