subsurface.git/scripts, branch v4.8.6

Travis: update build options

2019-04-08T17:36:03Z

This pulls the latest .travis.yml from master. Which among other things uses a new tool chain for Mac. Which requires some changes to the Travis Mac build script. Signed-off-by: Dirk Hohndel

build-system: add script to build only libdivecomputer

2019-04-04T22:04:42Z

This is used on LGTM (and initially got lost when I merged those changes). Signed-off-by: Dirk Hohndel

facebook: remove the featute from the code base

2019-04-04T17:24:01Z

Remove from: - unit tests - desktop widgets - preferences - core intergration - cmakefiles - build scripts - icons - docs Also remove the plugins and social network integration. Signed-off-by: Lubomir I. Ivanov Signed-off-by: Dirk Hohndel

Travis: OpenSUSE 42.3 / Qt5.6 build issue, use openssl and no libressl

2019-01-22T00:06:01Z

... and remove install of the default (old) libgit2 from OS. That old (0.24.0) libgit2 will be replaced by a newer anyway, so useless to install. But the real change to get this Travis build running again is using the well known openssl instead of libressl. Signed-off-by: Jan Mulder

Travis: OpenSUSE 42.3 / Qt5.6, add missing curl

2019-01-22T00:06:01Z

The install was missing curl. Signed-off-by: Jan Mulder Removed upgrade to newer libgit2. Signed-off-by: Dirk Hohndel

Build: build libgit2 from source when less than 0.26.0

2019-01-22T00:06:01Z

We currently require a minimal version of libgit2 of 0.24.0. From issue #1926 it seems that this version is too old. So, a simple test on Linux to see the behaviour with such an old libgit2, I tried that. Interestingly, with the current version of openssl that old libgit2 version does not even compile from source (known error in libgit2). So, bump our minimal version of libgit2 to 0.26.0. That is also the version we currently use on the Travis and official builds, so well tested. Signed-off-by: Jan Mulder

build system: try harder to checkout the right version

2019-01-22T00:05:03Z

And actually fail a build if that doesn't work. Signed-off-by: Dirk Hohndel

Travis: use 5.12.03 Docker image for Android

2019-01-22T00:02:39Z

With this we have working arm and arm64 images (except that the arm64 image crashes when using Bluetooth). Signed-off-by: Dirk Hohndel

Android Dockerfile: add latest cmake 3.13.2

2019-01-22T00:02:39Z

cmake 3.10 (which comes with Ubuntu 18.04) in combination with Qt 5.12 and the current qt-android-cmake causes an odd bug. Paths are set with a double slash at the start '//' and later in the process this causes garbled path names for some of the objects which in return causes the APKs built in the container to fail. Upgrading the cmake inside the container to 3.13.2 fixes that problem. All the credit for identifying the problem and figuring out a solution goes to Jan Mulder. The resulting container was pushed to Docker hub as version to 5.12.03. Reported-by: Jan Mulder Signed-off-by: Dirk Hohndel

Android Docker: give the docker build its own output tree

2019-01-22T00:02:39Z

Again, this is relevant for developers that do local docker android builds, and normal android builds. A normal build uses the directory subsurface-mobile-build-arm(64), and when doing a docker android build this directory is shared between host and container. That sharing is good, as it nicely exposes the build tree to the host (for easy compare, inspection, etc.). But reusing the same tree as the local one is inconvenient (and possibly dangerous due to all kinds of caching issues). So, give the docker build its own output tree for the shared subsurface-mobile-build-arm(64) build output. Signed-off-by: Jan Mulder