Building nRF5340 project with multiple external dependencies that depend on each other

RE: Building nRF5340 project with multiple external dependencies that depend on each other

Einarh — Thu, 17 Aug 2023 08:28:02 GMT

[quote user="Omegaki113r"]But is there a way that instead of makefile on the external project to use CMake on there as well?[/quote]

I think that should be possible, maybe you could look to the Asset Tracker application for inspiration:

https://github.com/nrfconnect/sdk-nrf/tree/main/applications/asset_tracker_v2

There multiple CMakeLists.txt files are chained to include modules, using add_subdirectory() and target_include_directories().

[quote user="Omegaki113r"]there is a linking error. that the ADSController library cant find the C functions from the SPIController.c[/quote]

This might also be fixed with the above approach I think, adding all source files to your main project's target sources.

-Einar

RE: Building nRF5340 project with multiple external dependencies that depend on each other

Omegaki113r — Wed, 16 Aug 2023 18:07:48 GMT

Yes. this Stackoverflow thread helped to make the code compile. Compilation is happening successfully now. But there is a linking error. that the ADSController library cant find the C functions from the SPIController.c

but let me look into that more before i get back to you. most likely a typo in my end.

RE: Building nRF5340 project with multiple external dependencies that depend on each other

Omegaki113r — Wed, 16 Aug 2023 18:06:17 GMT

Quick question before that.

So the projects created by the VSCode for Zephyr is based on CMake. But the external project example (external project itself) is using makefile. I know this is written like that to show that the Zephyr can build project that get build from other build systems as well.

But is there a way that instead of makefile on the external project to use CMake on there as well?

Do we have guidance to do that?

RE: Building nRF5340 project with multiple external dependencies that depend on each other

Einarh — Wed, 16 Aug 2023 11:50:27 GMT

I think that just makes them compile in the right order, which is good, but you'll have to make sure the SPI project header file is visible to your ADS project.

Which would be done by including the SPI project in your ADS project's makefile I believe, have a look here, I believe this case is pretty similar to yours:

https://stackoverflow.com/questions/15045748/how-to-use-external-libraries-and-headers-in-c-makefile

-Einar

RE: Building nRF5340 project with multiple external dependencies that depend on each other

Omegaki113r — Tue, 15 Aug 2023 13:09:31 GMT

yeah.
i haven't done something like that.

i thought putting this on the main project's CMakeLists.txt took care of that

So it seems like that doesn't take care of it.

can you explain how/what i need to put on the "OmegaADS129xController" makefile to make the code compile.

RE: Building nRF5340 project with multiple external dependencies that depend on each other

Einarh — Tue, 15 Aug 2023 09:17:13 GMT

Hello

I would suspect that you'll have to include the SPI controller project in the makefile of your OmegaADS129xController project, since your ADS project needs to find the OmegaSPIController.h file.

As far as I can see you haven't done this, or am I missing something?

Best regards,

Einar