In CMake, functions are used to encapsulate a reusable block of code. Below is a detailed explanation of defining and calling functions in CMake. Defining Functions Function definitions start with function(), followed by the function name and any parameter list, as shown below: function(<function_name> [arg1 [arg2 […]]]) # Function code… endfunction() The function name should … Read more
Introduction to CMakeLists<span>CMakeLists.txt</span> file is the input file for the CMake build system used to build software packages. Any package that conforms to the CMake specification contains one or more <span>CMakeLists.txt</span> files that describe how to build the code and where to install it. The <span>CMakeLists.txt</span> file used for catkin projects is a standard CMakeLists.txt … Read more
Word count: 7897, approximately 40 minutes of reading time Comprehensive Guide to CMakeLists (Part 1) 0. CMake Application Examples Previously, we organized content on using CMake to introduce third-party libraries (header file directories, library directories, library files). However, the content organized here is not complete. Therefore, we need to further organize the usage of CMake … Read more
Previous exciting content:CMake Hello, WorldCMake VariablesCMake Official Tutorial (Basic Project Setup)CMake Official Tutorial (Library Creation)CMake Official Tutorial (Usage Requirements)CMake Official Tutorial (Installation and Testing)CMake Common Syntax (if Statement) In the previous article on CMake Variables, we briefly mentioned cache variables but did not elaborate on them. Today, we will organize the common syntax for cache … Read more
Foundation of Modular Builds: In-Depth Practice from Directory Isolation to Variable Passing 1. Why is Multi-Directory Project Management Necessary? As the project scales to hundreds of source files, piling all code into a single directory leads to: Difficult Maintenance: Hard to quickly locate the code corresponding to a module or function Low Compilation Efficiency: Full … Read more
Enabling Link Time Optimization (LTO) in CMake can significantly enhance program performance and sometimes reduce the size of the final binary. LTO allows the compiler to perform optimizations across the entire program rather than just within individual source files. Below is a detailed guide on how to enable and configure LTO in CMake projects.1. Enabling … Read more
Previous Exciting Content:CMake Hello, WorldCMake VariablesCMake Official Tutorial (Basic Project Setup)CMake Official Tutorial (Library Creation)CMake Official Tutorial (Usage Requirements)CMake Official Tutorial (Installation and Testing)CMake Common Syntax (if Statement)CMake Common Syntax (Cache Variables) In CMake, environment variables have the following characteristics: 1. The scope of environment variables is global and they are not cached. 2. They … Read more
In-depth analysis<span>function()</span> and <span>macro()</span> differences, mastering variable arguments and cross-platform compilation practical applications. 1. <span><span>function()</span></span> and <span><span>macro()</span></span> essential differences 1.1 Scope and Variable Passing <span>function()</span>: Local Scope: Variables (including parameters) defined inside the function are only valid within the function and are not visible externally. Parameter Passing: Passed by value, modifications to parameters within the … Read more
1. Why is it important to understand variables and scope? CMake is not just a build tool, but also a “meta-programming language”. Variables and scope are its core programming elements, directly affecting: Project Configuration: Dynamically switching compilers, library paths, and compilation options Module Interaction: Data transfer between parent and child directories Environment Control: Cross-platform compatibility … Read more
cmake_minimum_required(VERSION 3.0)project(MyProject VERSION 1.0) # Specify the output path for the executable set(CMAKE_RUNTIME_OUTPUT_DIRECTORY ${CMAKE_SOURCE_DIR}/bin/$<CONFIG>) # Specify the output path for dynamic libraries set(CMAKE_LIBRARY_OUTPUT_DIRECTORY ${CMAKE_SOURCE_DIR}/bin/$<CONFIG>) # Specify the output path for static libraries set(CMAKE_ARCHIVE_OUTPUT_DIRECTORY ${CMAKE_SOURCE_DIR}/bin/$<CONFIG>) set(SRC_LIST add.c subtract.c main.c)add_executable(demo01 ${SRC_LIST}) File paths and execution results