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

Precompiled header fallout #42544

Merged
merged 2 commits into from
Jul 29, 2020

Conversation

jbytheway
Copy link
Contributor

Summary

SUMMARY: None

Purpose of change

To fix some CI issues resulting from the precompiled header PR.

Describe the solution

  • Add a virtual destructor to catch.hpp to avoid a warning there.
  • Improve the heuristics for identifying header guards in our custom clang-tidy check.

Describe alternatives you've considered

Suppressing the compiler warning in other ways.

Testing

Don't have the means to properly test locally right now; hoping the CI tests it sufficiently.

Additional context

When using precompiled headers, the suppression of this warning isn't
working correctly.  We could suppress it in other ways, but this seems
simpler.
There was a false-positive for header guard check in a cpp file.  Fix it
by not looking for bad guards in non-headers.
@anothersimulacrum anothersimulacrum added the Code: Build Issues regarding different builds and build environments label Jul 29, 2020
@ZhilkinSerg ZhilkinSerg merged commit 4654765 into CleverRaven:master Jul 29, 2020
@jbytheway
Copy link
Contributor Author

#42535 is probably a better fix than the adding of a virtual destructor here.

Coolthulhu referenced this pull request in cataclysmbnteam/Cataclysm-BN May 25, 2021
* Add a virtual destructor to a Catch2 struct

When using precompiled headers, the suppression of this warning isn't
working correctly.  We could suppress it in other ways, but this seems
simpler.

* Don't try to fix header guards in non-headers

There was a false-positive for header guard check in a cpp file.  Fix it
by not looking for bad guards in non-headers.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Code: Build Issues regarding different builds and build environments
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants