[SERVER-38658] Enable windows autolib and windows ABI library name tagging for embedded SDK Created: 14/Dec/18 Updated: 06/Dec/22 Resolved: 04/Nov/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Build |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Andrew Morrow (Inactive) | Assignee: | [DO NOT ASSIGN] Backlog - Server Development Platform Team (SDP) (Inactive) |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Server Development Platform
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Backport Requested: |
v4.2
|
||||
| Participants: | |||||
| Description |
|
Options that affect which runtime libraries are used to build the embedded SDKs result in different ABIs. We should adorn the DLL name with a tag that identifies the ABI (much like boost does), and then use #pragma comment(lib...) in the header so that the correct library to link to can be auto-selected and does not need to be explicitly named on the link line. |