Skip to content

Use the canonical SQLite CMake target - #1532

Merged
bmehta001 merged 3 commits into
microsoft:mainfrom
bmehta001:bhamehta/sqlite3-canonical-target
Sep 14, 2026
Merged

bmehta001 merged 3 commits into
microsoft:mainfrom
bmehta001:bhamehta/sqlite3-canonical-target

Conversation

@bmehta001

Copy link
Copy Markdown
Contributor

Summary

  • use SQLite3::SQLite3, the canonical target in CMake 4.3+
  • adapt the legacy SQLite::SQLite3 target for CMake 3.15-4.2 and embedding consumers
  • remove the deprecated BUILD_IOS option from the in-repo vcpkg overlay

Validation

  • Windows static vcpkg install and consumer: 10/10 passed with CMake 4.4.2
  • Windows consumer configure: passed with -Werror=author
  • Linux/WSL vendored static package build: passed with -Werror=dev
  • Linux/WSL embedding build with a preloaded legacy SQLite target: 10/10 passed with -Werror=dev

Avoid CMake 4.3+ developer warnings for static consumers while preserving compatibility with older FindSQLite3 modules and preloaded legacy targets.

Files changed:
- CMake dependency resolution and installed package helpers
- SDK, Android, and test target links
- in-repo vcpkg overlay port

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Keep the CMake target migration focused by dropping the legacy target adapter and updating the embedding fixture to provide SQLite3::SQLite3 directly.

Files changed:
- cmake/MSTelemetryConfig.cmake.in
- cmake/MatsdkDependencyTargets.cmake
- tests/embedding/CMakeLists.txt

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 037b338a-b5c0-4989-b9d3-36681fb822f5
@bmehta001 bmehta001 self-assigned this Sep 14, 2026
@bmehta001
bmehta001 enabled auto-merge (squash) September 14, 2026 21:55
@bmehta001
bmehta001 merged commit ba537f3 into microsoft:main Sep 14, 2026
43 of 47 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants