Using qiBuild CMake API

• Creating a binary
  • Basic CMake
  • Adding an executable
• Creating a library
  • Requirements
  • The answer library
  • Using the answer library
    • Adding the include directories
    • Creating the answer library
    • Link the foo executable with the answer library
  • Building
  • Conclusion
• Using qi_install functions
  • Components
  • Using qibuild install
  • Install functions, destination, components
  • Other use cases
  • Special features
    • Check of arguments
    • Support of glob and directories
    • “IF” keyword
    • SUBFOLDER and KEEP_RELATIVE_PATHS keywords
      • Using SUBFOLDER
      • Using KEEP_RELATIVE_PATHS
• Unit testing
  • Adding a test
  • Important
• Managing configuration files
• Managing data
  • The problem
  • The solution
  • How it works
    • When run from the build dir
    • When installed
• Writing a custom -config.cmake module file
  • Simplest case
  • Finding libraries with different names
  • Finding include directories with prefixes
  • Headers-only libraries
  • Finding in non standards paths
  • Finding pkg-config libraries
• Using qi_stage_lib
  • Basic usage
  • Advanced usage
    • Using qi_stage_lib with custom DEPENDS
    • Using qi_stage_lib with INCLUDE_DIRS
    • Using qi_stage_lib with PATH_SUFFIXES
• Using host tools for cross compilation