libftdi - A library (using libusb) to talk to FTDI's FT2232C,
FT232BM and FT245BM type chips including the popular bitbang mode.
Note: When you get a -5 error "can't claim usb device" during
ftdi_usb_open(), make sure the kernel ftdi_sio driver is unloaded.
===> The following configuration options are available for libftdi-0.20_24:
BOOST=on: C++ bindings (requires Boost)
PYTHON=on: Python bindings
===> Use 'make config' to modify these settings
devel/libftdi: resurrect and fix broken tree
There are several ports still depend on this one.
Fixes: b1f10ca6b2ffbdad2ba2bd309584941063fcb7b3
Reported by: many
Remove WWW entries moved into port Makefiles
Commit b7f05445c00f has added WWW entries to port Makefiles based on
WWW: lines in pkg-descr files.
This commit removes the WWW: lines of moved-over URLs from these
pkg-descr files.
Approved by: portmgr (tcberner)
Add WWW entries to port Makefiles
It has been common practice to have one or more URLs at the end of the
ports' pkg-descr files, one per line and prefixed with "WWW:". These
URLs should point at a project website or other relevant resources.
Access to these URLs required processing of the pkg-descr files, and
they have often become stale over time. If more than one such URL was
present in a pkg-descr file, only the first one was tarnsfered into
the port INDEX, but for many ports only the last line did contain the
port specific URL to further information.
There have been several proposals to make a project URL available as
a macro in the ports' Makefiles, over time.
(Only the first 15 lines of the commit message are shown above )
devel/libftdi: Fix build without PYTHON after r451798
BINARY_ALIAS is set unconditionally but swig3.0 is only available with
PYTHON=on and create-binary-alias will fail when it is missing.
PR: 225524
Reported by: johan@stromnet.se
Convert Python ports to FLAVORS.
Ports using USE_PYTHON=distutils are now flavored. They will
automatically get flavors (py27, py34, py35, py36) depending on what
versions they support.
There is also a USE_PYTHON=flavors for ports that do not use distutils
but need FLAVORS to be set. A USE_PYTHON=noflavors can be set if
using distutils but flavors are not wanted.
A new USE_PYTHON=optsuffix that will add PYTHON_PKGNAMESUFFIX has been
added to cope with Python ports that did not have the Python
PKGNAMEPREFIX but are flavored.
USES=python now also exports a PY_FLAVOR variable that contains the
(Only the first 15 lines of the commit message are shown above )
Convert a couple ports that use both _CMAKE_ON and _CMAKE_OFF to _CMAKE_BOOL.
Use options helpers all the way in math/carve, because I couldn't help myself.
- Don't build example programs that aren't installed
(examples/CMakeLists.txt also contains an error (include should be
include_directories on line 5) [1])
- Remove DOCS option
- Fix PYTHON option when it is disabled
Reported by: Mike Harding <mvharding@gmail.com> [1]
Remove indefinite articles and trailing periods from COMMENT, plus
minor COMMENT typos and surrounding whitespace fixes. Categories D-F.
CR: D196
Approved by: portmgr (bapt)
In preparation of removing devel/libusb (expires 2013-04-30), remove it
from these ports.
Other changes:
- convert Makefile header
- convert to optionsNG
- remove indefinite article from comment
- drop support for FreeBSD < 8.0
- pet portlint (leave library ABI versions in LIB_DEPENDS)
- net-mgmt/spectools: change option name from GTK to GTK2 to use default
description from bsd.options.desc.mk
Approved by: portmgr (bapt)
Fix build problems with new automake.
PR: ports/170241 (partial - upgrade to new version not done)
Submitted by: Craig Leres
Approved by: maintainer timeout
- Add LDFLAGS to CONFIGURE_ENV and MAKE_ENV (as it was done with LDFLAGS)
- Fix all ports that add {CPP,LD}FLAGS to *_ENV to modify flags instead
PR: 157936
Submitted by: myself
Exp-runs by: pav
Approved by: pav
-Repocopy devel/libtool15 -> libtool22 and libltdl15 -> libltdl22.
-Update libtool and libltdl to 2.2.6a.
-Remove devel/libtool15 and devel/libltdl15.
-Fix ports build with libtool22/libltdl22.
-Bump ports that depend on libltdl22 due to shared library version change.
-Explain what to do update in the UPDATING.
It has been tested with GNOME2, XFCE4, KDE3, KDE4 and other many wm/desktop
and applications in the runtime.
With help: marcus and kwm
Pointyhat-exp: a few times by pav
Tested by: pgollucci, "Romain Tartière" <romain@blogreen.org>, and
a few MarcusCom CVS users. Also, I might have missed a few.
Repocopy by: marcus
Approved by: portmgr
- Fix libftdi on HEAD by including stdlib.h in ftdi.c. Since HEAD's
version on usb.h doesn't include stdlib.h like libusb does, it fails
to find prototypes for realloc function which leads to incorrect
storage types used and memory corruption as a consequence.
- Chase libusb20 rename in r189585.
- Mark sane-backends broken on current due to changes
in USB stack.
Reviewed by: thompsa (old version), miwi
Tested by: miwi
Update CONFIGURE_ARGS for how we pass CONFIGURE_TARGET to configure script.
Specifically, newer autoconf (> 2.13) has different semantic of the
configure target. In short, one should use --build=CONFIGURE_TARGET
instead of CONFIGURE_TARGET directly. Otherwise, you will get a warning
and the old semantic may be removed in later autoconf releases.
To workaround this issue, many ports hack the CONFIGURE_TARGET variable
so that it contains the ``--build='' prefix.
To solve this issue, under the fact that some ports still have
configure script generated by the old autoconf, we use runtime detection
in the do-configure target so that the proper argument can be used.
Changes to Mk/*:
- Add runtime detection magic in bsd.port.mk
(Only the first 15 lines of the commit message are shown above )
libftdi - A library (using libusb) to talk to FTDI's FT2232C,
FT232BM and FT245BM type chips including the popular bitbang mode.
Note: When you get a -5 error "can't claim usb device" during
ftdi_usb_open(), make sure the kernel ftdi_sio driver is unloaded.
WWW: http://www.intra2net.com/de/produkte/opensource/ftdi/
PR: ports/100982
Submitted by: Olexandr Davydenko <o.davydenko at gmail.com>