2014-10-04 14:01:08 by Makoto Fujiwara | Files touched by this commit (4) |
Log message:
New in 1.1 - 2014-02-05
-----------------------
* Fix FT232H eeprom suspend pulldown setting (Davide Michelizza)
* Fix FT232H eeprom user area size (Davide Michelizza)
* Improved mingw build (Paul Fertser and Michel Zou)
* C++ wrapper: Get/set functions for USB timeouts (Jochen Sprickerhof)
* Partial support for FT230X (Nathael Pajani)
* New API function: ftdi_eeprom_set_strings() (Nathael Pajani)
* Prevent possible segfault in ftdi_eeprom_decode() (Nathael Pajani)
* Save device release number in eeprom (Jarkko Sonninen)
* Fix "self powered" eeprom flag (Jarkko Sonninen)
* Improved python wrapper (Michel Zou)
* Many buildsystem improvements (Michel Zou and Mike Frysinger)
* See the git history for more changes and fixes
|
2014-08-13 12:57:38 by Adam Ciarcinski | Files touched by this commit (95) | |
Log message:
Revbump after boost-libs update
|
2014-06-04 08:09:44 by David Sainty | Files touched by this commit (1) |
Log message:
This package builds using cmake these days, so CONFIGURE_ARGS isn't useful.
Port the intended flags to cmake arguments.
Fixes the build in obscure circumstances where doxygen is installed, but
some documentation python build-time requirements happen to be missing.
|
2014-05-20 00:44:14 by David Sainty | Files touched by this commit (1) |
Log message:
The package uses the "python" executable for building the python bits. \
If it
isn't present in the package build sandpit it may reach out and use a possibly
unmanaged version of python. On Linux that might be some base system copy of
python, which would only be the same version by chance.
If it happens to be, say, python 2.6 - but Pkgsrc is defaulting to python 2.7,
then the installed files will have the wrong filenames, the PLIST won't match,
and the build will fail (not to mention that the built files may well be
incompatible with the intended python anyway).
Having the "python" tool in the sandpit solves this problem.
|
2014-05-09 09:37:28 by Thomas Klausner | Files touched by this commit (553) |
Log message:
Mark packages that are not ready for python-3.3 also not ready for 3.4,
until proven otherwise.
|
2014-01-25 11:30:32 by Thomas Klausner | Files touched by this commit (533) | |
Log message:
Mark packages as not ready for python-3.x where applicable;
either because they themselves are not ready or because a
dependency isn't. This is annotated by
PYTHON_VERSIONS_INCOMPATIBLE= 33 # not yet ported as of x.y.z
or
PYTHON_VERSIONS_INCOMPATIBLE= 33 # py-foo, py-bar
respectively, please use the same style for other packages,
and check during updates.
Use versioned_dependencies.mk where applicable.
Use REPLACE_PYTHON instead of handcoded alternatives, where applicable.
Reorder Makefile sections into standard order, where applicable.
Remove PYTHON_VERSIONS_INCLUDE_3X lines since that will be default
with the next commit.
Whitespace cleanups and other nits corrected, where necessary.
|
2013-12-03 02:40:14 by Makoto Fujiwara | Files touched by this commit (6) |
Log message:
Import libftdi1-1.0 as devel/libftdi1.
libftdi version 1.0
A library (using libusb) to talk to FTDI's UART/FIFO chips
including the popular bitbang mode.
The following chips are supported:
- FT4232H / FT2232H
- FT232R / FT245R
- FT2232L / FT2232D / FT2232C
- FT232BM / FT245BM (and the BL/BQ variants)
- FT8U232AM / FT8U245AM
libftdi requires libusb 1.x.
|