Package manager integration#
2025-05-14
5 min read time
This section provides information about the required meta-packages for the following AMD ROCm programming models:
- Heterogeneous-Computing Interface for Portability (HIP) 
- OpenCL™ 
- OpenMP™ 
ROCm package naming conventions#
A meta-package is a grouping of related packages and dependencies used to support a specific use case.
Example: Running HIP applications
All meta-packages exist in both versioned and non-versioned forms.
- Non-versioned packages: For a single-version installation of the ROCm stack 
- Versioned packages: For multi-version installations of the ROCm stack 
 
The figure above demonstrates the single and multi-version ROCm packages’ naming structure, including examples for various Linux distributions. See terms below:
Module - It is the part of the package that represents the name of the ROCm component.
Example: The examples mentioned in the image represent the ROCm HIP module.
Module version - It is the version of the library released in that package. It should increase with a newer release.
Release version - It shows the ROCm release version when the package was released.
Example: 50400 points to the ROCm 5.4.0 release.
Build id - It represents the build number for that release.
Arch - It shows the architecture for which the package was created.
Distro - It describes the distribution for which the package was created. It is valid only for rpm packages.
Example: el8 represents RHEL 8.x packages.
Components of ROCm programming models#
The figure below demonstrates the high-level layered architecture of ROCm programming models and their meta-packages. All meta-packages are a combination of required packages and libraries.
 
Note
The preceding figure is for informational purposes only. The individual packages in a meta-package are subject to change. To avoid conflicts, install meta-packages, not individual packages.
Example:
- rocm-hip-runtimeis used to deploy on supported machines to execute HIP applications.
- rocm-hip-sdkcontains runtime components to deploy and execute HIP applications.
Note
rocm-llvm is not a meta-package; it’s a single package that installs the ROCm Clang compiler files.
| Package | Description | 
|---|---|
| 
 | All ROCm core packages, tools, and libraries. | 
| 
 | The ROCm runtime. | 
| 
 | Debug and profile HIP applications. | 
| 
 | Run HIP applications writen for the AMD platform. | 
| 
 | Develop applications on HIP or port from CUDA. | 
| 
 | Run OpenCL-based applications on the AMD platform. | 
| 
 | Develop OpenCL-based applications for the AMD platform. | 
| 
 | HIP libraries optimized for the AMD platform. | 
| 
 | Develop or port HIP applications and libraries for the AMD platform. | 
| 
 | Key machine learning libraries. Includes MIOpen. | 
| 
 | Develop and run machine learning applications for AMD. | 
| 
 | Run OpenMP-based applications on the AMD platform. | 
| 
 | Develop OpenMP-based applications for the AMD software. | 
Packages in ROCm programming models#
This section discusses the available meta-packages and their packages. The following table shows the meta-packages and their associated (meta-)packages in a ROCm programming model.
Note
rocm-utils is a legacy meta-package that includes rocminfo, rocm-cmake, and rocm-core.
Other meta-packages manage the installation of these components.
| Meta package | Associated packages | 
|---|---|
| 
 | Meta packages: 
 Packages: 
 | 
| 
 | Meta packages: 
 Packages: 
 | 
| 
 | Meta packages: 
 Packages: 
 | 
| 
 | Meta packages: 
 Packages: 
 | 
| 
 | Meta packages: 
 Packages: 
 | 
| 
 | Meta packages: 
 Packages: 
 | 
| 
 | Meta packages: 
 Packages: 
 | 
| 
 | Meta packages: 
 Packages: 
 | 
| 
 | Packages: 
 | 
| 
 | Meta packages: 
 Packages: 
 | 
| 
 | Meta packages: 
 Packages: 
 | 
| 
 | Meta packages: 
 Packages: 
 |