Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] ubxlib: missing header u_timeout.h #215

Closed
rexut opened this issue May 3, 2024 · 0 comments · Fixed by #220
Closed

[BUG] ubxlib: missing header u_timeout.h #215

rexut opened this issue May 3, 2024 · 0 comments · Fixed by #220
Assignees
Labels
bug Something isn't working
Milestone

Comments

@rexut
Copy link
Member

rexut commented May 3, 2024

Describe the bug

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:

  1. west workspace from Bridle main branch
  2. west build -b nucleo_f413zh -p -d build/nucleo_f413zh-ubx_gnss bridle/samples/ubx_gnss
  3. 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.

@rexut rexut added the bug Something isn't working label May 3, 2024
@rexut rexut self-assigned this May 3, 2024
@rexut rexut added this to the v3.6.99 milestone May 5, 2024
@rexut rexut modified the milestones: v3.6.99, v3.6.1 May 9, 2024
@rexut rexut linked a pull request May 9, 2024 that will close this issue
@rexut rexut closed this as completed May 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant