gtk3.22-client built by default, though gtk3-client is assumed default in S2_6
Seems to be caused by backporting of gtk3.22-client gone bad.
Attached fix makes gtk3-client the default like documented. I wouldn't be opposed to a solution that we officially make gtk3.22-client the default - that would probably be what users of modern distributions would expect.
#1 Updated by Jacob Nevins about 1 year ago
I wouldn't be opposed to a solution that we officially make gtk3.22-client the default
Once again I can't build the latest clients; I currently can't build gtk3.22 or gtk3x, as I'm still on Ubuntu 14.04.
Not saying that's a good reason not to change the default, but it will be somewhat awkward. I should probably get a VM or something (I don't currently have any plans to upgrade my main machine).
#2 Updated by Marko Lindqvist about 1 year ago
Ah, gtk3.22-client can't be default in Windows at least, as our msys1 (default env for S2_6 Windows builds) environment has only ancient gtk3 libraries. It would be too confusing to default to another client in Windows than is the global default -> let's keep gtk3-client as the default. If linux distributions want gtk3.22-client to be the default, that's their choice.