You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are currently exporting symbols that are not declared in public headers. These symbols are listed in map/def files and seem to be exported primarily for use in tests when UMF is compiled as a shared library.
Identified Issue:
A specific instance of this problem was addressed in issue #564, but it is likely that there are additional symbols improperly exported.
Tasks Before Major Release:
Review Exported Functions:
Conduct a comprehensive audit of all symbols currently exported in the project.
Verify whether each exported symbol should be publicly available or if they were exported inadvertently.
The text was updated successfully, but these errors were encountered:
lplewa
changed the title
Inconsistent Exporting of Symbols Across Platforms
Do not export private symbols(symbols not declared in public headers)
Jun 26, 2024
Current State:
We are currently exporting symbols that are not declared in public headers. These symbols are listed in map/def files and seem to be exported primarily for use in tests when UMF is compiled as a shared library.
Identified Issue:
A specific instance of this problem was addressed in issue #564, but it is likely that there are additional symbols improperly exported.
Tasks Before Major Release:
Conduct a comprehensive audit of all symbols currently exported in the project.
Verify whether each exported symbol should be publicly available or if they were exported inadvertently.
The text was updated successfully, but these errors were encountered: