Do they provide any flag in qglobal.h that announces this so that an app can test whether they're using such a bizarre combination? I'd rather not rely on configure tests for this. In fact, I'm about out of love with configure itself.
I'm admittedly caught a bit off heel that such a major feature was removed in 5.6 and am annoyed that we may have to support two paths for a long time. Our use of the embedded web view is quite pedestrian so it's not like it's even a major annoyance.
Do any of our Linux experts have advice on how other portable apps are dealing with this? In the absence of a sane way to detect which path is really available, I may just disable this feature (it's really not used that much anywhere...) on Linux and let the distro people work it out when they make their builds. Then we can rely on a version-based test to handle the case for Mac and Windows builders using the current official Qt configuration to allow spanning the 5.6 boundary where QtWebKit is gone.