qt5base-lts/examples/widgets/tutorials/gettingStarted/gsQt/part4/part4.pro


QT += widgets
SOURCES = main.cpp

# install
target.path = $$[QT_INSTALL_EXAMPLES]/widgets/tutorials/gettingStarted/gsQt/part4
INSTALLS += target
Squashed commit of changes from the 4.8-temp branch. 2011-05-11 15:35:46 +00:00
gettingStarted, part 3-5: sanitize parameter names and compile fix Change-Id: I12795439de71a41728f98b3d3438324664b27a0f Reviewed-by: Friedemann Kleint <Friedemann.Kleint@nokia.com> 2012-05-09 15:56:47 +00:00			`QT += widgets`
Squashed commit of changes from the 4.8-temp branch. 2011-05-11 15:35:46 +00:00			`SOURCES = main.cpp`

			`# 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/tutorials/gettingStarted/gsQt/part4`
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`
Squashed commit of changes from the 4.8-temp branch. 2011-05-11 15:35:46 +00:00