Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use swig4.2 or later #3985

Open
wants to merge 5 commits into
base: main
Choose a base branch
from
Open

Use swig4.2 or later #3985

wants to merge 5 commits into from

Conversation

aymanhab
Copy link
Member

@aymanhab aymanhab commented Jan 7, 2025

Fixes issue #0

Brief summary of changes

Changed CMakeLists to not require exact version match and SWIG out references to functions that are not useful to scripting

Testing I've completed

Looking for feedback on...

Is there a chance the function in MocoUtilities is actually used? Should we remove it altogether from bindings?

CHANGELOG.md (choose one)

  • no need to update because internal

This change is Reviewable

@aymanhab aymanhab requested a review from nickbianco January 7, 2025 17:34
@nickbianco
Copy link
Member

Is there a chance the function in MocoUtilities is actually used? Should we remove it altogether from bindings?

createPeriodicTrajectory() is quite frequently used by Moco users. Could we add a custom SWIG binding for std::vector<std::pair<std::string, std::string>> (e.g., StdVectorStringPair)?

@aymanhab
Copy link
Member Author

aymanhab commented Jan 7, 2025 via email

undo formatting changes for non-swig side for cleaner diff
@aymanhab
Copy link
Member Author

aymanhab commented Jan 8, 2025

@nickbianco ready for review, I separated the prototypes so the code looks cleaner, there's no loss of functionality as the vector was never possible to construct in scripting. I can open a separate issue for that if you think we should keep it on our radar. Thank you

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants