| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
|
|
|
|
| |
This way libosmocore build fails during configuring phase if expected
default behavior (building with libsctp support enabled and providing
osmo_sock_init2_multiaddr() API) fails. User is still provided with
--disable-libsctp option in case he doesn't need those features or his
environment doesn't provide required libsctp APIs.
Change-Id: I710c9cb1c6da0e5fc94b792df8bf60194a72208f
|
| |
|
|
|
|
| |
Run the new logging_vty_test.vty VTY transcript test in our CI.
Change-Id: Ic4ec1f6c131da50b3956f16f0b49375f387196b3
|
| |
|
|
| |
Change-Id: I45ab11b461a35923853f38b5bedd5025f53cc5b5
|
| |
|
|
|
|
|
| |
If we're cross-compiling for arm-none-eabi, we cannot execute test
programs.
Change-Id: I64e88a31091b67c37c308c44013c42d4574d2312
|
| |
|
|
| |
Change-Id: Ied8c1085b8bee2cc4fa65592e805838b8cdae287
|
|
|
Similar to the way we test osmo-bts, add simple dispatcher script which
calls appropriate test depending on a given parameter. This will allow
to simplify the job description. While at it, also rename jenkins-arm.sh
-> jenkins_arm.sh to match the OsmoBTS.
The older scripts are preserved for compatibility and shall be removed
once we update job description in osmo-ci.
Change-Id: I2955e866bce4f000a53369bd601a346c36c82468
|
