Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
L
libHexEx
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
HexEx
libHexEx
Commits
ea85fc77
Commit
ea85fc77
authored
4 years ago
by
Max Lyon
Browse files
Options
Downloads
Patches
Plain Diff
fix ci-mac script
parent
fc5ff4d8
Branches
Branches containing commit
No related tags found
1 merge request
!9
Cmake library
Pipeline
#16245
failed
4 years ago
Stage: build
Changes
1
Pipelines
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
CI/ci-mac.sh
+4
-2
4 additions, 2 deletions
CI/ci-mac.sh
with
4 additions
and
2 deletions
CI/ci-mac.sh
+
4
−
2
View file @
ea85fc77
...
...
@@ -32,7 +32,7 @@ OUTPUT='\033[0;32m'
WARNING
=
'\033[0;93m'
#clone OpenVolumeMesh
if
[
!
-d
OpenVolueMesh
]
;
then
if
[
!
-d
OpenVolu
m
eMesh
]
;
then
git clone https://graphics.rwth-aachen.de:9000/OpenVolumeMesh/OpenVolumeMesh
else
cd
OpenVolumeMesh
...
...
@@ -60,6 +60,8 @@ echo "======================================================================"
echo
-e
"
${
NC
}
"
git submodule update
--init
--recursive
if
[
!
-d
build-release-
$BUILDPATH
]
;
then
mkdir
build-release-
$BUILDPATH
fi
...
...
@@ -119,7 +121,7 @@ echo "======================================================================"
echo
-e
"
${
NC
}
"
cd
Build
cd
Build
/bin
#execute tests
./unittests
--gtest_color
=
yes
--gtest_output
=
xml
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment