sqlite-with-gcov

Compile C/C++ software with gcov instrumentation and custom prefixes.

Updated Feb 24, 2026

Search Tags:#code coverage #build #sqlite #instrumentation #c++#compilation #gcov

Ready to run

npx skills add https://github.com/Zurybr/lefarma-skills --skill sqlite-with-gcov-zurybr

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sqlite-with-gcov
Source: https://github.com/Zurybr/lefarma-skills/tree/main/letta/benchmarks/trajectory-only/sqlite-with-gcov
Command: npx skills add https://github.com/Zurybr/lefarma-skills --skill sqlite-with-gcov-zurybr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the complexity of compiling C/C++ projects, specifically SQLite, with gcov code coverage instrumentation, installing them to custom locations, and making the resulting binaries accessible system-wide.

Core Features & Use Cases

Code Coverage Compilation: Integrates gcov flags (-fprofile-arcs, -ftest-coverage) into the build process for detailed code coverage analysis.
Custom Installation Prefixes: Allows installation to non-standard directories (--prefix).
System-wide Binary Availability: Provides strategies (symlinks, profile scripts) to ensure compiled binaries are accessible in the system's PATH.
Use Case: When developing or auditing C/C++ libraries and you need to ensure a high level of test coverage and understand the runtime behavior of the instrumented code.

Quick Start

Compile SQLite with gcov instrumentation and install it to /opt/sqlite-coverage, making the binary available in the system's PATH.

Frequently Asked Questions about sqlite-with-gcov

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I compile SQLite with gcov code coverage instrumentation?▼

To compile SQLite with gcov code coverage, you need to configure the build using specific CFLAGS like `-fprofile-arcs` and `-ftest-coverage`, along with the appropriate LDFLAGS. This process integrates instrumentation directly into the compiled binaries for runtime analysis.

What is the process for installing C++ builds to a custom prefix?▼

Installing C++ builds to a custom prefix involves using the `--prefix` configuration option to target a non-standard directory. After installation, you must ensure binary accessibility by creating symlinks or updating your profile scripts to include the custom path.

How does gcov instrumentation work for C/C++ software?▼

gcov instrumentation works by compiling C/C++ software with specific flags that insert profiling code into the binary. When the instrumented program runs, it generates detailed coverage data files, allowing you to analyze which lines of code were executed during testing.

Why are my compiled binaries not found in the system PATH after a custom installation?▼

Binaries are not found in the system PATH after a custom installation because they are placed in a non-standard directory. You must manually add this directory to your PATH environment variable using profile scripts or create symbolic links to a standard binary location.

Can I use custom CFLAGS and LDFLAGS to generate coverage data for auditing?▼

Yes, you can use custom CFLAGS and LDFLAGS to generate coverage data for auditing. By configuring your C/C++ build with gcov flags, the resulting instrumented binaries will produce the necessary coverage files upon execution to verify test coverage and runtime behavior.