You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Important changes which may directly impact the packaging of this release include:
MongoDB C Driver 1.29.0 or newer is required.
External polyfill library support is removed as a breaking change to the build system, API, and ABI.
This is the most significant change in this release.
This means the default build configuration now uses bsoncxx polyfill implementations for pre-C++17 configurations rather than the Boost or mnmlstc/core libraries.
This means Boost and mnmlstc/core are no longer optional dependencies.
ENABLE_TESTS is now OFF by default.
This means test targets are no longer defined by the default build configuration.
This means the FetchContent download-and-configure of the Catch2 v3 library and corresponding C++14 or newer compiler support for building tests (both added in the 3.11.0 release) are no longer required by the default build configuration.
Building and using the installed libraries still only require C++11 or newer.
The CMake option MONGOCXX_OVERRIDE_DEFAULT_INSTALL_PREFIX is removed and now implicitly OFF.
This means CMake's default install prefix and related paths are now used by default.
Various deprecated or undocumented features are removed as a breaking change to the API and ABI.
Note: v3.11 will continue to receive bug fixes (as patch releases) for up to one year after the 4.0.0 release.
The text was updated successfully, but these errors were encountered:
Library name
mongo-cxx-driver
New version number
4.0.0
Other information that may be useful (release notes, etc...)
Release notes are here.
Important changes which may directly impact the packaging of this release include:
ENABLE_TESTS
is nowOFF
by default.MONGOCXX_OVERRIDE_DEFAULT_INSTALL_PREFIX
is removed and now implicitlyOFF
.Note: v3.11 will continue to receive bug fixes (as patch releases) for up to one year after the 4.0.0 release.
The text was updated successfully, but these errors were encountered: