Disable non-actionable, noisy warnings.

[hzeller]

• deprecated: some QString conversions are deprecated, but since they're not addressed now, these warnings might hide other issues.
• unused local typedefs: happens in lemon, but not actionable for us.

[gemini-code-assist]

Code Review

This pull request aims to reduce build noise by disabling two types of compiler warnings and fixing the path matching for suppressing warnings in external dependencies. While the goal is valid, disabling warnings globally can hide issues. My review suggests more targeted approaches for both disabled warnings, either by using pragmas in code for deprecation warnings, or by ensuring third-party dependency warnings are suppressed at the dependency level rather than globally. This will improve long-term maintainability.

[github-actions]

clang-tidy review says "All clean, LGTM! 👍"

[maliberty]

Isn't Qt considered an external dependency? Why do we get warnings from it at all?

[hzeller]

It is OpenROAD code that uses deprecated functionality.

[hzeller]

ready to merge ?

[maliberty]

I would like to avoid turning off warnings globally. Lemon is only used in a few places so can we just wrap those includes in a suppression?

[hzeller]

The lemon warnings are only a few and I could even live with them, but the hundreds and hundreds of deprecation warnings in the gui (OpenRoad uses QString constants, but they have been deprecated in qt 6 apparently) are annoying and potentially hiding other things.

Should I wrap the Qt warnings in #pragmas that disable that warning ?

[maliberty]

Fight it another day