#include errors

[SerJoG]

Zephyr Commit hash

b05b8ad63acf30e08a570ce553831a06db27a2e0

Golioth SDK Commit Hash

11d19a7cc599f2ebc0cdd8b8613bbcb0e482aa72

Hardware Target

nRF91

What host OS are you using?

PRETTY_NAME="Ubuntu 22.04.2 LTS" NAME="Ubuntu" VERSION_ID="22.04" VERSION="22.04.2 LTS (Jammy Jellyfish)" VERSION_CODENAME=jammy ID=ubuntu ID_LIKE=debian HOME_URL="https://www.ubuntu.com/" SUPPORT_URL="https://help.ubuntu.com/" BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/" PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy" UBUNTU_CODENAME=jammy

Current Behavior

fatal error when building with golioth on existing west project caused by: ncs/modules/lib/golioth/include/net/golioth/lightdb.h:11:10: fatal error: zephyr/net/coap.h: No such file or directory 11 | #include <zephyr/net/coap.h> | ^~~~~~~~~~~~~~~~~~~ compilation terminated.

Same for: lightdb.h, rpc.h, settings.h, stream.h, golioth.h. For: rpc.h, golioth.h (<zephyr/kernel.h> to <kernel.h>). For: golioth.h (<zephyr/net/tls_credentials.h> to <net/tls_credential.h>)

Expected Behavior

no fatal error.

Steps To Reproduce

1. Add golioth to existig west project like in the guide. (p.s. in west.yml in addition to paste the code under "project:" you have to add golioth some line above as it says the yaml itself.
2. Implement dfu sample but probably any samples.
3. Make build.
4. fatal error appears.

Logs, console output, or any kind of debug information

No response

[mniestroj]

@SerJoG Could you please elaborate on how you exactly create such a project? It is possible to include the contents of west.yml, most importantly how you added this SDK into your downstream project? It would be even better if you could create such a downstream sample project, which exactly reproduces this issue.

We have our downstream tests with west-ncs.yml and did not discover any issues. I suspect there is some problem with setting up west on your side.