Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
D
dune-codegen
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container Registry
Model registry
Operate
Environments
Monitor
Incidents
Service Desk
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
This is an archived project. Repository and other project resources are read-only.
Show more breadcrumbs
Christian Heinigk
dune-codegen
Commits
c06fbaa9
Commit
c06fbaa9
authored
7 years ago
by
Dominic Kempf
Browse files
Options
Downloads
Patches
Plain Diff
Minor fixes to the README file
parent
ded458ea
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
README.md
+6
-6
6 additions, 6 deletions
README.md
with
6 additions
and
6 deletions
README.md
+
6
−
6
View file @
c06fbaa9
# dune-perftool
# dune-perftool
dune-perftool is an active research
code
project with the goal of
dune-perftool is an active research project with the goal of
generating high-performance integration kernels for dune-pdelab.
generating high-performance integration kernels for dune-pdelab.
**Note**
: Due to the research character of the code things will change
**Note**
: Due to the research character of the code things will change
a lot and there is no guarantee
o
f interface stability ;).
a lot and there is no guarantee f
or
interface stability ;).
## Dependencies
## Dependencies
...
@@ -21,7 +21,7 @@ dune-perftool depends on the following software packages:
...
@@ -21,7 +21,7 @@ dune-perftool depends on the following software packages:
## Cloning and Patching
## Cloning and Patching
We use several su
m
bodules so you should clone with the --recursive option:
We use several sub
m
odules so you should clone with the
`
--recursive
`
option:
```
```
git clone --recursive ssh://git@parcomp-git.iwr.uni-heidelberg.de:20022/dominic/dune-perftool.git
git clone --recursive ssh://git@parcomp-git.iwr.uni-heidelberg.de:20022/dominic/dune-perftool.git
...
@@ -33,9 +33,9 @@ or
...
@@ -33,9 +33,9 @@ or
git clone --recursive https://parcomp-git.iwr.uni-heidelberg.de/dominic/dune-perftool.git
git clone --recursive https://parcomp-git.iwr.uni-heidelberg.de/dominic/dune-perftool.git
```
```
If you have a feature branch
'
feature/my-branch
'
where you change the
If you have a feature branch
`
feature/my-branch
`
where you change the
submodules of dune-perftool and you want to test your branch it makes
submodules of dune-perftool and you want to test your branch it makes
sense to checkout this branch directly:
sense to checkout this branch directly
in a fresh clone
:
```
```
git clone --recursive -b feature/my-branch ssh://git@parcomp-git.iwr.uni-heidelberg.de:20022/dominic/dune-perftool.git
git clone --recursive -b feature/my-branch ssh://git@parcomp-git.iwr.uni-heidelberg.de:20022/dominic/dune-perftool.git
...
@@ -81,7 +81,7 @@ the following:
...
@@ -81,7 +81,7 @@ the following:
```
```
CMAKE_FLAGS="
CMAKE_FLAGS="
-DDUNE_FORCE_PYTHON3=1
-DDUNE_
PYTHON_
FORCE_PYTHON3=1
-DDUNE_PYTHON_ALLOW_GET_PIP=1
-DDUNE_PYTHON_ALLOW_GET_PIP=1
-DDUNE_PYTHON_VIRTUALENV_SETUP=1
-DDUNE_PYTHON_VIRTUALENV_SETUP=1
-DCMAKE_BUILD_TYPE=Release
-DCMAKE_BUILD_TYPE=Release
...
...
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