-
Notifications
You must be signed in to change notification settings - Fork 0
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
Bindings using RoadNetwork unique_ptr are not working. #846
Comments
Some ideas:
|
I like the idea and I think that for how things are right now it's the tidier option. I have a workaround in this branch for this. Wdyt? |
I concur. Note my comment in a15cc30#r77070044 which I guess it should help to reduce the code maintenance in delphyne for this workaround. The second part of the comment might not be as useful because of use cases though. |
This issue hasn't been fixed, there was a case I missed and I think I'd mistakenly tried the solution out. CI still failing, not because of using
Here I am tempted to say that going with the option
Seems the way to go at this point. CC: @agalbachicar |
Summary
maliput_py
stopped relying on custom pybind11 version. This seems to be causing a failure indelphyne
bindings that are usingstd::unique_ptr<RoadNetwork>
delphyne/python/delphyne/roads.cc
Lines 86 to 90 in 141bc61
Here
delphyne::roads::CreateMalidriveRoadNetworkFromXodr
returns astd::unique_ptr<RoadNetwork>
. When using this binding this it is throwing an error because:When
maliput_py
's bindings are compiled using the custompybind11
version it works correctly.Related
maliput/maliput_infrastructure#225
The text was updated successfully, but these errors were encountered: