Unable to generate compile commands in OpenThread CLI Example

RE: Unable to generate compile commands in OpenThread CLI Example

Øyvind — Fri, 01 Oct 2021 07:18:50 GMT

Hey Allen, can you please elaborate more on what issues you are getting? The best is to open a new ticket with your issues, this for us to keep track of issues with the VS code extension.

Thank you!

Kind regards,
Øyvind

RE: Unable to generate compile commands in OpenThread CLI Example

Allen — Thu, 30 Sep 2021 17:17:27 GMT

I am having the same issue. Here is the VCS plugin screen when configuring the project. This is with SDK v1.7.0 on a Mac

RE: Unable to generate compile commands in OpenThread CLI Example

AustinE — Wed, 29 Sep 2021 14:50:27 GMT

Hello,

I'm currently using the VS code extension. I believe I set that profile(or what that config is called) but the normal "proj.conf" didn't work either.

RE: Unable to generate compile commands in OpenThread CLI Example

Øyvind — Mon, 27 Sep 2021 12:13:46 GMT

Hello,

Can you please elaborate on how you are building the project? Are you using command line or the VS Code extension? I'm very curious to why it executes west build with -DCONF_FILE:STRING=[PATH]/otcli/prj_nrf5340dk_nrf5340_cpuapp.conf when you are building for board --board nrf52840dk_nrf52840

Kind regards,
Øyvind

RE: Unable to generate compile commands in OpenThread CLI Example

AustinE — Sat, 25 Sep 2021 02:40:17 GMT

"[PATH]" is the path to where the sample was saved. For me /Users/<username>/git/nrf/otcli/prj...

RE: Unable to generate compile commands in OpenThread CLI Example

Øyvind — Fri, 24 Sep 2021 07:01:41 GMT

A follow-up to my previous comment. What is [PATH] configured to? Where is the project folder located? You have also pulled in config files for nRF5340 in the build command: [PATH]/otcli/prj_nrf5340dk_nrf5340_cpuapp.conf

-Øyvind

RE: Unable to generate compile commands in OpenThread CLI Example

Øyvind — Fri, 24 Sep 2021 06:36:17 GMT

Hello,

There is an issue with paths i.e. [PATH]/otcli/../common/overlay-ot-defaults.conf which we are aware of. I will forward this to the developers and get back to you with a work-around.

Kind regards,
Øyvind