qt5base-lts/examples/network/dnslookup/dnslookup.pro

TEMPLATE = app
QT = core network
mac:CONFIG -= app_bundle
win32:CONFIG += console
HEADERS += dnslookup.h
SOURCES += dnslookup.cpp

# install
target.path = $$[QT_INSTALL_EXAMPLES]/network/dnslookup
INSTALLS += target
Add support for DNS lookups using native APIs The QDnsLookup class provides asynchronous APIs for performing DNS lookups. For now, the following lookups are supported: - A and AAAA - CNAME as defined per RFC 1035 - MX as defined per RFC 1035 - NS as defined per RFC 1035 - PTR as defined per RFC 1035 - SRV as defined per RFC 2782 - TXT as defined per RFC 1035 Task-number: QTBUG-10481 Change-Id: I46c1741ec23615863eeca3a1231d5e3f8942495e Reviewed-by: Thiago Macieira <thiago.macieira@intel.com> 2012-01-23 17:25:39 +00:00			`TEMPLATE = app`
			`QT = core network`
			`mac:CONFIG -= app_bundle`
			`win32:CONFIG += console`
			`HEADERS += dnslookup.h`
			`SOURCES += dnslookup.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]/network/dnslookup`
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`