-
Notifications
You must be signed in to change notification settings - Fork 331
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
Some compilation warnings to check before release #6563
Comments
@Thanatomanic I've pushed a new branch to fix some low hanging fruits. Though I don't get no deprecation warnings here. As to
Feel free to add your fixes to the branch, everyone. Best, |
@Thanatomanic @Floessie Pierre |
The lensfun deprecation warnings can be ignored for now. They are deprecated since the current stable version (0.3.3). Some replacements have only been added in 0.3.2 and the rest in 0.3.3. I suppose we could fix some warnings and bump the minimum required version to 0.3.2, which is almost 7 years old. |
I pushed some warning fixes to @Floessie's branch.
Removing the deprecated GDK functions could break some things that are not trivial to fix. Let's leave them for 5.9. |
@Lawrence37 Thanks for picking this up! Two points:
Best, |
@Floessie I've added |
I pushed one more change which replaces the deprecated function The remaining deprecated functions can stay for now.
|
@Pandagrapher as it's been a few years since I dealt with the joy called HiDPI, and since I now actually have a HiDPI monitor, could you link me to some documentation on what "real" HiDPI support means and how to go about implementing it? Also, which version of Gtk+ will be required for that? Sorry for the off-topic - if there is an issue dedicated to that, feel free to reply there and tag me. |
I did a build of
|
At this point I think its best to leave this for 6.0. |
Hello to everyone here, is anyone currently working on removing gdk_threads_enter() (one warning message above). I don't have a lot of experience in GDK/GTK and its thread handling. But if no one is working on that, I will give it a try. Thank you in advance. Greetings |
There are a few new warnings, but not from new code. See #6621 (comment). |
I fixed the remaining warnings, minus the ones we agree to ignore, in #7257. It builds and runs fine in Windows and Linux. |
I did an extended warning build of
dev
on Windows and gcc 12.1 with-Wall -Wextra -Wdouble-promotion -Wno-unused-parameter -Wno-double-promotion
to check for things that might be improved in the codebase before we ship 5.9. Could somebody (@Floessie ?) take a look at whether something can or should be done?I ignored warnings from
dcraw.cc
and decoders (CR3, Panasonic).rtengine/imagedata.cc
there are instances ofuint16
that are deprecated. Probably needs<cstdint>
'ifying.rtengine/imageio.cc
there are instances ofuint16
(and more) anduint32
that are deprecated. Probably needs<cstdint>
'ifying.rtengine/imageio.cc
something may be clobbered on line 1002:rtengine/rtlensfun.cc
this happens:rtengine/rtthumbnail.cc
there is a whole slew of[-Warray-bounds]
warnings, similar to this onertgui/adjuster.cc
it reports:rtgui/main.cc
there are calls to some deprecated GDK functionsrtgui/myflatcurve.cc
there are potentially uninitialized variablesprevCursorX
andprevCursorY
(line 1646)rtgui/options.cc
there are these[-Wmissing-field-initializers]
warnings:rtgui/rtimage.cc
things could be made more explicit:rtgui/rtscalable.cc
it is suggested to use a replacement for a deprecated function callrtgui/rtwindow.cc
it is suggested to use a replacement for a deprecated function callrtgui/thumbbrowserbase.cc
it is suggested to use a replacement for a deprecated function callrtgui/main-cli.cc
there may be some unwanted implicit fallthroughThe text was updated successfully, but these errors were encountered: