# KDEInstallDirs6

Define KDE standard installation directories for Qt6/KF6 based software.

Note that none of the variables defined by this module provide any information about the location of already-installed KDE software.

Also sets `CMAKE_INSTALL_PREFIX` to the installation prefix of ECM, unless that variable has been already explicitly set by something else.

Inclusion of this module defines the following variables:

`KDE_INSTALL_<dir>`

  destination for files of a given type

`KDE_INSTALL_FULL_<dir>`

  corresponding absolute path

where `<dir>` is one of (default values in parentheses):

`BUNDLEDIR`

  application bundles (`/Applications/KDE`)

`EXECROOTDIR`

  executables and libraries (`<empty>`)

`BINDIR`

  user executables (`EXECROOTDIR/bin`)

`SBINDIR`

  system admin executables (`EXECROOTDIR/sbin`)

`LIBDIR`

  object code libraries (`EXECROOTDIR/lib`, `EXECROOTDIR/lib64` or `EXECROOTDIR/lib/<multiarch-tuple` on Debian)

`LIBEXECDIR`

  executables for internal use by programs and libraries (`BINDIR` on Windows, `LIBDIR/libexec` otherwise)

`CMAKEPACKAGEDIR`

  CMake packages, including config files (`LIBDIR/cmake`)

`QTPLUGINDIR`

  Qt plugins (`LIBDIR/plugins` or qtpaths’s `QT_INSTALL_PLUGINS`)

`PLUGINDIR`

  Plugins (`QTPLUGINDIR`) [`PLUGIN_INSTALL_DIR`]

`QMLDIR`

  QtQuick2 imports (`LIBDIR/qml` or qtpaths’s `QT_INSTALL_QML`)

`INCLUDEDIR`

  C and C++ header files (`include`)

`LOCALSTATEDIR`

  modifiable single-machine data (`var`)

`SHAREDSTATEDIR`

  modifiable architecture-independent data (`com`)

`DATAROOTDIR`

  read-only architecture-independent data root (`BINDIR/data` on Windows, `share` otherwise)

`DATADIR`

  read-only architecture-independent data (`DATAROOTDIR`)

`DOCBUNDLEDIR`

  documentation bundles generated using kdoctools (`DATAROOTDIR/doc/HTML`)

`KCFGDIR`

  kconfig description files (`DATAROOTDIR/config.kcfg`)

`KCONFUPDATEDIR`

  kconf_update scripts (`DATAROOTDIR/kconf_update`)

`KXMLGUIDIR`

  kxmlgui .rc files (`DATAROOTDIR/kxmlgui5`)

`KAPPTEMPLATESDIR`

  KAppTemplate and KDevelop templates (`DATAROOTDIR/kdevappwizard/templates`)

`KFILETEMPLATESDIR`

  KDevelop file templates (`DATAROOTDIR/kdevfiletemplates/templates`)

`KNOTIFYRCDIR`

  knotify description files (`DATAROOTDIR/knotifications6`)

`ICONDIR`

  icons (`DATAROOTDIR/icons`)

`LOCALEDIR`

  locale-dependent data (`DATAROOTDIR/locale`)

`SOUNDDIR`

  sound files (`DATAROOTDIR/sounds`)

`TEMPLATEDIR`

  templates (`DATAROOTDIR/templates`)

`WALLPAPERDIR`

  desktop wallpaper images (`DATAROOTDIR/wallpapers`)

`APPDIR`

  application desktop files (`DATAROOTDIR/applications`)

`DESKTOPDIR`

  desktop directories (`DATAROOTDIR/desktop-directories`)

`MIMEDIR`

  mime description files (`DATAROOTDIR/mime/packages`)

`METAINFODIR`

  AppStream component metadata files (`DATAROOTDIR/metainfo`)

`QTQCHDIR`

  documentation bundles in QCH format for Qt-extending libraries (`DATAROOTDIR/doc/qch` or qtpaths’s `QT_INSTALL_DOCS`)

`QCHDIR`

  documentation bundles in QCH format (`DATAROOTDIR/doc/qch`)

`QTMETATYPESDIR`

  Qt metatypes files (`metatypes` or qtpaths’s `QT_INSTALL_ARCHDATA/metatypes`). Since 6.27.

`MANDIR`

  man documentation (`DATAROOTDIR/man`)

`INFODIR`

  info documentation (`DATAROOTDIR/info`)

`DBUSDIR`

  D-Bus (`DATAROOTDIR/dbus-1`)

`DBUSINTERFACEDIR`

  D-Bus interfaces (`DBUSDIR/interfaces`)

