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

[messagingframework] Sync upstream and fix compiler warnings on patches. JB#46713 #10

Merged
merged 1 commit into from Nov 9, 2023

Conversation

pvuorela
Copy link
Contributor

@pvuorela pvuorela commented Nov 8, 2023

Upstream got one patch in.

Rest of the patches adjusted to avoid compiler warnings mostly by sprinkling QLatin1String() here and there.

@dcaliste - hope this doesn't conflict with any adjustments you've been doing too much. Got myself tired of seeing the warnings flood when trying different changes upstream.

…es. JB#46713

Upstream got one patch in.

Rest of the patches adjusted to avoid compiler warnings mostly by
sprinkling QLatin1String() here and there.
@dcaliste
Copy link
Contributor

dcaliste commented Nov 8, 2023

Patches apply well and the code compiles almost without any warning anymore. Nice.

Actually there is one place in src/libraries/qmfmessageserver/qmailmessageserverplugin.cpp where we still have a warning, but this is upstream code. It is not catched by the Qt CI since this part is only compiled when the flag MESSAGESERVER_PLUGINS is defined.

No problem to get this in with regards to my current changes and work. So good for me to go in.

@pvuorela
Copy link
Contributor Author

pvuorela commented Nov 9, 2023

Yep, indeed that warning from upstream, thus not touched here. Also one unused variable warning on upstream unit test.

I think the warnings introduced by the patches here should be handled now.

@pvuorela pvuorela merged commit 1ab2c42 into master Nov 9, 2023
@mlehtima mlehtima deleted the fix_warnings branch April 22, 2024 14:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants