[Interest] creating a binary .rcc version of a series of Freedesktop icon themes linked through inheritance
elvstone at gmail.com
Sun Jun 25 10:16:33 CEST 2017
2017-06-25 10:04 GMT+02:00 Elvis Stansvik <elvstone at gmail.com>:
> 2017-06-21 11:18 GMT+02:00 René J.V. Bertin <rjvbertin at gmail.com>:
>> I'd like to create a single binary .rcc resource from a total of 4 Freedesktop icon themes that are linked through inheritance.
>> Merging the actual directories is straightforward, but creating a merged index.theme file isn't .
>> Does anyone know of a tool to assist in that part of the merge or is there rcc functionality I'm overlooking that allows a .rcc file to declare a dependency on another .rcc file, such that the application needs only register that single "toplevel" rcc file?
> Even after reading your other mails, I'm not 100% sure I understand
> what you want to do.
> Say you have
> perhaps with inheritances icontheme4 -> icontheme3 -> icontheme2 -> icontheme1.
> Then shouldn't you be able to just generate something like:
> <qresource prefix="/icons">
> I.e. putting the iconthemes side by side in :/icons in the RCC namespace.
> If the application then QIcon::setThemeName("icontheme4"), I think it
> should just work? Why do you need to merge the index.theme files?
> I'm most probably missing some aspect here, but if you now correct me,
> it will hopefully help us understand :)
I should also mention, I'm doing something slightly similar in my app.
and on macOS/Windows, I process both these with rcc and link both into
my application, and do QIcon::setThemeName("breeze"). The "breeze"
theme inherits "hicolor", so my application-specific icons will be
(Though I realize now that this is actually not a good test case for
whether the inheritance works, since even if it didn't work, the icon
engine will fall back to the "hicolor" theme, as mandated by the
>> Interest mailing list
>> Interest at qt-project.org
More information about the Interest