Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
S
skywater-digital-flow
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
Package Registry
Container Registry
Model registry
Operate
Environments
Terraform modules
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
EE272
skywater-digital-flow
Commits
6fe155e0
Commit
6fe155e0
authored
4 years ago
by
Priyanka Raina
Browse files
Options
Downloads
Patches
Plain Diff
Update README.md
parent
dab84d59
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
+10
-1
10 additions, 1 deletion
README.md
with
10 additions
and
1 deletion
README.md
+
10
−
1
View file @
6fe155e0
...
...
@@ -30,16 +30,25 @@ Follow the setup steps at https://github.com/mflowgen/mflowgen.
# Using the Pipecleaners
First, make sure you update various install paths in the
`setup.bashrc`
file. Then source it.
```
bash
source setup.bashrc
```
Next, enter into the build directory of the pipecleaner you want to run, and run the following:
```
cd build
$MFLOWGEN_HOME/configure --design ../design/
```
`$MFLOWGEN_HOME/configure --design ../design/`
Now, if you do
`make status`
you will see all the status of all the steps in the flow. Use the following make targets to run and debug each step.
# Helpful make Targets
*
`make list`
- list all the nodes in the graphs and their corresponding step number
*
`make status`
- list the build status of all the steps
*
`make graph`
- generates a PDF of the graph
*
`make N`
- runs step N
*
`make debug-N`
- pulls up GUI for the appropriate tool for debugging (at the output of step N)
*
`make clean-N`
- removes the folder for step N, and sets the status of steps [N,) to build
*
`make clean-all`
- removes folders for all the steps
*
`make runtimes`
- lists the runtime for each step
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