From da432cdc35ddc3e2e1374f7fc46210b4a92e6f54 Mon Sep 17 00:00:00 2001 From: Harald Welte Date: Sun, 15 Dec 2019 19:13:26 +0100 Subject: libosmocore libusb integration Osmocom applications typically use libosmocore select.[ch] event loop code as their main event dispatch mechanism. When they want to deal with libusb in a non-blocking/asynchronous way, they need to integrate libusb into that select(). The new libosmousb is doing exactly that: Providing a shared utility library for Osmocom programs that wish to use libusb. This is useful for example in simtrace2 host utilitie as well as osmo-e1d. Change-Id: I656a1a38cbb5b1f3a9145d2869d3b4d0adefcae3 Closes: OS#4299 --- contrib/jenkins_arm.sh | 1 + 1 file changed, 1 insertion(+) (limited to 'contrib') diff --git a/contrib/jenkins_arm.sh b/contrib/jenkins_arm.sh index 8ee90f03..c9cd922e 100755 --- a/contrib/jenkins_arm.sh +++ b/contrib/jenkins_arm.sh @@ -19,6 +19,7 @@ build() { --disable-doxygen \ --disable-shared \ --disable-libsctp \ + --disable-libusb \ --enable-external-tests \ CFLAGS="-Os -ffunction-sections -fdata-sections -nostartfiles -nodefaultlibs $WERROR_FLAGS" -- cgit v1.2.3