"Add New File To CMakeLists.txt" option missing

[Chris Pearson]

I am working through the Getting Started documentation for the nRF Connect SDK 1.5.1 on a Windows 10 machine running SEGGER Embedded Studio Nordic Edition Windows x64, Release 5.34a Build 2021011401.44914. So far the examples compile and download to my device successfully.

In the section Maintaining CMakeLists.txt in SES, the documentation refers to right-clicking the "Project 'app/libapp.a' to find the functions "Add New File To CMakeLists.txt" and "Add Existing File To CMakeLists.txt". However, these functions are not present when I right-click:

According to the documentation, the following is expected:

Also missing is the "Edit Compile Options in CMakeLists.txt" option at the bottom of the menu.

I have tried a couple of different example projects from the "Open nRF Connect SDK Project" menu and this is the case for all of them.

Am I missing something here? 

Thanks!

[Håkon Alseth]

Hi,

 

For a project to be able to add files to the CMakeListst.txt file, they need this tag:

https://developer.nordicsemi.com/nRF_Connect_SDK/doc/1.5.1/nrf/gs_modifying.html#ses-tags-in-cmakelists-txt

 

Projects in the sdk-nrf all have these tags, but zephyr samples does not, unfortunately. In that case, the tags need to be manually added to the CMakeLists.txt.

 

Kind regards,

Håkon

[Chris Pearson]

Hi Håkon Alseth. While we're talking about documentation, another thing I ran into is the configure tool in the  "Project->Configure nRF Connect SDK Project" menu. I don't think it's mentioned in the documentation at all, but it's definitely a useful tool.

[Håkon Alseth]

I believe you're right.

I will add this to the docs improvement list! Thank you very much for reporting this back to us!

 

Note that this is the equivilant to running "menuconfig" (or "guiconfig") from command line. Please note that the changes you do is only valid for your specific build folder, and not saved into the prj.conf file.

 

Kind regards,

Håkon

[Chris Pearson]

Ah, good to know, thanks Håkon Alseth!

I do actually have a bunch of notes regarding the setup process through the nRF Connect for Windows "Getting Started Assistant". I ran into a few problems and, given how "friendly" that assistant is, they're things that should probably be taken care of to polish it up a bit. Where should such a list be sent?

Thanks!

[Håkon Alseth]

Hi Chris!

 

I have made our product manager aware of this specific devzone thread, so just feel free to add your comments to this thread.

Again, I have to thank you for taking the time to help us improve on these topics, as we do aim to ease the process of installing dependencies (sdk, toolchain, etc) and helping to make the process take as little time away from you, the developer, so that you can focus on developing and running firmware instead.

 

Kind regards,

Håkon

[Chris Pearson]

Hi Håkon Alseth. Here's another comment for you regarding the SDK setup.

I must have missed this the first time through, but the start of the "Getting Started Assistant" v1.1.2 has a big deprecation warning:

Deprecation warning

For nRF Connect SDK v1.2.0 (and later), this app has been replaced by the Toolchain Manager app. Go to the app overview to install and open the Toolchain Manager.

However, the nRF Connect SDK documentation clearly directs the user to use the Getting Started Assistant. Obviously there is a conflict there.

An additional problems with the Toolchain Manager is that it does not put any of the installed tools onto the path. (Windows 10 at least.) So, while it may have installed west, it cannot be used easily.

[Håkon Alseth]

Hi Chris!

 

Chris Pearson said:

An additional problems with the Toolchain Manager is that it does not put any of the installed tools onto the path. (Windows 10 at least.) So, while it may have installed west, it cannot be used easily.

 This is something I've also noticed, but I have forgotten to report internally when looking through our bugs. I believe we're mixing due to the launch of toolchain manager, and the manual setup via getting started.

I will report this!

 

Chris Pearson said:

Here's another comment for you regarding the SDK setup.

I must have missed this the first time through, but the start of the "Getting Started Assistant" v1.1.2 has a big deprecation warning:

Deprecation warning

For nRF Connect SDK v1.2.0 (and later), this app has been replaced by the Toolchain Manager app. Go to the app overview to install and open the Toolchain Manager.

However, the nRF Connect SDK documentation clearly directs the user to use the Getting Started Assistant. Obviously there is a conflict there.

Yes, this is correct. We have bundled the whole SDK (incl. deps) in the toolchain manager, but we clearly have improvements to do here.

The layout of where you would normally click, here highlighted:

 

These are, atleast in my mind, the path of least resistance when looking at heading/sub-headings.

By only looking at the left-hand frame, my mind assumes that this is the proper way: "I want to get started, install, and here's an assistant"

 

However, that is unfortunately not the simplest way to get started at this time. I'll work together with our technical writers to improve upon this.

 

Kind regards,

Håkon