Why Noy Use include_directories() For That¶
Discuss
include_directories("<top>/toolcase/{base,data-logger,boiling-pot}")globally
Vs.
target_include_directories()at the used node, not the using
Programming Linux
Navigation
Courses
- Courses Overview
- Slide Material
- Python Programming
- The C Programming Language
- C++: TODO List
- C++: Miscellaneous Live-Hacking
- C++
- The New C++ (11-…)
- Design Patterns With C++
- C++ Code
- C++ Exercises
- CMake
- CMake: Introduction
- CMake: Advanced Topics
- Targets, Properties, And More
- Screenplay: Public And Private Include Directories
- The Language
- Screenplay: Function Wrapping
add_library() - Screenplay: Adding
SQLite3External Dependency - Screenplay: Making
SQLite3Optional (target_compile_definitions()) - Screenplay: Making
SQLite3Optional (configure_file()) - Screenplay: Integrating
libmosquitto(MQTT - Handwritten Find-Module) - Screenplay: Generated Code (
add_custom_command()) - Running Tests
- Why Noy Use
include_directories()For That - External Dependencies
- “Configured” Header Files
- Optional Code: Problem Definition,
OPTION() - Optional Code, Approach 1: Optional
blacklist, C Macro (Global Flags) - Optional Code, Approach 2: Pushing Optionality Down In Module Interface
- Linux
- Is Software A Craft? Software Is A Craft! ⟶ Clean Code
- Unit Testing With
googletest - Linux Kernel Driver Development
- Generated Topic Graph
- How To Book
- Log Of Past Courses
About
Blog