SQLiteCpp: Skill for Claude Code

SQLiteCpp CI Workflows

Common steps

• Checkout code.
• Initialize submodules: git submodule update --init --recursive.
• Configure build directory (build or builddir).
• Build and run tests with verbose output.

GitHub Actions (CMake)

• Matrix across Windows (MSVC/MinGW), Ubuntu, macOS.
• Keep the latest-MSVC Windows build in Debug mode.
• Complement it with two Visual Studio 2022 Release builds for Win32/x86: one shared and one static. Do not recreate broader Visual Studio matrices.
• Keep the dedicated minimum-MSVC job on windows-2022: install the optional VS2017 15.9 / v141 toolset, select it with -T v141, and assert MSVC 1916 in the consumer. Run unit tests, the example, and the consumer with standard filesystem and string_view checks. Do not assume a current runner includes this optional toolset or let the baseline job silently use the default compiler.
• CMake config includes:
  • -DBUILD_SHARED_LIBS=ON for standard configurations; VS2022 Win32/x86 Release covers both ON and OFF.
  • -DSQLITECPP_BUILD_TESTS=ON
  • -DSQLITECPP_BUILD_EXAMPLES=ON
  • -DSQLITECPP_RUN_CPPCHECK=OFF
  • -DSQLITECPP_RUN_CPPLINT=OFF
• Tests: ctest --verbose --output-on-failure.
• Keep explicit custom assertion handler coverage in Debug and Release. The SQLITE_ENABLE_ASSERT_HANDLER CMake option defaults to OFF, so default builds of tests and examples do not compile or link the application-provided handlers. The dedicated static-library job enables this option and builds the unit tests and both examples to check their handler definitions.

GitHub Actions (Meson)

• Use pipx install meson ninja.
• Set CC, CXX, and optional linkers.
• Setup with tests/examples and sqlite3 fallback: meson setup builddir -DSQLITECPP_BUILD_TESTS=true -DSQLITECPP_BUILD_EXAMPLES=true --force-fallback-for=sqlite3.
• Build: meson compile -C builddir.
• Test: meson test -C builddir.
• Keep column metadata coverage with -DSQLITE_ENABLE_COLUMN_METADATA=true: shared and static SQLite fallback builds, plus a system SQLite build with --wrap-mode=nofallback and the SQLite/GTest development packages installed. The fallback wrap enables metadata in SQLite itself.
• Build and run the standalone column metadata consumer through sqlitecpp_dep only. It must check that the public feature definition matches the option and call both origin-name APIs when enabled; do not add SQLITE_ENABLE_COLUMN_METADATA directly to consumer compiler flags. Default Meson jobs cover the metadata-disabled consumer.