> On 5 Apr 2022, at 3:08 pm, Christoph Kukulies <[email protected]> wrote: > > Thanks. Assumed I have downloaded a binary release from libusb’s github > Releases and it looks like that in the tree: > > $ find macos_11.6 > macos_11.6 > macos_11.6/.DS_Store > macos_11.6/bin > macos_11.6/bin/dpfp > macos_11.6/bin/listdevs > macos_11.6/bin/sam3u_benchmark > macos_11.6/bin/fxload > macos_11.6/bin/xusb > macos_11.6/bin/testlibusb > macos_11.6/bin/hotplugtest > macos_11.6/bin/stress > macos_11.6/include > macos_11.6/include/.DS_Store > macos_11.6/include/libusb-1.0 > macos_11.6/include/libusb-1.0/libusb.h > macos_11.6/lib > macos_11.6/lib/pkgconfig > macos_11.6/lib/pkgconfig/libusb-1.0.pc > macos_11.6/lib/libusb-1.0.dylib > macos_11.6/lib/libusb-1.0.0.dylib > macos_11.6/lib/libusb-1.0.a > macos_11.6/lib/libusb-1.0.la > > How can I make these active in libusb-devel or otherwise available?
You cannot. Macports strongly prefers to build ports from source itself, and only redistributes rebuilt binaries in extreme circumstances. You need to update the port file to fetch and then build a newer github revision for the devel subport. See https://github.com/macports/macports-ports/blob/584723a8c2a65990bd0566b226f8c31b7f30fce5/devel/libusb/Portfile See line 60 onwards. That said, the devel port currently builds a revision that appears to be from the 3rd of April this year, so is pretty recent. Is this not new enough ? Chris > > Do the pkgconfig .pc files play a role in the installation mechanism? > > — > Christoph > >> Am 05.04.2022 um 15:36 schrieb Chris Jones <[email protected]>: >> >> >>> On 05/04/2022 1:54 pm, Christoph Kukulies wrote: >>> Thanks. Nonetheless I don‘t get how I can aim at a specific version or >>> 1.0.26-rc1 „HEAD“ >> >> you cannot. You still get whatever version libusb-devel is current set to >> provide. The idea of a X-devel port though is these can be updated and >> tested without affecting the default X port. >> >> If you want a different version than libusb-devel currently provides, then >> you need to update the port to provide this. >> >>> Btw, what is the correspondent to >>> ldd >>> under macOS? >> >> otool -L >> >>> — >>> Christoph >>>> Am 05.04.2022 um 12:56 schrieb Chris Jones <[email protected]>: >>>> >>>> >>>> >>>>> On 05/04/2022 11:50 am, Christoph Kukulies wrote: >>>>> $ sudo port deactivate libusb @1.0.25_0 >>>>> Password: >>>>> Note: It is not recommended to uninstall/deactivate a port that has >>>>> dependents as it breaks the dependents. >>>>> The following ports will break: >>>>> libusb-compat @0.1.7_0 >>>>> openocd @0.11.0_0 >>>>> usbutils @007_1 >>>>> libftdi1 @1.5_1 >>>>> qemu @6.2.0_0 >>>>> stlink @1.7.0_1 >>>>> Continue? [y/N]: >>>>> >>>>> OK to continue? >>>> >>>> yes. >>>> >>>> ports that depend on libusb should use a path style dependency, to allow >>>> libusb or libusb-devel to satisfy it >>>> >>>> path:lib/pkgconfig/libusb-1.0.pc:libusb >>>> >>>> so assuming you are about to install libusb-devel its fine. >
