You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Build the Ubxlib GNSS Sample in bridle/samples/ubx_gnss leads to build error: missing include file u_timeout.h.
To Reproduce
Steps to reproduce the behavior:
west workspace from Bridle main branch
west build -b nucleo_f413zh -p -d build/nucleo_f413zh-ubx_gnss bridle/samples/ubx_gnss
See error
Expected behavior
Build w/o any error as before.
Impact
Showstopper, can't use the sample and also the ubxlib API as Bridle module.
Logs and console output
In file included from .../ws/bridle/samples/ubx_gnss/src/main.h:10,
from .../ws/bridle/samples/ubx_gnss/src/shell.c:10:
.../ws/modules/lib/ubxlib/ubxlib.h:75:10: fatal error: u_timeout.h: No such file or directory
75 | #include <u_timeout.h>
| ^~~~~~~~~~~~~
Screenshots
If applicable, add screenshots to help explain your problem.
Development Environment (please complete the following information):
OS: [e.g. Linux, MacOS, Windows]
Toolchain (e.g Zephyr SDK, ...)
Commit SHA or Version [e.g. 0.2.5] used
Additional context
Since u-blox/ubxlib@79e808e on ubxlib upstream the CMake configuration have to respect the new uTimeout API in Bridle module too.
The text was updated successfully, but these errors were encountered:
Describe the bug
Build the Ubxlib GNSS Sample in
bridle/samples/ubx_gnss
leads to build error: missing include fileu_timeout.h
.To Reproduce
Steps to reproduce the behavior:
Expected behavior
Build w/o any error as before.
Impact
Showstopper, can't use the sample and also the
ubxlib
API as Bridle module.Logs and console output
Screenshots
If applicable, add screenshots to help explain your problem.
Development Environment (please complete the following information):
Additional context
Since u-blox/ubxlib@79e808e on ubxlib upstream the CMake configuration have to respect the new uTimeout API in Bridle module too.
The text was updated successfully, but these errors were encountered: