Use Case
As a macos arm64 user I want libmongocrypt to test against compiling on that system so that I can rely on prebuilt mongo-c-driver and libmongocrypt binaries in evergreen.
User Impact
Any developer working on an Apple M1 device, or deploying a client side FLE app to M1 Macs.
Dependencies
- MongoDB C Driver (just libbson) - will also need to support M1
- kms-message - will also need to support M1
Unknowns
- Are there any differences compiling on macos arm64 vs linux arm64?
Acceptance Criteria
Implementation Requirements
- n/a
Testing Requirements
- Add macos-1100-arm64 to the CI matrix
- Ensure compilation is successful
- Ensure the prep-c-driver-source task is available for other driver languages to use
Documentation Requirements
- Maybe document system support? If there is a docs page for that.
Follow Up Requirements
- n/a
- is depended on by
-
NODE-3631 Install of mongocrypt fails on M1
-
- Closed
-
- is related to
-
-
- Closed
-
- split to
-
JAVA-4445 Update Java bindings for client side encryption to support M1 processor
-
- Closed
-
-
CSHARP-4016 Update libmongocrypt C# bindings for macOS m1
-
- Closed
-
-
-
- Closed
-