summaryrefslogtreecommitdiffstats
path: root/examples/examples.pro
Commit message (Collapse)AuthorAgeFilesLines
* Don't build QtCompositor unless explicitly enabledAndy Nichols2013-02-051-6/+11
| | | | | | | | | | | | | The QtCompositor API is to be considered experimental in Qt 5.1 and thus it should be disabled from being built by default. If the qmake variable CONFIG contains "wayland-compositor" then the QtCompositor API will be built. Change-Id: If10f5a688749f31338a80be45bbec22a0f2d12da Reviewed-by: Pier Luigi Fiorini <pierluigi.fiorini@gmail.com> Reviewed-by: Jørgen Lind <jorgen.lind@gmail.com> Reviewed-by: Paul Olav Tvete <paul.tvete@digia.com>
* make use of qtHaveModule()Oswald Buddenhagen2013-01-081-2/+2
| | | | | | Change-Id: I7cd0b3e1ac9f326b249bc8ed2ca5abf522cc619a Reviewed-by: Jørgen Lind <jorgen.lind@gmail.com> Reviewed-by: Tasuku Suzuki <stasuku@gmail.com>
* Don't build qwidget compositor when qt is configured with -no-widgetsAndy Nichols2012-06-061-1/+5
| | | | | Change-Id: Ie7952d83527015996fe678ccd68d2984b0119858 Reviewed-by: Samuel Rødal <samuel.rodal@nokia.com>
* Remove the MDI compositor.Robin Burchell2012-01-131-1/+1
| | | | | | | | | | This was broken by the recent input rewrites, and isn't really the 'correct' future-proof path anyway. Wayland is more advocating client-side decorations rather than compositor-side decorations, and this won't work in that world. Change-Id: I187084d7eea785eda43e8658cfd2120205eea211 Sanity-Review: Qt Sanity Bot <qt_sanity_bot@ovi.com> Reviewed-by: Jørgen Lind <jorgen.lind@nokia.com>
* Make wayland actually a moduleJørgen Lind2011-12-071-0/+6
Also fix so that QtCompositor can be built as shared object. + fix so that the default QT_WAYLAND_GL_CONFIG is wayland_egl Change-Id: I02b72e99286584426bd37ab2d00bbc84af11efdc Reviewed-by: Laszlo Agocs <laszlo.p.agocs@nokia.com>