Mastering Cmake Pdf Verified

if(MyLib_FOUND AND NOT TARGET MyLib::MyLib) add_library(MyLib::MyLib UNKNOWN IMPORTED) set_target_properties(MyLib::MyLib PROPERTIES IMPORTED_LOCATION "$MyLib_LIBRARY" INTERFACE_INCLUDE_DIRECTORIES "$MyLib_INCLUDE_DIR" ) endif()

The most common use case for CMake involving PDFs is automating the build of technical documentation.

This article is part of the “Mastering Build Systems” series. Next up: Mastering Ninja – Speeding Up Your CMake Builds. mastering cmake pdf

# 3. Add a custom target to build the PDF # We run pdflatex twice to ensure references/TOC are updated correctly add_custom_command( OUTPUT $LATEX_OUTPUT COMMAND $PDFLATEX_COMPILER -output-directory=$CMAKE_CURRENT_BINARY_DIR $LATEX_SOURCE COMMAND $PDFLATEX_COMPILER -output-directory=$CMAKE_CURRENT_BINARY_DIR $LATEX_SOURCE DEPENDS $LATEX_SOURCE COMMENT "Building PDF documentation from manual.tex" VERBATIM )

Mastering CMake is not about memorizing every command—it’s about embracing its . A well-written CMake project: mastering cmake pdf

:

If you are searching for digital copies or supplementary guides, several high-quality references are available: mastering cmake pdf

include(CMakePackageConfigHelpers) write_basic_package_version_file( "$CMAKE_CURRENT_BINARY_DIR/MyProjectConfigVersion.cmake" VERSION $PROJECT_VERSION COMPATIBILITY SameMajorVersion )

CMake’s built-in testing is trivial to use:

include(FindPackageHandleStandardArgs) find_package_handle_standard_args(PoDoFo DEFAULT_MSG PoDoFo_LIBRARY PoDoFo_INCLUDE_DIR)