Adding header and source files to nRF Connect SDK Project

RE: Adding header and source files to nRF Connect SDK Project

Alan — Sun, 07 Mar 2021 17:35:29 GMT

An easier way to reload the project is to:

Save CMakeLists.txt
Edit the configuration (Project->Configure nRF Connect SDK Project)
Click the Configure button

After that, my new c file appears in the project list. A little clumsy, but works.

RE: Adding header and source files to nRF Connect SDK Project

SergeiA — Mon, 28 Dec 2020 06:59:29 GMT

Unfortunately, editing CMakeLists.txt and even reloading project after that doesn't work. Your modification of SES generates .emProject file only once, when user executes command "Open nRF Connect SDK project". After that any changes to CMakeLists.txt will not update build.emProject and new files will not be included into build.

So to add new .c file I have run this command again, select board, select folder in combo box (which seems always points to obscure wrong folder), check "clear build folder" and wait until whole enchilada will be regenerated again.

Is it that hard to reinterpret CMake file when it is changed and update Segger project file? That what other IDEs based on CMake do.

Regards,

Sergei

RE: Adding header and source files to nRF Connect SDK Project

kgarland789 — Tue, 13 Oct 2020 18:44:19 GMT

Hi Carl,

This is great, and makes perfect sense! thanks for the example.

Sincerely,

Kyle Garland

RE: Adding header and source files to nRF Connect SDK Project

Carl Richard — Tue, 13 Oct 2020 08:32:56 GMT

Hi again, Kyle!

Good to hear. CMakeLists must indeed be updated as you have shown here, but note that the Zephyr documentation recommends that both source and header files are located under the src directory. You can have a look at this small hello world sample I've put together here: devzone.nordicsemi.com/.../8540.hello_5F00_world.zip. What's worth noting is that every subdirectory of src should contain it's own CMakeLists targeting the source code of that module. You can see this in the sample I've added here.

You should not need to do anything else than updating CMakeLists according to your project contents, and updating your #includes.

Hope this makes sense!

Best regards,
Carl Richard

RE: Adding header and source files to nRF Connect SDK Project

kgarland789 — Fri, 09 Oct 2020 17:49:29 GMT

Hi Carl,

Thank you for your response! I found the src folder in the project directory and that seems to do the trick. Would I need to then do something in CMakeList.txt like:

zephyr_include_directories(include)
zephyr_library_include_directories(include)

add_subdirectory(src/https)

add_subdirectory(src/gps)

add_subdirectory(src/device_drivers)

And then after, would I need to add dependencies for each specific project? Like If I'm starting with https_client and want to add the gps code, do I need to change the project dependencies to include the gps project.

RE: Adding header and source files to nRF Connect SDK Project

Carl Richard — Fri, 09 Oct 2020 09:50:31 GMT

Hi, Kyle!

This is unfortunate behavior. I will take further internally. In the meantime I recommend doing the addition of header and source files manually by:
1. Navigating to the project folder either using the file explorer or a terminal.
2. Placing your .c files in the src folder located there.
3. Making an "include" folder where you place your header files.
4. Edit CMakeList.txt directly as described in our sample modification guide.

Note that you may need to reload your SES project after changing CMakeLists.txt.

Hope this helps!

Best regards,
Carl Richard

RE: Adding header and source files to nRF Connect SDK Project

kgarland789 — Wed, 07 Oct 2020 18:43:22 GMT

EDIT: Also it looks like I can't even add a new folder because that option is grayed out when I right click on Project 'app/libapp.a'. Is this where a new folder even goes?