|This page is under construction. This page is actively being developed and updated with new information, and may be incomplete. You can help by editing this page|
One of the most common ways to name icons in sources is a "compact" form which includes various details. The format is the following:
To install icons with the CMake buildsystem using the KDE4 macros, you just need to use one macro:
<installation directory> is usually
|This CMake macros takes all the icons with a "compact" naming in the current directory, and installs them in the <installation directory> specified. Hence, to install some icons in one location and some in another, the only solution is to put the icons in different directories with ad-hoc kde4_install_icons() calls.|
There are few things to keep into account when choosing which icon theme use for icons, and which directory install them into.
One thing to remember is that the hicolor icon theme (called fallback theme) is the only common denimonator among all the possible icon themes.
When install the application icon of an application (i.e. the icon representing the application, usually named after the application itself), you want to make it used by anyone, regardless of which icon theme they are using. Because of this:
This is the case for KDE applications with nothing like plugins for plugin systems not of the own application itself (like kparts, kioslaves, konqueror service menus, etc). In this case:
Installing the icons in a icons subdirectory of the application data directory allows the application to make use of them without "polluting" the global icon theme with application-specific icons, but still making icon themes able to override the hicolor icons of the application with own icons.