Changes between Initial Version and Version 1 of Ticket #2781
- Timestamp:
- 05/29/18 10:11:07 (7 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #2781
- Property Summary Find a way to not leak ACE headers/definitions in MapGuide common headers → Find a way to not leak ACE/xerces headers/definitions in MapGuide common headers
-
Ticket #2781 – Description
initial v1 1 The SWIG bindings do not call anything in ace , but due to ACE headers/types leaking out of Foundation/MapGuideCommon, this gives us grief when building the PHP api due to its headers conflicting with ACE on certain platform definitions (eg. `uid_t`, `gid_t`, `struct dirent`)1 The SWIG bindings do not call anything in ace or xerces, but due to their headers/types leaking out of Foundation/MapGuideCommon, this gives us grief when building the PHP api due to its headers conflicting with ACE on certain platform definitions (eg. `uid_t`, `gid_t`, `struct dirent`). Also the leaking of xerces headers is completely unnecessary 2 2 3 3 Our current workaround has been to overlay patched PHP headers to resolve such conflicts, but this is not a tenable solution. We should either properly encapsulate or `#ifdef` any traces of ACE out of these headers when building SWIG bindings.