[SERVER-34676] Optionally enforce C driver minimum version for embedded builds Created: 25/Apr/18 Updated: 03/Jun/18 Resolved: 01/Jun/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Build |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Andrew Morrow (Inactive) | Assignee: | Gabriel Russell (Inactive) |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Sprint: | Platforms 2018-06-04 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
When building the C driver transport layer for embedded, we simply test for the presence of the C driver. If we find it, we build the TransportLayer shim, but we don't enforce a minimum for the C driver, and we should. We should also set things up so that you can make it a build error if you don't have the C driver, so that mobile SDK builds can enforce a dependency on it, without forcing server developers to do so. |
| Comments |
| Comment by Gabriel Russell (Inactive) [ 03/May/18 ] |
|
We currently depend on patching the cdriver during build. There is not any real version that works for us. Once the new version is released, and we import it, and we can use it without patching it, then we can require that version. |