Build SQLiteCpp with CMake. Use for CMake builds, tests, options, or build scripts.
84%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
mkdir buildcd buildcmake -G "Visual Studio 18 2026" -DSQLITECPP_BUILD_TESTS=ON -DSQLITECPP_BUILD_EXAMPLES=ON ..cmake --build . --config Releasemkdir build && cd buildcmake -DCMAKE_BUILD_TYPE=Debug -DSQLITECPP_BUILD_TESTS=ON -DSQLITECPP_BUILD_EXAMPLES=ON ..cmake --build .build.bat (Windows) enables shared libs, tests, examples, and runs ctest.build.sh (Unix) enables ASAN, shared libs, tests, examples, and runs ctest.SQLITECPP_BUILD_TESTS (OFF): build unit tests.SQLITECPP_BUILD_EXAMPLES (OFF): build examples.BUILD_SHARED_LIBS (OFF): build shared libs (DLLs).SQLITECPP_INTERNAL_SQLITE (ON): use bundled sqlite3 source.SQLITE_ENABLE_COLUMN_METADATA (ON): enable getColumnOriginName().SQLITECPP_RUN_CPPLINT (ON): run cpplint target.SQLITECPP_RUN_CPPCHECK (ON): run cppcheck target.SQLITECPP_RUN_DOXYGEN (OFF): generate docs.SQLITECPP_USE_ASAN (OFF): address sanitizer.SQLITECPP_USE_UBSAN (OFF): undefined behavior sanitizer for the library and linked consumers.SQLITECPP_USE_GCOV (OFF): GCov coverage.SQLITECPP_DISABLE_STD_FILESYSTEM (OFF): disable std::filesystem support.SQLITECPP_DISABLE_EXPANDED_SQL (OFF): disable sqlite3_expanded_sql support.ctest --output-on-failurectest --output-on-failure -Vctest --output-on-failure -R "Database"GTest; otherwise they fall back to the googletest submodule.git submodule update --init --recursive.find_package(SQLite3 3.38.0 REQUIRED) checks discovered system SQLite versions.
Custom SQLite targets are also covered by the source-level compile-time version check.cxx_std_17 requests a standard mode; it does not prove complete C++17 feature support.
Old MSVC toolsets are a special case: CMake can advertise standard meta-features even when the
compiler has no standard-selection flag, and can map C++17 to /std:c++latest on VS2015 Update 3.
CXX_STANDARD_REQUIRED therefore does not guarantee an early rejection of unsupported MSVC versions.
Preserve explicit minimum-version diagnostics when needed, using message(FATAL_ERROR ...).
See https://cmake.org/cmake/help/latest/prop_tgt/CXX_STANDARD_REQUIRED.html and
https://cmake.org/cmake/help/latest/manual/cmake-compile-features.7.html#requiring-language-standards....4.4 policy maximum in cmake_minimum_required does not cap the supported CMake version;
it opts into policy behavior through CMake 4.4 while still allowing newer CMake releases.SRombauts/SQLiteCpp
7302cd3
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.