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

ABI of the library depends on the value of NDEBUG? #1795

Closed
2 tasks done
traversaro opened this issue Mar 23, 2024 · 2 comments
Closed
2 tasks done

ABI of the library depends on the value of NDEBUG? #1795

traversaro opened this issue Mar 23, 2024 · 2 comments
Labels
type: bug Indicates an unexpected problem or unintended behavior

Comments

@traversaro
Copy link
Contributor

It seems that currently the ABI of the library depends on the value of NDEBUG used when using the headers of the library, see:

However, this value could be different in the downstream project using dart w.r.t. to the value used when compiling dart, for example see conda-forge/gz-physics-feedstock#26 (comment) .

Probably it could make sense to save in

#cmakedefine01 BUILD_TYPE_DEBUG
the NDEBUG value used when compiling dart (or something similar) and use that in the .hpp ?

Bug Report

Please answer the following questions for yourself before reporting a bug.

  • I checked the documentation and the forum but found no answer.
  • I checked to make sure that this issue has not already been filed.

Environment

Select the following information.

  • DART version: 6.13.2
  • OS name and version name(or number): Not relevant
  • Compiler name and version number: Not relevant

Expected Behavior

Please describe the behavior you are expecting.

Current Behavior

What is the current behavior?

See description.

Steps to Reproduce

Not relevant?

Code to Reproduce

Please remember that with a working code it's easier to reproduce the bug and it's much faster to fix it.
It would be great to fork this repo and create a regression test using this template.

Not relevant?

@traversaro traversaro added the type: bug Indicates an unexpected problem or unintended behavior label Mar 23, 2024
@jslee02
Copy link
Member

jslee02 commented Mar 24, 2024

Good suggestion! Created #1796

@jslee02
Copy link
Member

jslee02 commented Mar 30, 2024

I believe #1796 has resolved this issue. If there are more things that need to be resolved, please reopen it or create a new one. Thank you!

@jslee02 jslee02 closed this as completed Mar 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: bug Indicates an unexpected problem or unintended behavior
Projects
None yet
Development

No branches or pull requests

2 participants