Include the metadata headers in the generated SWIG bindings #2069
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In the generated SWIG bindings, include access to the metadata functions from other scripting languages (such as Python). This allows access to functions that indicate what object type an OID represents (
sai_metadata_get_object_type_name
) as well as metadata of an attribute (sai_metadata_get_attr_metadata
).As part of this, some workarounds are needed to either ignore certain types/functions or to not try to generate constructors. This is because of const qualifier issues: