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

Problem in downstream library if built with a gcc major version different from the one used to build manifpy #19

Open
traversaro opened this issue Feb 28, 2022 · 2 comments

Comments

@traversaro
Copy link
Contributor

In ami-iit/bipedal-locomotion-framework#514 a downstream library (blf) had runtime failures due to being compiled by a gcc major version different. We should handle this somehow, even if at the C++ level as far as I know gcc 9 and 10 should produce ABI compatible code.

@traversaro
Copy link
Contributor Author

Related issue: ami-iit/bipedal-locomotion-framework#386 .

@traversaro
Copy link
Contributor Author

Yesterday night I checked a bit pybind11 code, and it seems the issue here is not related to ABI layout of pybind11 objects, but rather the stability of the type information used in pybind11 (see https:/pybind/pybind11/blob/522c59ceb27e83750c121d5da3d8b67ac446b754/include/pybind11/pybind11.h#L1026 and the related code). At the beginning I tought it was related to the info returned by std::typeid operator, but actually I could not find any use of such operator in pybind11.

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

No branches or pull requests

1 participant