Favour internal SQLite3 library during build

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • WT12.0.0, 8.3.0-rc0
    • Affects Version/s: None
    • Component/s: Build, PALite
    • None
    • Storage Engines, Storage Engines - Foundations
    • SE Foundations - 2025-11-07
    • None

      Currently, if the build host contains SQLite3 library, then the build prefers the system library to be used with PALite instead of the bundled SQLite3 distribution.

      Unfortunately, some build hosts contain relatively old SQLite3 versions. The old SQLite3 versions limit PALite ability to use internal sqlite3 storage efficiently. It leads to poorly performing and/or cumbersome code.

      If internal SQLite3 is used by default, then configure-combinations task is failing with numerous compilation warnings for sqlite3 source code.

      TODO:

      • Fix configure-combinations task to rely on WT cmake high-level configuration, instead of supplying compilation flags directly. This is covered by WT-15719 .
      • Switch to default internal SQLite3 bundle.
      • Build SQLite3 internal bundle inly if PALite extension is enabled.
      • Create ENABLE_PALITE cmake flag to control whether PALite is included in the build.

            Assignee:
            Alex Blekhman
            Reporter:
            Alex Blekhman
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: