Using SCR bootstrap in an external build.
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 108
- Forks
- 37
- PR merge metrics
- No merged PRs in 30d
Description
In my use case, I have the following project structure.
- My project
- external
- SCR
- venv
- scripts
Currently, there is no way to pass the INSTALL DIR of venv to the bootstrap script.
This builds and installs everything within external/scr/install
When I use CMAKE_INSTALL_PREFIX with SCR, it does not find it as the install folder is not there.
I was hoping if we could pass INSTALL_DIR as an optional argument to the bootstrap script.
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.
Research direction
Start by inspecting the SCR bootstrap script and how it handles CMAKE_INSTALL_PREFIX during an external build. Reproduce the project layout described in the issue, then verify that an optional INSTALL_DIR is accepted and that the build installs into the requested venv location.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cmake
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100