qt5base-lts/examples/widgets/desktop/systray/systray.pro

HEADERS       = window.h
SOURCES       = main.cpp \
                window.cpp
RESOURCES     = systray.qrc

QT += widgets

# install
target.path = $$[QT_INSTALL_EXAMPLES]/widgets/desktop/systray
INSTALLS += target
Re-add the Systray example. Remove its dependency on QtSvg by converting the icons to (optimized) png files. Change-Id: If63257938dc816d7ab76a3042b9ac88ef3d51b07 Reviewed-by: Friedemann Kleint <Friedemann.Kleint@nokia.com> 2012-03-09 08:40:57 +00:00			`HEADERS = window.h`
			`SOURCES = main.cpp \`
			`window.cpp`
			`RESOURCES = systray.qrc`

			`QT += widgets`

			`# install`
Examples: Install to $$[QT_INSTALL_EXAMPLES]/$submodule/$example This makes the structure of the examples after an 'make install' similar to the one in a 'developer build'. Change-Id: I9120bd741fab332e64e30adc01cefe87e5633454 Reviewed-by: Martin Smith <martin.smith@digia.com> 2012-11-26 13:04:31 +00:00			`target.path = $$[QT_INSTALL_EXAMPLES]/widgets/desktop/systray`
centralize and fixup example sources install targets it's confusing for the users if the examples' project files contain code to install their own sources. also, this constitutes an enormous code duplication, and lots of mistakes. consequently, automate it. more or less as a side effect, this also removes the entirely meaningless target installs in subdirs projects. Task-number: QTBUG-28184 Change-Id: I9fc1367a06db9e2c46aeb67d68729a4f67163ef9 Reviewed-by: hjk <qthjk@ovi.com> 2012-11-27 19:40:16 +00:00			`INSTALLS += target`