Congratulations with the release!
On Fri, Dec 11, 2020 at 05:49:22PM +0800, Xiaofan Chen wrote:
> * Windows: Drop support for Windows XP
I wonder if it's essential for the OpenOCD userbase, heh.
--
Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software!
mailto:fercer...@gmail.c
Hello Yegor,
On Wed, Apr 12, 2017 at 08:00:32AM +0200, Yegor Yefremov wrote:
> compiling libftdi with mingw toolchain produces following warnings:
>
> [ 29%] Building C object examples/CMakeFiles/stream_test.dir/stream_test.c.obj
> /home/user/Documents/versioned/libftdi/examples/stream_test.c: In
Hello,
On Mon, Jan 02, 2017 at 09:51:34AM +0800, Xiaofan Chen wrote:
> On Mon, Dec 14, 2015 at 10:09 PM, Xiaofan Chen wrote:
> > Today I tried to build libftdi git under MSYS2 and it seems to be
> > quite easy. Just need to install the necessary dependencies using
> > MSYS2 pacman.
>
> Today I t
On Fri, Mar 06, 2015 at 08:53:51PM -0500, Forest Crossman wrote:
> On Fri, Mar 6, 2015 at 4:01 PM, Paul Fertser wrote:
> > Just for the reference, OpenOCD already has an SVF player and can use
> > any common FTDI-based JTAG adapter for that. Many people are uploading
> > bi
Hi,
On Fri, Mar 06, 2015 at 03:51:32PM -0500, William Kolment wrote:
> I am a hardware test engineer (working for IntroSpect Technology) and we
> would like to make use of libftdi library to implement a svf player that
> would upload firmware onto a fpga product.
Just for the refere
Hi,
On Tue, Jan 27, 2015 at 11:21:17PM +0100, Robin Haberkorn wrote:
> btw.: Hosting a Github mirror of the libftdi repository could boost free
> software contributions to libftdi. With a Github repository, I could
> create a fork and maintain my "patches" on a public branch, while
> sending you p
On Wed, Jan 29, 2014 at 08:33:29PM +0800, Xiaofan Chen wrote:
> I hear that MinGW-w64 has better C99 compliance than MinGW.org.
MinGW doesn't aim at C99 compliance at all, it's in their official
FAQ, they just provide support for the official MS CRT, and MS is not
interested in C99. MinGW-w64 is a
This fixes /usr/include/libftdi1/ftdi.h:467:12: error: function declaration
isn't a prototype [-Werror=strict-prototypes]
Reported-by: Drasko DRASKOVIC
Signed-off-by: Paul Fertser
---
src/ftdi.h |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/ftdi.h b/src/f
Hi,
On Thu, Sep 12, 2013 at 10:24:20AM +0200, Johannes Hampel wrote:
> 1.Creation of symbolic links in /usr/local/lib was necessary (I
> installed the libraries explicitly into /usr/local):
>
> # ln -s libftdi1.so libftdi.so
>
> I don't know if this is an issue that LibFTDI must handle or
This should make them less hackish and the outlined way seems to be
what upstream is recommending.
Signed-off-by: Paul Fertser
---
v2: use $HOME, fix a typo
README.mingw | 55 ++-
1 files changed, 18 insertions(+), 37 deletions(-)
diff
This should make them less hackish and the outlined way seems to be
what upstream is recommending.
Signed-off-by: Paul Fertser
---
README.mingw | 55 ++-
1 files changed, 18 insertions(+), 37 deletions(-)
diff --git a/README.mingw b
to be explicitly set.
It still doesn't prevent pkg-config-less operation, i.e. the user can
specify something like
-DLIBUSB_INCLUDE_DIR=~/i686-w64-mingw32-root/usr/include/libusb-1.0
and the build will succeed even when no pkg-config executable is
present.
Signed-off-by: Paul Fertser
---
wed from libusb, fixes it.
Signed-off-by: Paul Fertser
---
src/ftdi.h | 12
1 files changed, 12 insertions(+), 0 deletions(-)
diff --git a/src/ftdi.h b/src/ftdi.h
index 15067c7..3d97dd9 100644
--- a/src/ftdi.h
+++ b/src/ftdi.h
@@ -20,6 +20,18 @@
#include
#include
+/* '
13 matches
Mail list logo
