https://bugs.kde.org/show_bug.cgi?id=369554
--- Comment #11 from RJVB <rjvber...@gmail.com> ---
OK, so I was wrong in thinking that only a minority of frameworks do this
let's-add-another-directory-layer thing (which still feels like a solution in
search of a problem to me).
Here's the list I've compiled so far, based on the frameworks I install - which
excludes anything (really) not supported on Mac and of course everything that's
not part of the frameworks collection.
Given the length of that list we're looking at a lot of copy/paste and code
duplication (and there's the unknown number of "mere" libraries that may be
making the same error).
So I'd really urge to set the install destitination in the ECM macro used to
generate the forwarding headers, so the change to individual frameworks
CMakeList files can be limited to removing some newly-redundant code:
- attica
- baloo
- kactivities
- kactivities-stats
- kdeclarative{,calendarevents,kquickaddons,quickaddons}
- kdesu
- kdnssd
- kfilemetadata
- kio{core,gui,widgets}
- kjsembed
- kpackage
- kparts
- kpeople{,backend}
- kross
- krunner
- ktexteditor
- kunitconversion
- kxmlrpcclient
- purpose
- solid
- sonnet
- threadweaver
PS: am I right that these forwarding headers could be symlinks on Unix-based
platforms?
--
You are receiving this mail because:
You are watching all bug changes.
