ROCm / ROCm/rocAL

[Issue]: rocAL cmake checks MIVisionX for dependency/backend, rather than vx_rpp

Open
#501 3 comments 0 reactions 1 assignee View on GitHub

@levxn is already working on this.

Since Aug 7, 2026.

bug
Dominant language
C++
Stars
25
Forks
26
Avg merge
5d 1h
Merged PRs (30d)
2

Description

In rocAL/CMakeLists.txt, rocAL checks for MIVisionX as a dependency, and also checks MIVisionX's backend to determine if rocAL needs to fallback to CPU.

However, the real dependency is vx_rpp (extension within MIVisionX).
For example, if MIVisionX is built with HIP backend but vx_rpp with CPU backend, then rocAL must be built with CPU backend. But currently, CMakeLists only checks MIVisionX, and so will not detect that rocAL must be built with CPU backend.
vx_rpp is both the required and sufficient check.

The README could also have better documentation on this dependency.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.