AcademySoftwareFoundation / AcademySoftwareFoundation/rez
BUILD_ROOT + BUILD_INSTALLR_ROOT vars
- Dominant language
- Python
- Stars
- 1.1k
- Forks
- 369
- Avg merge
- 12d 3h
- Merged PRs (30d)
- 5
Description
This information is interpretable in other ways, but requires unneeded string manipulation.
REZ_BUILD_INSTALL_PATH points to the installing-variant's build path, e.g. /path/to/pkg/vers/variant
and REZ_BUILD_PATH does the same:
/path/to/builds/pkg/build/variant
however if you need the unvarianted root for some reason during your build, it requires some hoops as mentioned, because REZ_PKGNAME_ROOT is not available yet for the package being built.
Would be nice to have a:
REZ_BUILD_INSTALL_ROOT = /path/to/pkg/vers
REZ_BUILD_ROOT = /path/to/builds/pkg/build
Contributor guide
Research direction
Start by tracing where REZ_BUILD_PATH and REZ_BUILD_INSTALL_PATH are defined and populated. Add the corresponding unvarianted root values, and verify that they resolve to the package/version paths described in the issue during a build.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100