Build script: use Subsurface-testing branches of marble and libdivecomputer

While in a release we'd want to use the corresponding release branches, it
seems to make more sense to me to switch to the testing branches for Subsurface
master.

Signed-off-by: Dirk Hohndel (Intel) <dhohndel@dhohndel-mac02.jf.intel.com>
This commit is contained in:
Dirk Hohndel (Intel) 2015-06-02 10:41:29 -07:00
parent 3de62f5275
commit 5823683229

View file

@ -96,11 +96,11 @@ if [ ! -d libdivecomputer ] ; then
if [[ $1 = local ]] ; then
git clone $SRC/../libdivecomputer libdivecomputer
else
git clone -b Subsurface-4.4 git://subsurface-divelog.org/libdc libdivecomputer
git clone -b Subsurface-testing git://subsurface-divelog.org/libdc libdivecomputer
fi
fi
cd libdivecomputer
git checkout Subsurface-4.4
git checkout Subsurface-testing
if [ ! -f configure ] ; then
autoreconf --install
fi
@ -116,11 +116,11 @@ if [ ! -d marble-source ] ; then
if [[ $1 = local ]] ; then
git clone $SRC/../marble-source marble-source
else
git clone -b Subsurface-4.4 git://subsurface-divelog.org/marble marble-source
git clone -b Subsurface-testing git://subsurface-divelog.org/marble marble-source
fi
fi
cd marble-source
git checkout Subsurface-4.4
git checkout Subsurface-testing
mkdir -p build
cd build
cmake -DCMAKE_BUILD_TYPE=Release -DQTONLY=TRUE -DQT5BUILD=ON \