Compiling OpenThread samples via Visual Studio Code method?

[HeneryH]

Trying to build the OpenThread sample programs (coap_server and coap_client) and am running into some problems that I hope someone might recognize as an easy fix.

In the documentation for these apps, it says there are some prerequisites.

Configuring Thread in nRF Connect SDK

The first problem I am facing is just complete uncertainty of how to do these things in the VIsualStudio Code method.  I can see something like the modules if I click on the kconfig item in VS and bring up the checklist of optional modules but it is unclear exactly which ones should be turned on.

Editing the other items I have no idea how to accomplish.

Second item is that my current compilation attempt (for the client) is erroring out on being able to find the coap_server_client_interface.h file.  This file is present in the server directory but not the client directory(it is in "C:\nrf_apps\ot_coap_server\interface\coap_server_client_interface.h" but I am in the client build).  Might that be solved by fixing #1 or is this a separate issue?

So sorry for the NOOB problems.  Thank you for any advice.

[Edvin]

Hello,

If your question is how to enable configs in VS Code or in the nRF Connect SDK (NCS), then yes, this is done in the prj.conf file. 

These are already set in the prj.conf for the sample.

Second item is that my current compilation attempt (for the client) is erroring out

Is that the coap_client sample, or your client?

Did it not compile out of the box? Or are you trying to add the coap client to another application?

Best regards,

Edvin

[HeneryH]

Out of the box client build fails for finding that noted .h file which happens to exist in the server directory.

[Edvin]

Ah, yes. I see that the coap_client depends on the coap_server to be located in the same folder. I see that I just copied both of those samples to the same folder, and then they should compile. So you can either do that, or you can copy the files that are needed, and redirect what folder the client sample should look for them using the coap_client\CMakeLists.txt:

Best regards,

Edvin

[HeneryH]

Yes, thank you.  Sorry for the mistake on my part.