Alex Merry d4ea9ef66d Fix CamelCase header installation.
Installing the Plasma directory (which contains the CamelCase forwarding
headers) breaks on case-insensitive filesystems (eg: Windows) because it
is that directory also contains the lowercase build-time-only forwarding
headers (they are put in the plasma directory). These then overwrite the
real lowercase headers with ones that forward to the source directory.

However, the first argument to ecm_generate_headers is a variable name
containing exactly the CamelCase headers that should be installed,
avoiding this issue rather neatly.

Reviewed-by: Patrick von Reth
2015-01-31 13:01:49 +00:00
..
2013-02-14 17:17:12 +01:00
2013-02-14 17:17:12 +01:00
2014-12-29 13:56:52 +01:00
2014-12-29 13:56:52 +01:00
2014-12-29 13:56:52 +01:00
2014-12-29 13:56:52 +01:00
2014-04-26 01:48:37 +02:00
2014-07-22 03:14:26 +02:00
2014-12-29 13:56:52 +01:00
2014-12-29 13:56:52 +01:00
2014-12-29 13:56:52 +01:00
2014-12-29 13:56:52 +01:00
2013-07-10 00:12:26 +02:00
2014-10-31 17:29:33 +01:00
2014-12-29 13:56:52 +01:00
2014-04-26 01:48:37 +02:00
2013-02-14 17:17:12 +01:00
2014-05-19 18:32:34 +02:00
2014-04-26 01:48:37 +02:00
2014-04-26 01:48:37 +02:00
2014-04-26 01:48:37 +02:00
2014-10-11 21:04:10 +02:00

libplasma

This directory contains the classes making up libplasma, which provides the
core framework used by Plasma applications, such as the Plasma desktop shell
and its components. This includes applet and extension definitions and loading,
common GUI elements, data and service interaction, search system, etc.

Domain specific sets of functionality, e.g. for network awareness or sensors,
are not found here but as DataEngine, Service, Applet, Package, Wallpaper,
ContainmentActions, Containment and other plugins.

Commit Guidelines:
* If your patch is not an obvious or trivial bug fix, have it peer reviewed
  by another Plasma developer; http://reviewboard.kde.org is your friend :)

* All code MUST follow the kdelibs coding style, as found at:
        http://techbase.kde.org/Policies/Kdelibs_Coding_Style

* All new public API MUST have apidox written before committing and must go
  through an API review with another Plasma developer. We have to maintain
  binary compatibility, remember!

Unit tests are next to godliness. (Though as you can see, right now libplasma
is hellbound.)

Please refer to the Plasma website (http://plasma.kde.org) and Plasma wiki
(http://techbase.kde.org/Projects/Plasma) for API documentation and design
documents regarding this library.