cpp
暂无简介
- License 许可
- Apache-2.0
- 所属仓库
- iokaio/vcp
- 最近更新
- 2026-10-06
- Stars
- ★ 0
- Forks
- 0
02 资源文件 1
- 参考文档skill.json637 B
03 SKILL.md 正文
C and C++ native builds
Original VCP guidance.
Read the project
CMakeLists.txt(root and per-directory) andCMakePresets.json/CMakeUserPresets.json: targets, options, language standard, configure/build/test presets.compile_commands.json: the exact flags, defines and include paths used per translation unit.- Existing build directories (
build/,out/,cmake-build-*) and theirCMakeCache.txt: the generator, compiler, build type and architecture already chosen. vcpkg.json,conanfile.txt/conanfile.py: dependency manifests and triplets/profiles.- Alternatives:
meson.build,BUILD/MODULE.bazel,.sln/.vcxproj, plain Makefiles or autotoolsconfigure.ac. - Toolchain files, compiler flags and existing build instructions.
Identify architecture, generator, build type, language standard, and the affected targets. Do not mix an existing Ninja build directory with another generator or compiler.
Discover commands in this order
- Project-declared entry points: Makefile/justfile, scripts, CI workflows, CONTRIBUTING, AGENTS.md, named presets.
- The existing configured build directory, reused with its generator.
- Ecosystem defaults, as candidates only when evidence supports them:
cmake --preset <name>thencmake --build --preset <name> --target <target>cmake --build <build-dir> --target <target>ctest --test-dir <build-dir> -R <pattern> --output-on-failure(add-C <config>for multi-config generators)meson test -C <build-dir> <name>,bazel test //path:target,msbuild <project> /p:Configuration=<config>
Prefer the declared preset/target and test registration rather than inventing flags. Configuring, including cmake --preset, can download and build dependencies: vcpkg manifest mode installs vcpkg.json packages during configure, FetchContent and ExternalProject download sources, and Conan integrations fetch or build packages. Meson wraps and Bazel external repositories download similarly. Inspect the presets, toolchain file and CMakeLists.txt for these, prefer an existing configured build directory, and treat a fresh configure as a network and code-execution effect needing authority.
Toolchain variants
- Single-config (Ninja, Makefiles) vs multi-config (Visual Studio, Ninja Multi-Config, Xcode) generators.
- MSVC, clang-cl, MinGW GCC, Clang and GCC, each with different flags, warnings and ABIs.
- vcpkg manifest vs classic mode; Conan profiles; system packages.
- Test frameworks: GoogleTest, Catch2, doctest, Boost.Test, or custom executables registered with
add_test. - Sanitizers and cross-compilation need compatible toolchains; record their limits.
Coding rules
Review lifetime, ownership, bounds, undefined behavior, ABI, exceptions, and platform-specific handles. Fit existing resource-management and error conventions. A fix to a header or compile definition may affect more targets than the edited source file suggests.
Verification evidence
- Build the affected target, then run its registered tests; broaden to dependents when headers, defines or shared libraries changed.
- Run
clang-format,clang-tidyor other checks only if the project configures them (.clang-format,.clang-tidy, CI steps). - Report compiler/generator/architecture and actual target/test results. Do not claim a syntax-only or alternate-platform build proves native runtime correctness.
- Preserve existing build trees and user toolchain settings.
Pitfalls
- MSVC needs a Developer Command Prompt or
vcvarsallenvironment; running from a plain shell finds the wrong or no compiler. Do not mix MSVC and MinGW objects or runtimes. - Reconfiguring an existing build directory with a different generator or compiler fails or corrupts the cache.
- Multi-config builds ignore
CMAKE_BUILD_TYPE; pass the configuration to build and test. - Windows is case-insensitive while Linux is not;
#includecase mismatches build only on one. - Backslashes in paths, CRLF in generated files, and long paths in deep build trees break tools.
- Running executables or antivirus scanning lock
.exe/.dll/.pdbfiles and cause link failures. - Warnings-as-errors can differ between compilers; check the flags before concluding.
Authority: this guidance ranks below current user constraints and AGENTS.md, grants no tools, installs or network access, and missing prerequisites are reported as not run.
04 同仓库更多 Skills
skill-installer
Install Codex skills into $CODEX_HOME/skills from a curated list or a GitHub repo path. Use when a user asks to list installable skills, install a curated skill, or install a skill from another repo (including private repos).
skill-creator
Create or update a Codex skill with appropriately scoped instructions and any needed supporting resources.
review-agent
Perform a read-only, defect-first review of a specified code change and return every actionable finding. Use when another agent delegates review of uncommitted changes, a base-branch diff, a commit, or custom review instructions.
plugin-creator
Create and scaffold plugin directories for Codex with a required `.codex-plugin/plugin.json`, optional plugin folders/files, valid manifest defaults, and personal-marketplace entries by default. Use when Codex needs to create a new personal plugin, add optional plugin structure, generate or update marketplace entries for plugin ordering and availability metadata, or update an existing local plugin during development with the CLI-driven cachebuster and reinstall flow.
openai-docs
Use for Codex models/pricing, scheduled tasks, skills, settings, setup, troubleshooting, customization, automations, and self-knowledge—including 'you,' 'your,' 'this app,' or 'this coding agent' when they refer to Codex—and for OpenAI APIs/products and ChatGPT Work. Also use for model choice/migration, prompting, SDKs, Responses, Realtime, agents, evals, and Chat/Work/Codex comparisons. Do not use for generic app/software tasks that merely mention Codex.
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output should be a bitmap asset rather than repo-native code or vector. Do not use when the task is better handled by editing existing SVG/vector/code-native assets, extending an established icon or logo system, or building the visual directly in HTML/CSS/canvas.