Closed Bug 466215 Opened 16 years ago Closed 16 years ago

CAPI is disabled on Windows Mobile

Categories

(NSS :: Build, defect)

Product:
NSS
Platform:
All
Windows Mobile 6 Standard
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX
Milestone:
3.12.3

People

(Reporter: dougt, Assigned: wtc)

Details

CAPI has been disabled in the build system. When building, we get a link error: cobject.obj : error LNK2019: unresolved external symbol RpcStringFree referenced in function ckcapi_getContai cobject.obj : error LNK2019: unresolved external symbol UuidToString referenced in function ckcapi_getContain cobject.obj : error LNK2019: unresolved external symbol UuidCreate referenced in function ckcapi_getContainer
Doug, How is this bug distinct from bug 4544120? There is a patch for this very issue, attached to Bug 454120 - Problems Compiling SECURITY module for WinMobile awaiting your review
priority. i think we can live without CAPI for a while.
We did not need CAPI on windows mobile until the run time dependencies are resolved. And once they are resolved, it is still an outstanding question if CAPI is useful on windows mobile.
Marked the bug WONTFIX. We can revisit this when the CAPI module is officially supported and used on Windows.
Assignee: nobody → wtc
Status: NEW → RESOLVED
Closed: 16 years ago
OS: Other → Windows Mobile 6 Standard
Resolution: --- → WONTFIX
Target Milestone: --- → 3.12.3
You need to log in before you can comment on or make changes to this bug.