[CXX-45] Align SASL/Kerberos library selection with enterprise build.py logic Created: 10/Feb/14 Updated: 26/Mar/14 Resolved: 04/Mar/14 |
|
| Status: | Closed |
| Project: | C++ Driver |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | legacy-0.0-26compat-2.6.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Andrew Morrow (Inactive) | Assignee: | Mira Carey |
| Resolution: | Done | Votes: | 0 |
| Labels: | legacy-cxx | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Description |
|
The enterprise build pulls in other libraries when using the sasl_sspi.cpp file, we should see if similar things are needed in the build of the C++ driver. |
| Comments |
| Comment by Mira Carey [ 04/Mar/14 ] |
|
Talked it over with Eric, apparently the gssapi_krb5 dependency (which is pulled in on linux, compared to pulling in secur32 on windows) is only needed for some symbols that we used to grab out of gsasl before the port to cyrus. Since the client links without it on linux, we don't have unresolved symbols and shouldn't have to bring it in. That was pretty much the difference between linux and windows: windows: sasl2 + secur32 and we only need: (for the client) windows: sasl2 + secur32 |