Steps refer to "build.sh"
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 45/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- cmake, shell
- Domain
- build-system, documentation
Research direction
Locate the tutorial steps that refer to build.sh and review how the external script is used. Document the equivalent CMake commands explicitly in those steps, with completion meaning the tutorial no longer depends on build.sh for this workflow.
Written by the indexing model from the issue text.
Description
For some reason build.sh from git@github.com:eic/drich-dev.git is used in this tutorial. Perhaps, it's a good idea to advertise CMake commands explicitly.
- Dominant language
- Makefile
- Stars
- 0
- Forks
- 3
- Avg merge
- 1m
- Merged PRs (30d)
- 1
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Similar issues
-
type/automation type/tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
priority: p3
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
googleapis/librarian#7636 ·
-
package-update
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
oSoWoSo/vOid_Community_repOsitory#147 · 1 comment ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
agentic-workflows cascade-suspected
Difficulty 1/5 Under an hour Newbie friendliness 88/100