cmake-presets – CMakePresets.json Introduction One problem that CMake users often face is sharing settings with other people for common ways to configure a project. This may be done to support CI builds, or for users who frequently use the same build. CMake supports two files, CMakePresets.json and CMakeUserPresets.json, that allow users to specify common configure…
cmake-policies – CMake Policies Reference Introduction Policies in CMake are used to preserve backward compatible behavior across multiple releases. When a new policy is introduced, newer CMake versions will begin to warn about the backward compatible behavior. It is possible to disable the warning by explicitly requesting the OLD, or backward compatible behavior using the…
cmake-packages – CMake Packages Reference Introduction Packages provide dependency information to CMake based buildsystems. Packages are found with the find_package() command. The result of using find_package() is either a set of IMPORTED targets, or a set of variables corresponding to build-relevant information. Using Packages CMake provides direct support for two forms of packages, Config-file Packages…
cmake-modules – CMake Modules Reference The modules listed here are part of the CMake distribution. Projects may provide further modules; their location(s) can be specified in the CMAKE_MODULE_PATH variable. Utility Modules These modules are loaded using the include() command. AndroidTestUtilities New in version 3.7. Create a test that automatically loads specified data onto an Android…
cmake-language – CMake Language Reference Organization CMake input files are written in the "CMake Language" in source files named CMakeLists.txt or ending in a .cmake file name extension. CMake Language source files in a project are organized into: • Directories (CMakeLists.txt), • Scripts (<script>.cmake), and • Modules (<module>.cmake). Directories When CMake processes a project source…
cmake-generators – CMake Generators Reference Introduction A CMake Generator is responsible for writing the input files for a native build system. Exactly one of the CMake Generators must be selected for a build tree to determine what native build system is to be used. Optionally one of the Extra Generators may be selected as a…
cmake-generator-expressions – CMake Generator Expressions Introduction Generator expressions are evaluated during build system generation to produce information specific to each build configuration. Generator expressions are allowed in the context of many target properties, such as LINK_LIBRARIES, INCLUDE_DIRECTORIES, COMPILE_DEFINITIONS and others. They may also be used when using commands to populate those properties, such as target_link_libraries(),…
cmake-file-api – CMake File-Based API Introduction CMake provides a file-based API that clients may use to get semantic information about the buildsystems CMake generates. Clients may use the API by writing query files to a specific location in a build tree to request zero or more Object Kinds. When CMake generates the buildsystem in that…
cmake-env-variables – CMake Environment Variables Reference This page lists environment variables that have special meaning to CMake. For general information on environment variables, see the Environment Variables section in the cmake-language manual. Environment Variables That Change Behavior Cmake_Prefix_Path This is a CMake Environment Variable. Its initial value is taken from the calling process environment. The…
cmake-developer – CMake Developer Reference Introduction This manual is intended for reference by developers working with cmake-language(7) code, whether writing their own modules, authoring their own build systems, or working on CMake itself. See https://cmake.org/get-involved/ to get involved in development of CMake upstream. It includes links to contribution instructions, which in turn link to developer…
cmake-compile-features – CMake Compile Features Reference Introduction Project source code may depend on, or be conditional on, the availability of certain features of the compiler. There are three use-cases which arise: Compile Feature Requirements, Optional Compile Features and Conditional Compilation Options. While features are typically specified in programming language standards, CMake provides a primary user…
cmake-commands – CMake Language Command Reference Scripting Commands These commands are always available. break Break from an enclosing foreach or while loop. break() Breaks from an enclosing foreach() or while() loop. See also the continue() command. cmake_host_system_information Query host system specific information. cmake_host_system_information(RESULT <variable> QUERY <key> …) Queries system information of the host system on…
cmake-buildsystem – CMake Buildsystem Reference Introduction A CMake-based buildsystem is organized as a set of high-level logical targets. Each target corresponds to an executable or library, or is a custom target containing custom commands. Dependencies between the targets are expressed in the buildsystem to determine the build order and the rules for regeneration in response…
checksec – check executables and kernel properties Synopsis checksec [options] [file] Description checksec is a bash script used to check the properties of executables (like PIE, RELRO, PaX, Canaries, ASLR, Fortify Source) and kernel security options (like GRSecurity and SELinux). Options -o or –output or –format {cli|csv|xml|json} Output the results in different formats for ingestion…
charsets – character set standards and internationalization Description This manual page gives an overview on different character set standards and how they were used on Linux before Unicode became ubiquitous. Some of this information is still helpful for people working with legacy systems and documents. Standards discussed include such as ASCII, GB 2312, ISO 8859,…
cgroups – Linux control groups Description Control groups, usually referred to as cgroups, are a Linux kernel feature which allow processes to be organized into hierarchical groups whose usage of various types of resources can then be limited and monitored. The kernel’s cgroup interface is provided through a pseudo-filesystem called cgroupfs. Grouping is implemented in…
cgroup_namespaces – overview of Linux cgroup namespaces Description For an overview of namespaces, see namespaces(7). Cgroup namespaces virtualize the view of a process’s cgroups (see cgroups(7)) as seen via /proc/[pid]/cgroup and /proc/[pid]/mountinfo. Each cgroup namespace has its own set of cgroup root directories. These root directories are the base points for the relative locations displayed…
ccze – A robust log colorizer, plugin infrastructure Synopsis #include <ccze.h> /* Plugin support */ typedef void (*ccze_plugin_startup_t) (void); typedef void (*ccze_plugin_shutdown_t) (void); typedef int (*ccze_plugin_handle_t) (const char *str, size_t length, char **rest); CCZE_DEFINE_PLUGIN (name, type, desc); CCZE_DEFINE_PLUGINS (plugins…); /* Display */ void ccze_addstr (ccze_color_t col, const char *str); void ccze_newline (void); void ccze_space (void);…
casper – a hook for initramfs-tools to boot live systems. Synopsis BOOT=casper As kernel parameter boot prompt. Description Casper is a hook for initramfs-tools used to generate an initramfs capable to boot live systems as those created by make-live. This includes the Debian-Live isos, netboot tarballs, and usb stick images and Ubuntu live cds. At…
capabilities – overview of Linux capabilities Description For the purpose of performing permission checks, traditional UNIX implementations distinguish two categories of processes: privileged processes (whose effective user ID is 0, referred to as superuser or root), and unprivileged processes (whose effective UID is nonzero). Privileged processes bypass all kernel permission checks, while unprivileged processes are…