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

Re-evaluate using nano include wrappers for boost (third-party) libraries #247

Open
gr0vity-dev opened this issue Jan 10, 2023 · 0 comments
Labels
debug Updates assisting with debugging and development efforts quality improvements This item indicates the need for or supplies changes that improve maintainability

Comments

@gr0vity-dev
Copy link
Owner

2021-10-28T18:11:17Z thsfs
Header wrappers such as have been included in many source files in order to suppress warnings. The problem is that, there are still many warnings when compiling with MSVC, as not all the headers that issue warnings were wrapped. Perhaps we don't need to follow this path, adding this extra amount of code just to get the buildings less verbose.Evaluate other paths to disable warnings from third-party code, as below:- https://stackoverflow.com/questions/56707123/how-to-suppress-clang-warnings-in-third-party-library-header-file-in-cmakelists- https://docs.microsoft.com/en-us/cpp/build/reference/external-external-headers-diagnostics?view=msvc-160

@gr0vity-dev gr0vity-dev added quality improvements This item indicates the need for or supplies changes that improve maintainability debug Updates assisting with debugging and development efforts labels Jan 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
debug Updates assisting with debugging and development efforts quality improvements This item indicates the need for or supplies changes that improve maintainability
Projects
None yet
Development

No branches or pull requests

1 participant