Support TheRock ROCm “Python-managed” install paths (non-/opt/rocm)
@zufayu is already working on this.
Since Mar 4, 2026.
- Dominant language
- Python
- Stars
- 565
- Forks
- 585
- Avg merge
- 3d 4h
- Merged PRs (30d)
- 366
Description
After installing the latest ROCm 7.12 (TheRock / ROCm Core SDK stream) following the official guide , and initializing with: rocm-sdk init, the resulting SDK layout does not follow the traditional /opt/rocm or /opt/rocm-x.y.z convention on a vanilla ubuntu:22.04 base image.
Instead, the SDK is installed / expanded under a Python site-packages managed location, e.g.:
/usr/local/lib/python3.10/site-packages/_rocm_sdk_core
(and other rocm_sdk* directories)
This path change breaks tools and scripts that assume ROCm lives under /opt/rocm* (e.g., hardcoded discovery, PATH/CMAKE_PREFIX_PATH logic, or “rocm root” probing).
Request / ask
As TheRock-derived ROCm becomes a priority target, please consider updating the tooling to discover and support ROCm installations rooted in the rocm_sdk* site-packages paths (in addition to /opt/rocm*).
Contributor guide
No contributing guide indexed for this repository
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.
Assessment
This issue has not been assessed yet.