RESOLVED WONTFIX 212126
[GTK4] Build error with gtk4 on PluginProcessMainUnix.cpp
https://bugs.webkit.org/show_bug.cgi?id=212126
Summary [GTK4] Build error with gtk4 on PluginProcessMainUnix.cpp
Santosh Mahto
Reported 2020-05-19 22:05:41 PDT
In gtk4, gtk_init doesn't take any command line arguments, but PluginProcessMainUnix.cpp still uses the gtk3 based gtk_init call. which result in error while building with gtk4
Attachments
Patch (1.22 KB, patch)
2020-05-19 22:19 PDT, Santosh Mahto
no flags
Patch (1.19 KB, patch)
2020-05-19 22:27 PDT, Santosh Mahto
no flags
Patch (1.11 KB, patch)
2020-05-20 02:51 PDT, Santosh Mahto
mcatanzaro: review-
Santosh Mahto
Comment 1 2020-05-19 22:19:09 PDT
Santosh Mahto
Comment 2 2020-05-19 22:23:05 PDT
It would be nice if
Santosh Mahto
Comment 3 2020-05-19 22:23:45 PDT
It would be nice if someone can review this simple build error fix for gtk4
Santosh Mahto
Comment 4 2020-05-19 22:27:25 PDT
Adrian Perez
Comment 5 2020-05-20 00:30:21 PDT
Comment on attachment 399810 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=399810&action=review > Source/WebKit/ChangeLog:8 > + * PluginProcess/unix/PluginProcessMainUnix.cpp: NPAPI plug-in support is disabled for GTK4 builds. We are not planning to support them, given that all major browsers are phasing out the support (or have already). > Source/WebKit/PluginProcess/unix/PluginProcessMainUnix.cpp:64 > gtk_init(nullptr, nullptr); …anyway, instead of doing this, you should leave the call to gtk_init() unchanged and instead the <WebCore/GtkVersioning.h>, which has utility functions that avoid the need for preprocessor guards.
Santosh Mahto
Comment 6 2020-05-20 02:49:58 PDT
(In reply to Adrian Perez from comment #5) > Comment on attachment 399810 [details] > Patch > > View in context: > https://bugs.webkit.org/attachment.cgi?id=399810&action=review > > > Source/WebKit/ChangeLog:8 > > + * PluginProcess/unix/PluginProcessMainUnix.cpp: > > NPAPI plug-in support is disabled for GTK4 builds. We are not planning > to support them, given that all major browsers are phasing out the support > (or have already). > > > Source/WebKit/PluginProcess/unix/PluginProcessMainUnix.cpp:64 > > gtk_init(nullptr, nullptr); > > …anyway, instead of doing this, you should leave the call to gtk_init() > unchanged and instead the <WebCore/GtkVersioning.h>, which has utility > functions that avoid the need for preprocessor guards. Thanks for review, I will update the patch with WebCore/GtkVersioning.h inclusion, If you feel it should be part of main tree(at least until PluginProcessMainUnix.cpp code is removed), you can further review/merge it.
Santosh Mahto
Comment 7 2020-05-20 02:51:09 PDT
Michael Catanzaro
Comment 8 2020-05-20 08:03:07 PDT
$0.02: I think it's time to delete WebKitPluginProcess entirely, nobody should be using this anymore.
Santosh Mahto
Comment 9 2020-05-21 03:35:12 PDT
(In reply to Michael Catanzaro from comment #8) > $0.02: I think it's time to delete WebKitPluginProcess entirely, nobody > should be using this anymore. Should I open new bug to remove WebKitPluginProcess and mark it as "wontFix"? I guess this is to remove complete plugin support from webkit.
Michael Catanzaro
Comment 10 2020-05-21 05:36:52 PDT
Well we need to see if GTK port maintainers agree with me before opening a bug to remove the plugin process entirely. But this one should be WONTFIX because it's definitely not going to be available in GTK4, yes.
Note You need to log in before you can comment on or make changes to this bug.