Simplify custom-extension example

Don't confuse people by creating the extension inside a platform plugin.
It's only necessary when modifying Qt's default behaviour, and we're not going
to teach that in this example.

Also remove the load/unload extension logic from the qml example. Don't make
people believe that they have to use a loader.

Change-Id: Id263bb7d77fba176bfb8b6843a6ece9a0a203754
Reviewed-by: Johan Helsing <johan.helsing@qt.io>
Reviewed-by: Pier Luigi Fiorini <pierluigi.fiorini@hawaiios.org>

1 files changed, 26 insertions, 0 deletions

diff --git a/examples/wayland/custom-extension/client-common/client.pro b/examples/wayland/custom-extension/client-common/client.pro
new file mode 100644
index 000000000..9ba72bc9c
--- /dev/null
+++ b/examples/wayland/custom-extension/client-common/client.pro
@@ -0,0 +1,26 @@
+CONFIG += wayland-scanner
+CONFIG += link_pkgconfig
+
+TARGET = custom-wayland
+
+QT += waylandclient-private
+!contains(QT_CONFIG, no-pkg-config) {
+    PKGCONFIG += wayland-client
+} else {
+    LIBS += -lwayland-client
+}
+
+WAYLANDCLIENTSOURCES += ../protocol/custom.xml
+
+OTHER_FILES += client.json
+
+SOURCES += main.cpp \
+           customextension.cpp
+
+HEADERS += customextension.h
+
+PLUGIN_TYPE = platforms
+load(qt_plugin)
+
+# Installation into a "proper" Qt location is most unexpected for from an example.
+CONFIG += install_ok