-
Book Overview & Buying
-
Table Of Contents
-
Feedback & Rating
CMake Best Practices - Second Edition
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: “Mount the downloaded WebStorm-10*.dmg disk image file as another disk in your system.”
A block of code is set as follows:
project( "chapter1" VERSION 1.0 DESCRIPTION "A simple C++ project to demonstrate basic CMake usage" LANGUAGES CXX )
When we wish to draw your attention to a particular part of a code block, the relevant lines or items are set in bold:
include(GenerateExportHeader)
generate_export_header(hello
EXPORT_FILE_NAME export/hello/
export_hello.hpp)
target_include_directories(hello PUBLIC "${CMAKE_CURRENT_BINARY_DIR}
/export")
Any command-line input or output is written as follows:
cmake -G "Unix Makefiles" -DCMAKE_CXX_COMPILER=/usr/bin/g++-12 -S . -B ./build
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: "Although CMake is quite well integrated into many IDEs and editors, it is essentially a command-line tool, so learning how to use CMake in the command-line interface (CLI) is essential to use it to its full potential".
Tips or important notes
Appear like this.