cmake
Skill1 starsChanged 9 months agoMITView on GitHub
Package a CMake-based project for corepkgs. Use when a source tree has a CMakeLists.txt — covers the minimal derivation, cmakeFlags, cross-compilation, and diagnosing CMake configure failures.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- LuisaGroup/LuisaComputetheir own version, first seen Oct 8, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- LuisaGroup/LuisaCompute★ 1.1ksame name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository14 other files it gives its agents.
- AGENTS.mdAGENTS.md
- ekala-cmake-nixSkill
- ekapkgs-repoSkill
- goSkill
- mesonSkill
- mk-many-variantsSkill
- nix-buildSkill
- nix-evalSkill
- packagingSkill
- portingSkill
- pythonSkill
- rustSkill
- structured-attrsSkill
- validationSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 64
Use cmakeEntries to specify CMake -D cache entries as a structured attrset.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
CMake Build System
Minimal Example
{
lib,
stdenv,
fetchFromGitHub,
cmake,
}:
stdenv.mkDerivation (finalAttrs: {
pname = "example";
version = "1.0.0";
src = fetchFromGitHub {
owner = "example";
repo = "example";
tag = "v${finalAttrs.version}";
hash = "sha256-AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA=";
};
nativeBuildInputs = [
cmake
cmake.configurePhaseHook # Required
];
meta = {
description = "Example CMake package";
license = lib.licenses.mit;
};
})Essential Requirements
Always include cmake.configurePhaseHook in nativeBuildInputs.
Common Patterns
With Dependencies
nativeBuildInputs = [
cmake
cmake.configurePhaseHook
pkg-config
];
buildInputs = [
zlib
openssl
];CMake Entries (Preferred)
Use cmakeEntries to specify CMake -D cache entries as a structured attrset.
Booleans are automatically converted to ON/OFF.
cmakeEntries = {
BUILD_SHARED_LIBS = true;
ENABLE_TESTS = false;
CMAKE_INSTALL_LIBDIR = "lib";
};CMake Flags (Legacy)
cmakeFlags still works for string-based flags and non--D flags:
cmakeFlags = [
"-DBUILD_SHARED_LIBS=ON"
"-DENABLE_TESTS=OFF"
"-DCMAKE_INSTALL_LIBDIR=lib"
];Both can be used together. cmakeFlags values override cmakeEntries for the
same key (cmake uses last-wins for -D flags). Use cmakeFlags for non--D
flags like -Wno-dev or -GNinja.
Cross-Compilation
strictDeps = true;
nativeBuildInputs = [ cmake cmake.configurePhaseHook pkg-config ];
buildInputs = [ zlib ];
depsBuildBuild = [ pkg-config ];Troubleshooting
CMake can't find dependencies:
cmakeEntries = {
ZLIB_ROOT = "${zlib}";
OPENSSL_ROOT_DIR = "${openssl}";
};Library install to lib64:
cmakeEntries = {
CMAKE_INSTALL_LIBDIR = "lib";
};Install prefix issues:
cmakeEntries = {
CMAKE_INSTALL_PREFIX = "${placeholder "out"}";
};Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

