head 1.58; access; symbols pkgsrc-2026Q1:1.57.0.4 pkgsrc-2026Q1-base:1.57 pkgsrc-2025Q4:1.57.0.2 pkgsrc-2025Q4-base:1.57 pkgsrc-2025Q3:1.56.0.2 pkgsrc-2025Q3-base:1.56 pkgsrc-2025Q2:1.54.0.2 pkgsrc-2025Q2-base:1.54 pkgsrc-2025Q1:1.53.0.2 pkgsrc-2025Q1-base:1.53 pkgsrc-2024Q4:1.52.0.2 pkgsrc-2024Q4-base:1.52 pkgsrc-2024Q3:1.51.0.2 pkgsrc-2024Q3-base:1.51 pkgsrc-2024Q2:1.49.0.4 pkgsrc-2024Q2-base:1.49 pkgsrc-2024Q1:1.49.0.2 pkgsrc-2024Q1-base:1.49 pkgsrc-2023Q4:1.48.0.4 pkgsrc-2023Q4-base:1.48 pkgsrc-2023Q3:1.48.0.2 pkgsrc-2023Q3-base:1.48 pkgsrc-2023Q2:1.47.0.2 pkgsrc-2023Q2-base:1.47 pkgsrc-2023Q1:1.45.0.2 pkgsrc-2023Q1-base:1.45 pkgsrc-2022Q4:1.44.0.4 pkgsrc-2022Q4-base:1.44 pkgsrc-2022Q3:1.44.0.2 pkgsrc-2022Q3-base:1.44 pkgsrc-2022Q2:1.43.0.4 pkgsrc-2022Q2-base:1.43 pkgsrc-2022Q1:1.43.0.2 pkgsrc-2022Q1-base:1.43 pkgsrc-2021Q4:1.42.0.2 pkgsrc-2021Q4-base:1.42 pkgsrc-2021Q3:1.41.0.4 pkgsrc-2021Q3-base:1.41 pkgsrc-2021Q2:1.41.0.2 pkgsrc-2021Q2-base:1.41 pkgsrc-2021Q1:1.40.0.2 pkgsrc-2021Q1-base:1.40 pkgsrc-2020Q4:1.38.0.6 pkgsrc-2020Q4-base:1.38 pkgsrc-2020Q3:1.38.0.4 pkgsrc-2020Q3-base:1.38 pkgsrc-2020Q2:1.38.0.2 pkgsrc-2020Q2-base:1.38 pkgsrc-2020Q1:1.37.0.2 pkgsrc-2020Q1-base:1.37 pkgsrc-2019Q4:1.34.0.4 pkgsrc-2019Q4-base:1.34 pkgsrc-2019Q3:1.33.0.2 pkgsrc-2019Q3-base:1.33 pkgsrc-2019Q2:1.30.0.2 pkgsrc-2019Q2-base:1.30 pkgsrc-2019Q1:1.27.0.4 pkgsrc-2019Q1-base:1.27 pkgsrc-2018Q4:1.27.0.2 pkgsrc-2018Q4-base:1.27 pkgsrc-2018Q3:1.26.0.2 pkgsrc-2018Q3-base:1.26 pkgsrc-2018Q2:1.24.0.2 pkgsrc-2018Q2-base:1.24 pkgsrc-2018Q1:1.23.0.2 pkgsrc-2018Q1-base:1.23 pkgsrc-2017Q4:1.19.0.6 pkgsrc-2017Q4-base:1.19 pkgsrc-2017Q3:1.19.0.4 pkgsrc-2017Q3-base:1.19 pkgsrc-2017Q2:1.17.0.2 pkgsrc-2017Q2-base:1.17 pkgsrc-2017Q1:1.16.0.2 pkgsrc-2017Q1-base:1.16 pkgsrc-2016Q4:1.14.0.2 pkgsrc-2016Q4-base:1.14 pkgsrc-2016Q3:1.13.0.2 pkgsrc-2016Q3-base:1.13 pkgsrc-2016Q2:1.12.0.6 pkgsrc-2016Q2-base:1.12 pkgsrc-2016Q1:1.12.0.4 pkgsrc-2016Q1-base:1.12 pkgsrc-2015Q4:1.12.0.2 pkgsrc-2015Q4-base:1.12 pkgsrc-2015Q3:1.11.0.4 pkgsrc-2015Q3-base:1.11 pkgsrc-2015Q2:1.11.0.2 pkgsrc-2015Q2-base:1.11 pkgsrc-2015Q1:1.10.0.2 pkgsrc-2015Q1-base:1.10 pkgsrc-2014Q4:1.8.0.2 pkgsrc-2014Q4-base:1.8 pkgsrc-2014Q3:1.6.0.2 pkgsrc-2014Q3-base:1.6 pkgsrc-2014Q2:1.5.0.2 pkgsrc-2014Q2-base:1.5 pkgsrc-2014Q1:1.2.0.2 pkgsrc-2014Q1-base:1.2 pkgsrc-2013Q4:1.1.0.2 pkgsrc-2013Q4-base:1.1; locks; strict; comment @# @; 1.58 date 2026.05.15.09.58.46; author adam; state Exp; branches; next 1.57; commitid AbaMQjZsFUtxxTFG; 1.57 date 2025.09.27.09.57.13; author wiz; state Exp; branches; next 1.56; commitid GSXfRJoW2938VkcG; 1.56 date 2025.08.20.11.34.51; author wiz; state Exp; branches; next 1.55; commitid lgT5N7I1hRAxGs7G; 1.55 date 2025.07.05.10.23.35; author gdt; state Exp; branches; next 1.54; commitid PcbohlVuvesSLx1G; 1.54 date 2025.05.05.22.14.13; author gdt; state Exp; branches; next 1.53; commitid IHRMNwfc3WPeFLTF; 1.53 date 2024.12.29.15.09.44; author adam; state Exp; branches; next 1.52; commitid oeKjyQMgtu2FopDF; 1.52 date 2024.10.04.03.49.20; author ryoon; state Exp; branches; next 1.51; commitid W6qyL3zvAllroisF; 1.51 date 2024.08.25.06.18.35; author wiz; state Exp; branches; next 1.50; commitid BcrSL94SO85mvanF; 1.50 date 2024.08.17.09.18.41; author wiz; state Exp; branches; next 1.49; commitid aUd0JAz4c0ygL9mF; 1.49 date 2023.12.29.18.24.41; author adam; state Exp; branches; next 1.48; commitid CbzM4kTH4d8WeoSE; 1.48 date 2023.08.14.05.24.11; author wiz; state Exp; branches; next 1.47; commitid LOSB79OLVxvXjIAE; 1.47 date 2023.06.06.12.40.39; author riastradh; state Exp; branches; next 1.46; commitid xhspr6Z8JLQOWSrE; 1.46 date 2023.04.23.14.26.16; author adam; state Exp; branches; next 1.45; commitid Laj8GRA8jxylXemE; 1.45 date 2023.01.22.16.28.23; author ryoon; state Exp; branches; next 1.44; commitid aiP40A5zgFwvyyaE; 1.44 date 2022.06.30.11.18.15; author nia; state Exp; branches; next 1.43; commitid AhctUV91Vubws3KD; 1.43 date 2022.01.10.01.46.29; author ryoon; state Exp; branches; next 1.42; commitid Cj0KeHK24VPiN1oD; 1.42 date 2021.09.29.19.00.32; author adam; state Exp; branches; next 1.41; commitid WsBUbBM52TSePSaD; 1.41 date 2021.04.21.13.24.34; author adam; state Exp; branches; next 1.40; commitid RAyVO2K5RkoQ8aQC; 1.40 date 2021.03.07.10.51.06; author kleink; state Exp; branches; next 1.39; commitid nm9i1t4FC5sLJmKC; 1.39 date 2021.01.01.08.24.40; author ryoon; state Exp; branches; next 1.38; commitid slfyvXkOfADi10CC; 1.38 date 2020.05.06.14.04.27; author adam; state Exp; branches; next 1.37; commitid dLR3o37Fk2B5Cb7C; 1.37 date 2020.03.26.12.14.12; author nia; state Exp; branches; next 1.36; commitid IGyCZMkSs1l6kU1C; 1.36 date 2020.03.24.16.21.12; author nia; state Exp; branches; next 1.35; commitid cXdIBwufqRUNKF1C; 1.35 date 2020.01.12.20.20.11; author ryoon; state Exp; branches; next 1.34; commitid 5tyaDUwPevcZnrSB; 1.34 date 2019.11.03.10.39.16; author rillig; state Exp; branches; next 1.33; commitid REW2CfrA7HdqqoJB; 1.33 date 2019.09.02.13.19.40; author adam; state Exp; branches; next 1.32; commitid JNtg51I3DnX4jrBB; 1.32 date 2019.08.22.12.23.02; author ryoon; state Exp; branches; next 1.31; commitid UuiyQ10Dn9Rtl1AB; 1.31 date 2019.07.01.04.08.05; author ryoon; state Exp; branches; next 1.30; commitid qsMjwmrvOSh6hitB; 1.30 date 2019.04.26.14.12.35; author maya; state Exp; branches; next 1.29; commitid Y6vMANX4s26gKRkB; 1.29 date 2019.04.26.13.13.50; author maya; state Exp; branches; next 1.28; commitid U4pISddzN4WXpRkB; 1.28 date 2019.04.25.07.32.47; author maya; state Exp; branches; next 1.27; commitid 1FEMQBEPb9uTxHkB; 1.27 date 2018.12.13.19.51.48; author adam; state Exp; branches; next 1.26; commitid XjJhLcEnCzYFVF3B; 1.26 date 2018.08.16.18.54.41; author adam; state Exp; branches; next 1.25; commitid myXuojHMA7ifrnOA; 1.25 date 2018.07.03.05.03.10; author adam; state Exp; branches; next 1.24; commitid bH4MNADzVzoIfEIA; 1.24 date 2018.04.29.21.31.33; author adam; state Exp; branches; next 1.23; commitid QKwzJtFzAE0cOnAA; 1.23 date 2018.02.27.23.56.08; author khorben; state Exp; branches; next 1.22; commitid T6ZBmWV102XszysA; 1.22 date 2018.02.10.13.53.47; author khorben; state Exp; branches; next 1.21; commitid tTg638ybvKPFLjqA; 1.21 date 2018.01.01.21.18.21; author adam; state Exp; branches; next 1.20; commitid VDVceOVT4khVwdlA; 1.20 date 2018.01.01.18.16.36; author rillig; state Exp; branches; next 1.19; commitid L9I6buPNATMZvclA; 1.19 date 2017.08.24.20.03.11; author adam; state Exp; branches; next 1.18; commitid SAladHuASDqXhv4A; 1.18 date 2017.08.16.20.21.07; author wiz; state Exp; branches; next 1.17; commitid rqudPoPPU2GmEt3A; 1.17 date 2017.04.30.01.21.33; author ryoon; state Exp; branches; next 1.16; commitid 1A40BlmMDYkiOuPz; 1.16 date 2017.01.01.16.06.09; author adam; state Exp; branches; next 1.15; commitid jkBZ9Kd0NEyexhAz; 1.15 date 2017.01.01.14.43.31; author wiz; state Exp; branches; next 1.14; commitid TmfhF2MIYbgU4hAz; 1.14 date 2016.10.07.18.25.43; author adam; state Exp; branches; next 1.13; commitid WWBLkSP9Isuv4fpz; 1.13 date 2016.07.09.13.03.39; author wiz; state Exp; branches; next 1.12; commitid k9A2yv7vTRunbEdz; 1.12 date 2015.12.05.21.25.35; author adam; state Exp; branches; next 1.11; commitid bgA0CynThkP3WNLy; 1.11 date 2015.04.17.15.53.01; author adam; state Exp; branches; next 1.10; commitid kz5n0nxJowLkyXhy; 1.10 date 2015.01.18.06.18.58; author mef; state Exp; branches; next 1.9; commitid A1fO7LnmgqpPet6y; 1.9 date 2015.01.17.02.42.46; author mef; state Exp; branches; next 1.8; commitid iGlurGbLGRLE4k6y; 1.8 date 2014.11.07.19.39.29; author adam; state Exp; branches; next 1.7; commitid pQm2t4q4dGiUYhXx; 1.7 date 2014.10.04.12.01.08; author mef; state Exp; branches; next 1.6; commitid 1WOZHFLsfONPwSSx; 1.6 date 2014.08.13.10.57.34; author adam; state Exp; branches; next 1.5; commitid gRbzkcFp9YSgRbMx; 1.5 date 2014.06.04.06.09.44; author dsainty; state Exp; branches; next 1.4; commitid 2083ArZjC5GRvaDx; 1.4 date 2014.05.19.22.44.14; author dsainty; state Exp; branches; next 1.3; commitid ogeMXtkDNcWPwcBx; 1.3 date 2014.05.09.07.37.00; author wiz; state Exp; branches; next 1.2; commitid wfzXpL2biguCPPzx; 1.2 date 2014.01.25.10.30.01; author wiz; state Exp; branches; next 1.1; commitid VOWgk3vYhVXj8umx; 1.1 date 2013.12.03.01.40.14; author mef; state Exp; branches; next ; commitid dpYMIHS3xUAhUCfx; desc @@ 1.58 log @revbump for boost-libs @ text @# $NetBSD: Makefile,v 1.57 2025/09/27 09:57:13 wiz Exp $ DISTNAME= libftdi1-1.5 PKGREVISION= 12 CATEGORIES= devel MASTER_SITES= https://www.intra2net.com/en/developer/libftdi/download/ EXTRACT_SUFX= .tar.bz2 MAINTAINER= pkgsrc-users@@NetBSD.org HOMEPAGE= https://www.intra2net.com/en/developer/libftdi/ COMMENT= Userland driver library for FTDI USB chips LICENSE= gnu-lgpl-v2.1 # \todo Build fails if swig4 is installed. Apparently swig4 is # (incorrectly) used and the signature of SWIG_Python_AppendOutput has # changed. TOOL_DEPENDS+= swig3-[0-9]*:../../devel/swig3 USE_TOOLS+= pkg-config USE_LANGUAGES= c c++ .include "../../devel/cmake/build.mk" CMAKE_CONFIGURE_ARGS+= -Wno-dev CMAKE_CONFIGURE_ARGS+= -DEXAMPLES=off CMAKE_CONFIGURE_ARGS+= -DDOCUMENTATION=off CMAKE_CONFIGURE_ARGS+= -DLIB_SUFFIX="" CMAKE_CONFIGURE_ARGS+= -DFTDIPP=on CMAKE_CONFIGURE_ARGS+= -DPYTHON_BINDINGS=on CMAKE_CONFIGURE_ARGS+= -DCMAKE_POLICY_VERSION_MINIMUM=3.5 PKGCONFIG_OVERRIDE+= libftdi1.pc.in PKGCONFIG_OVERRIDE+= libftdipp1.pc.in PLIST_SUBST+= PYSITELIB=${PYSITELIB} .include "../../lang/python/pyversion.mk" .if ${PYTHON_VERSION} > 311 TOOL_DEPENDS+= ${PYPKGPREFIX}-setuptools-[0-9]*:../../devel/py-setuptools .endif .include "../../devel/boost-headers/buildlink3.mk" .include "../../devel/boost-libs/buildlink3.mk" .include "../../devel/confuse/buildlink3.mk" .include "../../devel/gettext-lib/buildlink3.mk" .include "../../devel/libusb1/buildlink3.mk" .include "../../lang/${PYPACKAGE}/buildlink3.mk" .include "../../lang/python/tool.mk" .include "../../mk/bsd.pkg.mk" @ 1.57 log @*: recursive bump for boost 1.89 @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.56 2025/08/20 11:34:51 wiz Exp $ d4 1 a4 1 PKGREVISION= 11 @ 1.56 log @*: fix build with cmake 4 @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.55 2025/07/05 10:23:35 gdt Exp $ d4 1 a4 1 PKGREVISION= 10 @ 1.55 log @libftdi1: Convert to cmake/build.mk (No apparent change in output.) @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.54 2025/05/05 22:14:13 gdt Exp $ d30 1 @ 1.54 log @devel/libftdii: Add caution/todo about swig4 @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.53 2024/12/29 15:09:44 adam Exp $ a18 1 USE_CMAKE= yes d22 2 @ 1.53 log @revbump after updating boost @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.52 2024/10/04 03:49:20 ryoon Exp $ d14 3 @ 1.52 log @*: Recursive revbump from Boost 1.86.0 @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.51 2024/08/25 06:18:35 wiz Exp $ d4 1 a4 1 PKGREVISION= 9 @ 1.51 log @*: replace CMAKE_ARGS with CMAKE_CONFIGURE_ARGS @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.50 2024/08/17 09:18:41 wiz Exp $ d4 1 a4 1 PKGREVISION= 8 @ 1.50 log @libftdi1: fix build with Python 3.12 Fix pkglint while here. @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.49 2023/12/29 18:24:41 adam Exp $ d20 6 a25 6 CMAKE_ARGS+= -Wno-dev CMAKE_ARGS+= -DEXAMPLES=off CMAKE_ARGS+= -DDOCUMENTATION=off CMAKE_ARGS+= -DLIB_SUFFIX="" CMAKE_ARGS+= -DFTDIPP=on CMAKE_ARGS+= -DPYTHON_BINDINGS=on @ 1.49 log @revbump for boost-libs @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.48 2023/08/14 05:24:11 wiz Exp $ d32 6 a42 1 .include "../../lang/python/pyversion.mk" @ 1.48 log @*: recursive bump for Python 3.11 as new default @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.47 2023/06/06 12:40:39 riastradh Exp $ d4 1 a4 1 PKGREVISION= 7 @ 1.47 log @Mass-change BUILD_DEPENDS to TOOL_DEPENDS outside mk/. Almost all uses, if not all of them, are wrong, according to the semantics of BUILD_DEPENDS (packages built for target available for use _by_ tools at build-time) and TOOL_DEPEPNDS (packages built for host available for use _as_ tools at build-time). No change to BUILD_DEPENDS as used correctly inside buildlink3. As proposed on tech-pkg: https://mail-index.netbsd.org/tech-pkg/2023/06/03/msg027632.html @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.46 2023/04/23 14:26:16 adam Exp $ d4 1 a4 1 PKGREVISION= 6 @ 1.46 log @revbump for boost @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.45 2023/01/22 16:28:23 ryoon Exp $ d14 1 a14 1 BUILD_DEPENDS+= swig3-[0-9]*:../../devel/swig3 @ 1.45 log @*: Recursive revbump from Boost 1.81.0 @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.44 2022/06/30 11:18:15 nia Exp $ d4 1 a4 1 PKGREVISION= 5 @ 1.44 log @*: Revbump packages that use Python at runtime without a PKGNAME prefix @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.43 2022/01/10 01:46:29 ryoon Exp $ d4 1 a4 1 PKGREVISION= 4 @ 1.43 log @*: Recursive revbump from boost 1.78.0 @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.42 2021/09/29 19:00:32 adam Exp $ d4 1 a4 1 PKGREVISION= 3 @ 1.42 log @revbump for boost-libs @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.41 2021/04/21 13:24:34 adam Exp $ d4 1 a4 1 PKGREVISION= 2 @ 1.41 log @revbump for boost-libs @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.40 2021/03/07 10:51:06 kleink Exp $ d4 1 a4 1 PKGREVISION= 1 @ 1.40 log @libftdi1: Update to 1.5. New in 1.5 - 2020-07-07 ----------------------- * Implement tc[io]flush methods & deprecate broken purge_buffers methods Please check your code for ftdi_usb_purge_rx_buffer(), ftdi_usb_purge_tx_buffer() and ftdi_usb_purge_buffers() and migrate to the new ftdi_tc[io]flush() methods. Old code will continue to function, but you'll get a deprecation warning during compilation. * Add program to test buffer flush (purge) functionality * Add kernel driver auto attach/detach. See new AUTO_DETACH_REATACH_SIO_MODULE option * Add ftdi_setflowctrl_xonxoff() * ftdi_eeprom / eeprom handling: * Unify handling of all boolean eeprom flags * Add device release number support * Add channel_a_driver support for type xxR chips * Add support for group0 drive levels on x232H chips * Fix handling of high_current_drive parameter * Fix inverted handling of VCP driver field for TYPE_R chips * New --verbose option for eeprom decode operation * Add example code for async mode * Add SPDX license identifiers to the core library & ftdi_eeprom * Various python SWIG wrapper improvements * Various cmake file improvements * Fix small bugs in error code paths @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.39 2021/01/01 08:24:40 ryoon Exp $ d4 1 @ 1.39 log @*: Recursive revbump from boost-1.75.0 @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.38 2020/05/06 14:04:27 adam Exp $ d3 1 a3 2 DISTNAME= libftdi1-1.4 PKGREVISION= 2 d23 2 @ 1.38 log @revbump after boost update @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.37 2020/03/26 12:14:12 nia Exp $ d4 1 a4 1 PKGREVISION= 1 @ 1.37 log @libftdi1: Don't use lib64 suffix on Linux @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.36 2020/03/24 16:21:12 nia Exp $ d4 1 @ 1.36 log @libftdi1: Update to 1.4 New in 1.4 - 2017-08-07 ----------------------- * New ftdi_usb_open_bus_addr() open function * Use BM/R series baud rate computation for FT230X * ftdi_get_error_string() now returns const char* * C++ API: Ability to open devices with empty descriptor strings * C++ API: Fix enumerations for buffer purge and modem controls * small build fixes and improvements in the python examples * ftdi_eeprom / eeprom handling: * New API function: ftdi_eeprom_get_strings() * Fix USE_SERIAL handling for 230X type chips * Make ftdi_read_eeprom_location() endianness independent * Fix flashing of FT245R New in 1.3 - 2016-05-20 ----------------------- * Added ftdi_usb_get_strings2() to prevent automatic device close (Fahrzin Hemmati) * Added ftdi_transfer_data_cancel() for cancellation of a submitted transfer, avoided resubmittion of a canceled transfer in the callbacks, replaced calls to libusb_handle_events with libusb_handle_events_timeout_completed (Eugene Hutorny) * ftdi_eeprom / eeprom handling: * Add support for arbitrary user data (Salvador Eduardo Tropea) * Add --build-eeprom support (Salvador Eduardo Tropea) * Fix use_usb_version config file option (Thilo Schulz) * Ability to include other config files in EEPROM config file (Thilo Schulz) * Add external oscillator enable bit (Raphael Assenat) * Support channel configuration (Stephan Linz) * Added --device option to ftdi_eeprom to specify FTDI device (Robin Haberkorn) * Fixed EEPROM user-area space checks for FT232R and FT245R chips (Robin Haberkorn) * Various improvements to CBUS handling, including the EEPROM (Robin Haberkorn) * swig wrapper: Fix handling of binary strings in ftdi_write_data() for python 3 (xantares09) * cbus python example code (Rodney Sinclair) * ftdi_stream: fix timeout setting (Ларионов Даниил) * Fixed typo in CBUS defines: CBUSG_DRIVE1 -> CBUSH_DRIVE1 New in 1.2 - 2014-11-21 ----------------------- * Support for FT230X devices (Uwe Bonnes) * ftdi_usb_get_strings(): Don't try to open an already open device (Denis Sirotkin) * Support for finding devices bricked by the Windows driver (Forest Crossman) * cmake build system: New LibFTDI1ConfigVersion.cmake file (xantares09) * Fix a typo in the MPSSE command CLK_BYTES_OR_LOW (Benjamin Vanheuverzwijn) * Various small code improvements (Florian Preinstorfer, Jochen Sprickerhof, xantares09) @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.35 2020/01/12 20:20:11 ryoon Exp $ d22 1 @ 1.35 log @*: Recursive revbump from devel/boost-libs @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.34 2019/11/03 10:39:16 rillig Exp $ d3 1 a3 2 DISTNAME= libftdi1-1.1 PKGREVISION= 16 d13 2 a14 1 USE_LIBTOOL= yes d16 1 a16 2 # false warning ? The "cmake" tool is used but not added to USE_TOOLS. USE_TOOLS+= pkg-config cmake d19 3 a21 6 PYTHON_VERSIONS_ACCEPTED= 27 # not yet ported as of 1.0 BUILD_DEPENDS+= libusb1-[0-9]*:../../devel/libusb1 # It is better off to have doxygen, but # clang segfaults while packaging print/luatex #BUILD_DEPENDS+= doxygen-[0-9]*:../../devel/doxygen a27 13 do-configure: (cd ${WRKSRC} ; \ cmake \ -DEXAMPLES:BOOL=off \ -DDOCUMENTATION:BOOL=off \ -DCMAKE_BUILD_WITH_INSTALL_RPATH=TRUE \ -DCMAKE_INSTALL_PREFIX=${PREFIX} \ -DCMAKE_INSTALL_RPATH=${PREFIX}/lib \ -DCMAKE_INSTALL_RPATH_USE_LINK_PATH=FALSE \ -DLIBUSB_INCLUDE_DIR=${PREFIX}/include/libusb-1.0 \ .) # -DCMAKE_INSTALL_PREFIX=${PREFIX} converts /usr/local to ${PREFIX} d31 1 a31 1 .include "../../mk/libusb.buildlink3.mk" a32 1 .include "../../devel/swig/buildlink3.mk" a35 1 @ 1.34 log @devel: align variable assignments pkglint -Wall -F --only aligned --only indent -r No manual corrections. @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.33 2019/09/02 13:19:40 adam Exp $ d4 1 a4 1 PKGREVISION= 15 @ 1.33 log @Changed PYTHON_VERSIONS_INCOMPATIBLE to PYTHON_VERSIONS_ACCEPTED; needed for future Python 3.8 @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.32 2019/08/22 12:23:02 ryoon Exp $ d22 1 a22 1 BUILD_DEPENDS+=libusb1-[0-9]*:../../devel/libusb1 d25 1 a25 1 #BUILD_DEPENDS+=doxygen-[0-9]*:../../devel/doxygen @ 1.32 log @Recursive revbump from boost-1.71.0 @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.31 2019/07/01 04:08:05 ryoon Exp $ d20 1 a20 1 PYTHON_VERSIONS_INCOMPATIBLE= 36 37 # not yet ported as of 1.0 @ 1.31 log @Recursive revbump from boost-1.70.0 @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.30 2019/04/26 14:12:35 maya Exp $ d4 1 a4 1 PKGREVISION= 14 @ 1.30 log @fix some whitespace, mostly introduced in the previous python 3.4 / 3.5 removal commit. @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.29 2019/04/26 13:13:50 maya Exp $ d4 1 a4 1 PKGREVISION= 13 @ 1.29 log @Omit mentions of python 34 and 35, after those were removed. - Includes some whitespace changes, to be handled in a separate commit. @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.28 2019/04/25 07:32:47 maya Exp $ d20 1 a20 1 PYTHON_VERSIONS_INCOMPATIBLE= 36 37 # not yet ported as of 1.0 @ 1.28 log @PKGREVISION bump for anything using python without a PYPKGPREFIX. This is a semi-manual PKGREVISION bump. @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.27 2018/12/13 19:51:48 adam Exp $ d20 1 a20 1 PYTHON_VERSIONS_INCOMPATIBLE= 34 35 36 37 # not yet ported as of 1.0 @ 1.27 log @revbump for boost 1.69.0 @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.26 2018/08/16 18:54:41 adam Exp $ d4 1 a4 1 PKGREVISION= 12 @ 1.26 log @revbump after boost-libs update @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.25 2018/07/03 05:03:10 adam Exp $ d4 1 a4 1 PKGREVISION= 11 @ 1.25 log @extend PYTHON_VERSIONS_ for Python 3.7 @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.24 2018/04/29 21:31:33 adam Exp $ d4 1 a4 1 PKGREVISION= 10 @ 1.24 log @revbump for boost-libs update @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.23 2018/02/27 23:56:08 khorben Exp $ d20 1 a20 1 PYTHON_VERSIONS_INCOMPATIBLE= 34 35 36 # not yet ported as of 1.0 @ 1.23 log @Revbump for packages depending on devel/libusb{,compat} @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.22 2018/02/10 13:53:47 khorben Exp $ d4 1 a4 1 PKGREVISION= 9 @ 1.22 log @Import global switch for libusb's implementation [2/2] This switch is meant to be used by packages requiring an implementation of the former libusb (as in devel/libusb). The original implementation can be chosen by setting LIBUSB_TYPE to "native". The alternative implementation libusb-compat (as in devel/libusb-compat) wraps libusb1 (in devel/libusb1). This implementation can be chosen by setting LIBUSB_TYPE to "compat". On NetBSD, it has the advantage of not requiring root privileges to locate and use USB devices without a kernel driver. This second part switches packages using libusb to this framework. It does not change compilation options or dependencies at this point. Compile-tested on most packages affected and available on NetBSD/amd64. @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.21 2018/01/01 21:18:21 adam Exp $ d4 1 a4 1 PKGREVISION= 8 @ 1.21 log @Revbump after boost update @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.20 2018/01/01 18:16:36 rillig Exp $ d48 1 a48 1 .include "../../devel/libusb/buildlink3.mk" @ 1.20 log @Replaced $(ROUND) with ${CURLY} variable references. This has been a pkglint warning for several years now, and pkglint can even fix it automatically. And it did for this commit. Only in lang/mercury, two passes of autofixing were necessary because there were nested variables. @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.19 2017/08/24 20:03:11 adam Exp $ d4 1 a4 1 PKGREVISION= 7 @ 1.19 log @Revbump for boost update @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.18 2017/08/16 20:21:07 wiz Exp $ d33 1 a33 1 (cd $(WRKSRC) ; \ @ 1.18 log @Follow some http redirects. @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.17 2017/04/30 01:21:33 ryoon Exp $ d4 1 a4 1 PKGREVISION= 6 @ 1.17 log @Recursive revbump from boost update @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.16 2017/01/01 16:06:09 adam Exp $ d6 1 a6 1 MASTER_SITES= http://www.intra2net.com/en/developer/libftdi/download/ d10 1 a10 1 HOMEPAGE= http://www.intra2net.com/en/developer/libftdi/ @ 1.16 log @Revbump after boost update @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.15 2017/01/01 14:43:31 wiz Exp $ d4 1 a4 1 PKGREVISION= 5 @ 1.15 log @Add python-3.6 to incompatible versions. @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.14 2016/10/07 18:25:43 adam Exp $ d4 1 a4 1 PKGREVISION= 4 @ 1.14 log @Revbump post boost update @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.13 2016/07/09 13:03:39 wiz Exp $ d20 1 a20 1 PYTHON_VERSIONS_INCOMPATIBLE= 34 35 # not yet ported as of 1.0 @ 1.13 log @Remove python33: adapt all packages that refer to it. @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.12 2015/12/05 21:25:35 adam Exp $ d4 1 a4 1 PKGREVISION= 3 @ 1.12 log @Extend PYTHON_VERSIONS_INCOMPATIBLE to 35 @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.11 2015/04/17 15:53:01 adam Exp $ d20 1 a20 1 PYTHON_VERSIONS_INCOMPATIBLE= 33 34 35 # not yet ported as of 1.0 @ 1.11 log @Revbump after updating devel/boost-libs @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.10 2015/01/18 06:18:58 mef Exp $ d20 1 a20 1 PYTHON_VERSIONS_INCOMPATIBLE= 33 34 # not yet ported as of 1.0 @ 1.10 log @PKGREVISION++, by converting (duplicated) libconfuse to confuse. Thanks gdt@@. @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.9 2015/01/17 02:42:46 mef Exp $ d4 1 a4 1 PKGREVISION= 2 @ 1.9 log @Convert buildlink3.mk from libconfuse to (just) confuse. They duplicate. @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.8 2014/11/07 19:39:29 adam Exp $ d4 1 a4 1 PKGREVISION= 1 @ 1.8 log @Revbump after updating boost @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.7 2014/10/04 12:01:08 mef Exp $ d47 1 a47 1 .include "../../devel/libconfuse/buildlink3.mk" @ 1.7 log @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 @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.6 2014/08/13 10:57:34 adam Exp $ d4 1 @ 1.6 log @Revbump after boost-libs update @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.5 2014/06/04 06:09:44 dsainty Exp $ d3 1 a3 2 DISTNAME= libftdi1-1.0 PKGREVISION= 1 @ 1.5 log @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. @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.4 2014/05/19 22:44:14 dsainty Exp $ d4 1 @ 1.4 log @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. @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.3 2014/05/09 07:37:00 wiz Exp $ a25 3 CONFIGURE_ARGS+= --without-examples CONFIGURE_ARGS+= --without-docs d34 2 @ 1.3 log @Mark packages that are not ready for python-3.3 also not ready for 3.4, until proven otherwise. @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.2 2014/01/25 10:30:01 wiz Exp $ d53 1 @ 1.2 log @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. @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.1 2013/12/03 01:40:14 mef Exp $ d19 1 a19 1 PYTHON_VERSIONS_INCOMPATIBLE= 33 # not yet ported as of 1.0 @ 1.1 log @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. @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.5 2013/04/06 03:45:10 rodent Exp $ d19 2 d32 1 a32 1 PLIST_SUBST+= PYSITELIB=${PYSITELIB} d43 1 a43 1 # -DCMAKE_INSTALL_PREFIX=${PREFIX} converts /usr/local to ${PREFIX} @