#34091: libftdi should able to use libusb-devel -----------------------------------+---------------------------------------- Reporter: jerkejacobs@… | Owner: snc@… Type: enhancement | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: libftdi -----------------------------------+---------------------------------------- Changes (by snc@…): * status: new => assigned Comment: I'll need to double check the files provided by both ports, but I aim to use a path dependency so that either one can be used and only if none are available do we pull in libusb. {{{ path:lib/pkgconfig/libusb-1.0.pc:libusb }}} -- Ticket URL: <https://trac.macports.org/ticket/34091#comment:2> MacPorts <http://www.macports.org/> Ports system for Mac OS

#34091: libftdi should able to use libusb-devel ------------------------------------+--------------------------------------- Reporter: jerkejacobs@… | Owner: snc@… Type: enhancement | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: libftdi | ------------------------------------+--------------------------------------- Changes (by adfernandes@…): * status: assigned => closed * resolution: => fixed Comment: I just committed a major revision to `libusb` and friends in #34338 (r92944). The `libusb-devel` was replaced by `libusb`, so `libusb-devel` is no longer needed. At the pace if `libusb` development, I doubt we'll need another `-devel` branch soon. I'm guessing that this ticket can be closed. -- Ticket URL: <https://trac.macports.org/ticket/34091#comment:4> MacPorts <http://www.macports.org/> Ports system for Mac OS