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

Eliminate warnings about #warning #122

Merged
merged 1 commit into from
Oct 9, 2023
Merged

Eliminate warnings about #warning #122

merged 1 commit into from
Oct 9, 2023

Conversation

jbowler
Copy link
Contributor

@jbowler jbowler commented Oct 5, 2023

The warnings are already only emitted with GCC so changing them to the GCC diagnostic pragma is safe.

The warnings are already only emitted with GCC so changing them to the
GCC diagnostic pragma is safe.

Signed-off-by: John Bowler <jbowler@acm.org>
@mrbean-bremen mrbean-bremen merged commit db04231 into MeVisLab:qt6 Oct 9, 2023
11 checks passed
@jbowler jbowler deleted the pull-request-122 branch October 9, 2023 12:45
mrbean-bremen pushed a commit to mrbean-bremen/pythonqt that referenced this pull request Oct 29, 2023
The warnings are already only emitted with GCC so changing them to the
GCC diagnostic pragma is safe.
mrbean-bremen pushed a commit that referenced this pull request Oct 29, 2023
The warnings are already only emitted with GCC so changing them to the
GCC diagnostic pragma is safe.
mrbean-bremen pushed a commit that referenced this pull request Nov 1, 2023
The warnings are already only emitted with GCC so changing them to the
GCC diagnostic pragma is safe.
mrbean-bremen pushed a commit that referenced this pull request Nov 2, 2023
The warnings are already only emitted with GCC so changing them to the
GCC diagnostic pragma is safe.
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

Successfully merging this pull request may close these issues.

2 participants