billliner.blogg.se - Cmake link library directory

Cmake link library directory how to#

logic controller ( controller.cpp and controller.h).

hardware devices ( devices.cpp and devices.h).

Let’s say we have two separate modules for our project: We can extend our list of source files for the target executable. You can find the complete configuration files in the GitHub project accompanying this blog. Set_target_properties(Application PROPERTIES The following is a simplified project configuration file where we have omitted the compiler and linker options as we are now concentrating on source code management: cmake_minimum_required(VERSION 3.16) So far, our example project has just used a single main.cpp source file, although the supporting GitHub projects use multiple source files to build a usable ELF image.įrom the previous blog, you may remember that, for our build, we use a separate toolchain file ( toolchain-STM32F407.cmake) and a project configuration file ( CMakeLists.txt).

Managing Source FilesĪny non-trivial project will use separate source files to encapsulate different functional areas of the system. In our training courses, we have identified two shared subsystems: the bare metal code used to initialise the C/C++ run time system and a middleware layer consisting of a real-time operating system (RTOS).īefore we look at configuring subsystems, we’ll briefly discuss managing a project with multiple source and header files.

Cmake link library directory how to#

In this blog post I will look at how to configure project source code, identify subsystems and use CMake to manage the build for each subsystem. In previous blog posts in this series ( Part 1 and Part 2), I looked at using CMake to configure a build for a cross compilation to target hardware such as the STM32F4 Series.