QtCurve uses it's own bespoke way of handling optional dependencies
whereby if something is not explicitly enabled it will optionally try to
find a library and update an enabled flag before unconditionally trying
to find the library again.
This currently existed for Qt4&5, but not kdelibs.
| Automatic diff as part of commit; lint not applicable. |
| Automatic diff as part of commit; unit tests not applicable. |
Let me get this straight, the goal here is to check if the KDE4 libs are available when building the Qt4 subdir and the user did NOT request KDE support to be built explicitly?
So, when building for Qt4
That's right.
It's what's done for Qt currently. Personally, I think it's somewhat over-engineered, but we should make the KDE finding match.
we should make the KDE finding match.
I don't think there's any particular obligation for that, but personally I'd be fine too with an implementation where you need to request KDE support specifically (basically keeping only item 2 from my breakdown above) or where you'd have to disable it explicitly if you only want the "pure Qt" style. But that might break packaging...