Skip to content
GitLab
Menu
Projects
Groups
Snippets
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
Menu
Open sidebar
OpenFlipper-Free
OpenFlipper-Free
Commits
b1a16e16
Commit
b1a16e16
authored
Aug 01, 2017
by
Martin Schultz
Browse files
added separate CI scripts for mac
parent
d8d3e81b
Changes
3
Hide whitespace changes
Inline
Side-by-side
CI/ci-mac-build.sh
0 → 100755
View file @
b1a16e16
########################################
# Fetch test data
########################################
rm
-rf
TestData
git clone git@roosevelt:moebius/OpenFlipper-Test-Data.git TestData
########################################
# Build
########################################
if
[
!
-d
build-release
]
;
then
mkdir
build-release
fi
cd
build-release
# Build without ports to avoid qt4 collision
/opt/local/bin/cmake ../
-DCMAKE_CXX_FLAGS
=
'-std=c++11'
-DQWT6_INCLUDE_DIR
=
/Users/jenkins/sw/qwt-6.1.2-Qt5-installed/lib/qwt.framework/Headers
-DQWT6_LIBRARY
=
/Users/jenkins/sw/qwt-6.1.2-Qt5-installed/lib/qwt.framework
-DQT5_INSTALL_PATH
=
/Qt/Qt5.5.1/5.5/clang_64
-DGLEW_INCLUDE_DIR
=
/Users/jenkins/sw/glew-1.10.0-installed/include/
-DGLEW_LIBRARY
=
/Users/jenkins/sw/glew-1.10.0-installed/lib/libGLEW.dylib
make
# Required for the tests to build, if a package was generated
make fixbundle
\ No newline at end of file
CI/ci-mac-deploy.sh
0 → 100755
View file @
b1a16e16
########################################
# Fetch test data
########################################
rm
-rf
TestData
git clone git@roosevelt:moebius/OpenFlipper-Test-Data.git TestData
#paths should be there as they are artifacts from prior stage
cd
build-release
#clean old cmake cache as the path might have changed
find
.
-name
"CMakeCache.txt"
-type
f
-delete
#just to be safe clean the test file definitions too
if
[
-f
CTestTestfile.cmake
]
then
rm
CTestTestfile.cmake
fi
#just to be safe clean the test file definitions too
if
[
-f
DartConfiguration.tcl
]
then
rm
DartConfiguration.tcl
fi
# Build without ports to avoid qt4 collision
# fix pathes if run on a different machine
/opt/local/bin/cmake ../
-DCMAKE_CXX_FLAGS
=
'-std=c++11'
-DQWT6_INCLUDE_DIR
=
/Users/jenkins/sw/qwt-6.1.2-Qt5-installed/lib/qwt.framework/Headers
-DQWT6_LIBRARY
=
/Users/jenkins/sw/qwt-6.1.2-Qt5-installed/lib/qwt.framework
-DQT5_INSTALL_PATH
=
/Qt/Qt5.5.1/5.5/clang_64
-DGLEW_INCLUDE_DIR
=
/Users/jenkins/sw/glew-1.10.0-installed/include/
-DGLEW_LIBRARY
=
/Users/jenkins/sw/glew-1.10.0-installed/lib/libGLEW.dylib
rm
-f
*
.dmg
make OpenFlipper_package
mv
*
.dmg OpenFlipper-Free-GIT-
$CI_BUILD_REF
-QT5
.5.1-CPP11.dmg
\ No newline at end of file
CI/ci-mac-test.sh
0 → 100755
View file @
b1a16e16
########################################
# Fetch test data
########################################
rm
-rf
TestData
git clone git@roosevelt:moebius/OpenFlipper-Test-Data.git TestData
#expect the build-release folder to be present the program binaries are there
cd
build-release
#clean old cmake cache as the path might have changed
find
.
-name
"CMakeCache.txt"
-type
f
-delete
#just to be safe clean the test file definitions too
if
[
-f
CTestTestfile.cmake
]
then
rm
CTestTestfile.cmake
fi
#just to be safe clean the test file definitions too
if
[
-f
DartConfiguration.tcl
]
then
rm
DartConfiguration.tcl
fi
# Build without ports to avoid qt4 collision
# run this prior testing to fix paths
/opt/local/bin/cmake ../
-DCMAKE_CXX_FLAGS
=
'-std=c++11'
-DQWT6_INCLUDE_DIR
=
/Users/jenkins/sw/qwt-6.1.2-Qt5-installed/lib/qwt.framework/Headers
-DQWT6_LIBRARY
=
/Users/jenkins/sw/qwt-6.1.2-Qt5-installed/lib/qwt.framework
-DQT5_INSTALL_PATH
=
/Qt/Qt5.5.1/5.5/clang_64
-DGLEW_INCLUDE_DIR
=
/Users/jenkins/sw/glew-1.10.0-installed/include/
-DGLEW_LIBRARY
=
/Users/jenkins/sw/glew-1.10.0-installed/lib/libGLEW.dylib
########################################
# Test
########################################
# Run tests
cd
tests
bash run_tests.sh
\ No newline at end of file
Write
Preview
Supports
Markdown
0%
Try again
or
attach a new file
.
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment