summaryrefslogtreecommitdiffstats
path: root/backend-shared
diff options
context:
space:
mode:
authorGravatar jan Iversen <jan@casacondor.com>2019-12-14 22:15:12 +0100
committerGravatar Dirk Hohndel <dirk@hohndel.org>2019-12-24 08:44:23 +0900
commit0ab8bd5ecaf0cbd92387283e3c21aa47f72ce977 (patch)
tree85e8831833179237c92d22b745d19f72e2a6461d /backend-shared
parenta4d299e01e216ef2db61d98d304d091da39ee51d (diff)
downloadsubsurface-0ab8bd5ecaf0cbd92387283e3c21aa47f72ce977.tar.gz
build-system: add new root dir backend-shared
WARNING: multi directory commit, needed to secure it builds. leaving the shared backend sources in core, imposes a severe limitation, that they cannot make use of e.g. qt-models, because that is created after core (first library to be created). The shared backend uses functionality from core and qt-models, so it must be created when those are available and before desktop-widgets or mobile-widgets are created. Make a new root directory "backend-shared" with empty CMakeLists.txt Signed-off-by: Jan Iversen <jan@casacondor.com>
Diffstat (limited to 'backend-shared')
-rw-r--r--backend-shared/CMakeLists.txt2
-rw-r--r--backend-shared/README11
2 files changed, 13 insertions, 0 deletions
diff --git a/backend-shared/CMakeLists.txt b/backend-shared/CMakeLists.txt
new file mode 100644
index 000000000..750d22a98
--- /dev/null
+++ b/backend-shared/CMakeLists.txt
@@ -0,0 +1,2 @@
+# backend functionality shared between Desktop (UI) and Mobile (QML)
+
diff --git a/backend-shared/README b/backend-shared/README
new file mode 100644
index 000000000..f82fc2fed
--- /dev/null
+++ b/backend-shared/README
@@ -0,0 +1,11 @@
+This directory contains shared UI backend code shared between
+the desktop version and the mobile version.
+
+The backend code sits between the actual functionality, which
+are implemented in core and qt-models, and the UI/QML which
+are implemented in desktop-widgets and mobile-widgets.
+
+The idea of backend is not to duplicate code, and at the same time
+limit the UI and QML to only deal with real GUI.
+
+The first implementations for backend are "export" and "diveplanner".