extra-cmake-modules.git, branch v1.5.0 hurd extra-cmake-modules.git Update the comments about the default lib MSVC hacks 2014-11-14T18:20:50+00:00 Alex Merry alex.merry@kde.org 2014-11-14T18:20:50+00:00 3f1020ca0ae58dbfd43169a691313116898647d5 Having done a lot of (unrelated) Windows development recently, I've come to understand the situation much better, so I'm recording that information here for the benefit of others. 
Having done a lot of (unrelated) Windows development recently, I've come
to understand the situation much better, so I'm recording that
information here for the benefit of others.
Set CMAKE_INSTALL_SYSCONFDIR to /etc when CMAKE_INSTALL_PREFIX is /usr 2014-11-07T15:07:31+00:00 Alex Merry alex.merry@kde.org 2014-11-07T15:07:31+00:00 e92da3387bdca560074656b65e3367f9c4086d4c When installing to /usr, we should use /etc for configuration. Using /usr/etc does not make sense. REVIEW: 120246 
When installing to /usr, we should use /etc for configuration. Using
/usr/etc does not make sense.

REVIEW: 120246
Do not skip searching for X11 and Wayland on Windows 2014-11-07T12:26:48+00:00 Alex Merry alex.merry@kde.org 2014-11-07T12:26:48+00:00 32c41706e06e96ab10b757ebe6337071db53fe43 While the search is unlikely to succeed on Windows, having different behaviour between the platforms (eg: find_package(Wayland REQUIRED) was not fatal on Windows, even though Wayland_FOUND would always be FALSE) is not ideal, and if someone did port them to Windows for some reason, the find modules should support that. If applications actually want different behaviour between platforms (like requiring a module on Unix, but not on Windows), they should implement that logic themselves (since they will have to deal with targets not being defined, etc, anyway). REVIEW: 120481 
While the search is unlikely to succeed on Windows, having different
behaviour between the platforms (eg: find_package(Wayland REQUIRED) was
not fatal on Windows, even though Wayland_FOUND would always be FALSE)
is not ideal, and if someone did port them to Windows for some reason,
the find modules should support that.

If applications actually want different behaviour between platforms
(like requiring a module on Unix, but not on Windows), they should
implement that logic themselves (since they will have to deal with
targets not being defined, etc, anyway).

REVIEW: 120481
Upgrade ECM version to 1.5.0. 2014-11-05T19:59:10+00:00 l10n daemon script scripty@kde.org 2014-11-05T19:59:10+00:00 7e535b93cdbb7420d241c00cb9c0abf462ff59d8 






enable -D_USE_MATH_DEFINES on Windows
2014-11-03T09:21:59+00:00

Patrick von Reth
vonreth@kde.org

2014-11-03T09:21:59+00:00

e8d8c44f1552390e30691d3bd8536e5c7cf3543e












Upgrade ECM version to 1.4.0.
2014-10-23T12:48:44+00:00

l10n daemon script
scripty@kde.org

2014-10-23T12:48:43+00:00

95d90ac3cb7a83a265f39b9b3f7a8a4b212a435a












If find_dependency() fails, so should the Config file it is in
2014-10-21T21:00:06+00:00

Alex Merry
alex.merry@kde.org

2014-10-19T11:21:08+00:00

abb5ae4e0164e639e5548c28b9806d9b8aa746bb

REVIEW: 120655





REVIEW: 120655







Wayland and QtWayland protocol scanners
2014-10-19T11:48:42+00:00

Pier Luigi Fiorini
pierluigi.fiorini@gmail.com

2014-09-02T03:32:53+00:00

caebc1a28e7124add5d07638ededb939f8965d0f

Add a couple of find modules for wayland-scanner and qtwaylandscanner.
These modules find the respective executables and create a target that
points to the executable.

Targets are respectively Wayland::Scanner and Wayland::QtScanner.

There are also macros to generate C protocols with wayland-scanner and
C++ wrappers with qtwaylandscanner.

REVIEW: 120034





Add a couple of find modules for wayland-scanner and qtwaylandscanner.
These modules find the respective executables and create a target that
points to the executable.

Targets are respectively Wayland::Scanner and Wayland::QtScanner.

There are also macros to generate C protocols with wayland-scanner and
C++ wrappers with qtwaylandscanner.

REVIEW: 120034







Typo
2014-10-03T20:53:30+00:00

Christophe Giboudeaux
cgiboudeaux@gmx.com

2014-10-03T20:53:30+00:00

9c58807a4a95273538304869c7081972272e796c

GIT_SILENT





GIT_SILENT







allow qmldir to follow qt_sys_path
2014-09-16T09:15:01+00:00

Harald Sitter
sitter@kde.org

2014-09-16T09:15:01+00:00

12d477256d805a5a09b237e15033a5f591d5f0d0

when running with the KDE_INSTALL_USE_QT_SYS_PATHS option allow QMLDIR in
KDEInstallDirs to follow whatever is defined by qmake

this change makes sure that qml plugins will end up in a default Qt path
when using the super special magic flag.





when running with the KDE_INSTALL_USE_QT_SYS_PATHS option allow QMLDIR in
KDEInstallDirs to follow whatever is defined by qmake

this change makes sure that qml plugins will end up in a default Qt path
when using the super special magic flag.