Created attachment 194177 [details]
Flavorized the port + fixed Makefile.in to make the wx-config name full like it is in the 3.0 port instead of just 'wx-config'.
Unfortunately, still can't parallel-install the two flavors because of the headers...
Some app testing: poedit works fine, treesheets works fine, hugin works only on X11 (does raw GdkX11Display stuff, invalid cast on GdkWaylandDisplay), kicad kinda works (with python disabled; some tools look broken), veracrypt works with skippable assertion failure dialogs
Created attachment 194179 [details]
+ here's a patch for bsd.wx.mk
Why do you want to support gtk2? It is the older version, superseded by gtk3.
My concern is associated maintenance cost without much sensible benefit.
(In reply to Yuri Victorovich from comment #2)
Not all applications work well with gtk3...
Compare "Required By" in
I guess the dev version (3.1) can be gtk3 only, but stable would need both for sure.
(In reply to Greg V from comment #3)
These "Required By" are possibly just due to the choice of the gtk2 version in Arch AUR ports. How many of them really require gtk2 and can't work with gtk3?
(In reply to Yuri Victorovich from comment #4)
kicad is definitely broken in many places...
Ok, I will study this issue how needed gtk2 support really is.
Please note that if some ports aren't gtk3 compatible they can also stay on wx28 or wx30 for the time being.
Mk certainly needs 3.1 added.
Thank you, Greg, for the patch.
I will see what to do next.
And, like you said, there is no easy way to install @gtk2 and @gtk3 flavors at the same time, so this would certainly cause conflicts.
A commit references this bug:
Date: Tue Jun 12 07:17:11 UTC 2018
New revision: 472232
x11-toolkits/wxgtk31: Change to gtk3 because it is the latest gtk version
Also remove the stray file wxmsw.mo that caused conflict with wxgtk30.
This patch is a portion of the patch from the bug#228904.
Submitted by: Greg V <firstname.lastname@example.org>
Any reason to keep this open?