-
Book Overview & Buying
-
Table Of Contents
CMake Best Practices
By :
There are a number of text conventions used throughout this book.
Code in text: Indicates code words in text, database table names, folder names, filenames, file extensions, pathnames, dummy URLs, user input, and Twitter handles. Here is an example: "FILES_MATCHING cannot be used after PATTERN or REGEX but it can be done vice versa."
A block of code is set as follows:
include(GNUInstallDirs)
install(DIRECTORY dir1 DESTINATION ${CMAKE_INSTALL_
LOCALSTATEDIR} FILES_MATCHING PATTERN "*.x")
install(DIRECTORY dir2 DESTINATION ${CMAKE_INSTALL_
LOCALSTATEDIR} FILES_MATCHING PATTERN "*.hpp"
EXCLUDE PATTERN "*")
install(DIRECTORY dir3 DESTINATION ${CMAKE_INSTALL_
LOCALSTATEDIR} PATTERN "bin" EXCLUDE)
When we wish to draw your attention to a particular part of a code block, the relevant lines or items are set in bold:
# ... -- Installing: /tmp/install-test/qbin/ch4_ex01_executable
Any command-line input or output is written as follows:
install(DIRECTORY dir1 dir2 dir3 TYPE LOCALSTATE)
Bold: Indicates a new term, an important word, or words that you see onscreen. For instance, words in menus or dialog boxes appear in bold. Here is an example: "To start configuring a project, select the project's root directory by clicking the Browse Source… button."
Tips or Important Notes
Appear like this.