-
Jocelyn Turcotte authored
This also removed experimental API uses from the quicknanobrowser example, which should be used mainly for documentation purposes. The quicktestbrowser should be the one that we use from now on as a raw testbed of new APIs. As with other targets in the tests directory, it will only be built by default if Qt is configured with -developer-build (and without -nomake tests). Change-Id: Ib4461c898cd3227bbb810493daac4d841d0d8f3e Reviewed-by:Pierre Rossi <pierre.rossi@gmail.com>
c117207e
quicknanobrowser.pro 501 B
TEMPLATE = appTARGET = quicknanobrowserHEADERS = quickwindow.h \ util.hSOURCES = quickwindow.cpp \ main.cppOTHER_FILES += ContextMenuExtras.qml \ quickwindow.qmlRESOURCES += resources.qrcQT += qml quickQT_PRIVATE += quick-private gui-private core-privateqtHaveModule(widgets) { QT += widgets # QApplication is required to get native styling with QtQuickControls}target.path = $$[QT_INSTALL_EXAMPLES]/webengine/quicknanobrowserINSTALLS += target