`DBUSSERVICEDIR`

  D-Bus session services (`DBUSDIR/services`)

`DBUSSYSTEMSERVICEDIR`

  D-Bus system services (`DBUSDIR/system-services`)

`SYSCONFDIR`

  read-only single-machine data (`etc`, or `/etc` if `CMAKE_INSTALL_PREFIX` is `/usr`)

`CONFDIR`

  application configuration files (`SYSCONFDIR/xdg`)

`AUTOSTARTDIR`

  autostart files (`CONFDIR/autostart`)

`LOGGINGCATEGORIESDIR`

  Qt logging categories files directory (`DATAROOTDIR/qlogging-categories6`)

`JARDIR`

  Java AAR/JAR files for Android.

`SYSTEMDUNITDIR`

  Systemd Units (`lib/systemd`)

`SYSTEMDUSERUNITDIR`

  Systemd User Units (`lib/systemd/user`)

If `KDE_INSTALL_USE_QT_SYS_PATHS` is set to `TRUE` before including this module, the default values for some variables are instead queried from Qt6’s qmake (where mentioned in the parentheses above). If not set, it will default to `TRUE` if Qt6’s qmake is found and it’s `QT_INSTALL_PREFIX` is the same as `CMAKE_INSTALL_PREFIX`, otherwise default to `FALSE`. This variable should NOT be set from within CMakeLists.txt files, instead is intended to be set manually when configuring a project which uses KDEInstallDirs (e.g. by packagers).

In addition, for each `KDE_INSTALL_*` variable, an equivalent `CMAKE_INSTALL_*` variable is defined, if such a variable is also defined by the `GNUInstallDirs` module (shipped with CMake). If `KDE_INSTALL_DIRS_NO_CMAKE_VARIABLES` is set to `TRUE`, no variables with a `CMAKE_` prefix will be defined by this module (other than `CMAKE_INSTALL_DEFAULT_COMPONENT_NAME` - see below).

The `KDE_INSTALL_<dir>` variables may be passed to the `DESTINATION` options of `install()` commands for the corresponding file type. They are set in the CMake cache, and so the defaults above can be overridden by users.

Note that if the `KDE_INSTALL_<dir>` or `CMAKE_INSTALL_<dir>` variables are set before `include(KDEInstallDirs)`, they won’t be overwritten by `KDEInstallDirs`. This is useful if you eg. want to use CMake command line variable definitions to set custom values. There are however some other implications you need to be aware of: `GNUInstallDirs` defines `CMAKE_INSTALL_<dir>` variables, before hence `KDEInstallDirs` will not overwrite them if it is included later. In most cases this is unintended and if you need to include `GNUInstallDirs` you should always do that after after you included `KDEInstallDirs`. Be aware that Qt uses `GNUInstallDirs` since Qt6 and hence `find_package(Qt6 ...)` is equivalent to `include(GNUInstallDirs)` in this case.

If you set custom values to `KDE_INSTALL_<dir>` or `CMAKE_INSTALL_<dir>` as described above always both forms of the variable will be affected. The effect of passing multiple forms of the same variable eg. on the command line (such as `KDE_INSTALL_BINDIR` and `CMAKE_INSTALL_BINDIR`) is undefined and should be avoided.

The variable `KDE_INSTALL_TARGETS_DEFAULT_ARGS` is also defined. This should be used when libraries or user-executable applications are installed, in the following manner:

    install(TARGETS mylib myapp ${KDE_INSTALL_TARGETS_DEFAULT_ARGS})

It MUST NOT be used for installing plugins, system admin executables or executables only intended for use internally by other code. Those should use `KDE_INSTALL_PLUGINDIR`, `KDE_INSTALL_SBINDIR` or `KDE_INSTALL_LIBEXECDIR` respectively.

Additionally, `CMAKE_INSTALL_DEFAULT_COMPONENT_NAME` will be set to `${PROJECT_NAME}` to provide a sensible default for this CMake option.

Note that mixing absolute and relative paths, particularly for `BINDIR`, `LIBDIR` and `INCLUDEDIR`, can cause issues with exported targets. Given that the default values for these are relative paths, relative paths should be used on the command line when possible (eg: use `-DKDE_INSTALL_LIBDIR=lib64` instead of `-DKDE_INSTALL_LIBDIR=/usr/lib/lib64` to override the library directory).

The `KDE_INSTALL_PREFIX_SCRIPT` option will install a ${CMAKE_INSTALL_PREFIX}/prefix.sh file that allows to easily incorporate the necessary environment variables for the prefix into a process.