From: "Åke Rehnman" <ake.rehnman@gmail.com>
To: cygwin-apps@cygwin.com
Subject: [ITP] libftdi1 & libconfuse
Date: Tue, 18 Apr 2017 18:50:00 -0000 [thread overview]
Message-ID: <afa43f96-dcb6-4372-6b9f-70ca1400f7b3@gmail.com> (raw)
In-Reply-To: <f4a188ae-6d07-b816-9bfa-897a88afcbbf@gmail.com>
Hello all,
One more effort to try getting some attention towards libftdi and
libconfuse packages...
Both libftdi and libconfuse are available in ubuntu and debian + others.
Libftdi is used with openocd among others. Libconfuse is used by eeprom
programmer for libftdi.
libftdi1 is released under LGPL 2.1 and eeprom programmer under GPL 2.
See https://www.intra2net.com/en/developer/libftdi/index.php
libconfuse is released under ISC License. See
https://github.com/martinh/libconfuse/blob/master/LICENSE
Regards
/Ake
Libftdi1:
category: Libs
requires: bash cygwin libconfuse1 libgcc1 libstdc++6 libusb1.0 libconfuse1
sdesc: "Library to control and program the FTDI USB controller"
ldesc: "libFTDI is an open source library to talk to FTDI chips: FT232BM, FT245BM, FT2232C, FT2232D, FT245R, FT232H and FT230X including the popular bitbang mode. The library is linked with your program in userspace, no kernel driver required. libFTDI works perfectly with Linux, Windows, MacOS X and BSD variants thanks to libusb."
Libconfuse:
category: Libs
requires: cygwin libintl8
sdesc: "Library for parsing configuration files"
ldesc: "libConfuse is a configuration file parser library, licensed under the terms of the ISC license, and written in C."
Files available here: https://stm8-binutils-gdb.sourceforge.io/cygwin/
next prev parent reply other threads:[~2017-04-18 18:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-18 12:33 [ITP] libftdi1 Åke Rehnman
2017-04-18 18:50 ` Åke Rehnman [this message]
2017-04-19 15:52 ` [ITP] libftdi1 & libconfuse Jon Turney
2017-04-19 22:03 ` Åke Rehnman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=afa43f96-dcb6-4372-6b9f-70ca1400f7b3@gmail.com \
--to=ake.rehnman@gmail.com \
--cc=cygwin-apps@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).