CMake install: no COMPONENT grouping, Python modules install to lib/ instead of site-packages

Summary

Audit of all install() directives in rocPyDecode as part of the vision-pack aggregator work revealed two gaps: no CPack component grouping making packaging impossible to split, and Python extension modules installing to the wrong prefix.

Findings

1. No COMPONENT grouping on any install() directive

Every install() call in both jpegDecode/CMakeLists.txt and videoDecode/CMakeLists.txt is missing a COMPONENT specification:

# jpegDecode/CMakeLists.txt
install(TARGETS ${ROCPYJPEG_TARGET} LIBRARY DESTINATION ${CMAKE_INSTALL_LIBDIR})
install(DIRECTORY pyRocJpegDecode DESTINATION ${CMAKE_INSTALL_LIBDIR})
install(DIRECTORY samples/rocjpeg DESTINATION ${CMAKE_INSTALL_DATADIR}/rocpyjpegdecode/samples)
install(FILES LICENSE.txt DESTINATION ${CMAKE_INSTALL_DATADIR}/doc/rocpyjpegdecode)

# videoDecode/CMakeLists.txt
install(TARGETS ${ROCPYVIDEO_TARGET} LIBRARY DESTINATION ${CMAKE_INSTALL_LIBDIR})
install(DIRECTORY pyRocVideoDecode DESTINATION ${CMAKE_INSTALL_LIBDIR})
install(DIRECTORY samples/rocdecode DESTINATION ${CMAKE_INSTALL_DATADIR}/rocpydecode/samples)
install(FILES LICENSE.txt DESTINATION ${CMAKE_INSTALL_DATADIR}/doc/rocpydecode)

Without COMPONENT, CPack cannot produce separate runtime, dev, and test packages. Every install target lands in all packages indiscriminately. The sibling libraries (rocAL, MIVisionX, rocCV) all use a consistent 4-component scheme: runtime, dev, asan, test.

Fix: Annotate each install() call with the appropriate component:

• Compiled .so targets → COMPONENT runtime
• Python package directories (pyRocJpegDecode/, pyRocVideoDecode/) → COMPONENT runtime
• Samples → COMPONENT dev
• Tests → COMPONENT test
• LICENSE → COMPONENT runtime

2. Python extension modules install to lib/ instead of site-packages

Both subprojects install compiled Python extension modules to ${CMAKE_INSTALL_LIBDIR} (/opt/rocm/lib/):

install(TARGETS ${ROCPYJPEG_TARGET} LIBRARY DESTINATION ${CMAKE_INSTALL_LIBDIR})
install(DIRECTORY pyRocJpegDecode DESTINATION ${CMAKE_INSTALL_LIBDIR})

This means import rocpyjpegdecode fails unless the user manually adds /opt/rocm/lib to PYTHONPATH. The correct destination is the Python interpreter's site-packages:

execute_process(
  COMMAND "${Python3_EXECUTABLE}" -c
    "import site; print(site.getsitepackages()[0])"
  OUTPUT_VARIABLE PYTHON_SITE_PACKAGES
  OUTPUT_STRIP_TRAILING_WHITESPACE)

install(TARGETS ${ROCPYJPEG_TARGET}
        LIBRARY DESTINATION ${PYTHON_SITE_PACKAGES}
        COMPONENT runtime)
install(DIRECTORY pyRocJpegDecode
        DESTINATION ${PYTHON_SITE_PACKAGES}
        COMPONENT runtime)

Context

Found during vision-pack aggregator repo audit. rocAL has the same Python install path issue (filed as ROCm/rocAL#514). A coordinated fix across both would be ideal so that all ROCm CV Python bindings are importable out of the box without PYTHONPATH changes.

References

• vision-pack aggregator: https://github.com/ROCm/vision-pack
• Related: ROCm/rocAL#514 (same Python install path issue)
• Related: ROCm/MIVisionX#1761 (cmake exports gap)