From cccd9ba701e67e280e26fb8fd62e8a2079f54925 Mon Sep 17 00:00:00 2001 From: James Edwards Date: Mon, 5 Mar 2018 14:40:52 -0600 Subject: [PATCH] Update README.md [ROCm/rocminfo commit: 99adf5d85fc65ac46d36c90f346f746427188d4c] --- projects/rocminfo/README.md | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-) diff --git a/projects/rocminfo/README.md b/projects/rocminfo/README.md index 54c3f9fc5d..58728529f3 100644 --- a/projects/rocminfo/README.md +++ b/projects/rocminfo/README.md @@ -4,19 +4,22 @@ ROCm Application for Reporting System Info ## To Build Use the standard cmake build procedure to build rocminfo. The location of ROCM root (parent directory containing ROCM headers and libraries) must be provided -as a cmake argument. For example, building from the CMakeLists.txt directory +as a cmake argument using the standard CMAKE_PREFIX_PATH cmake variable. Building +the package also requires the rocm-cmake helper files. + +For example, building from the CMakeLists.txt directory might look like this: mkdir -p build -cd build +cd buildhttp://www.google.com/ -cmake -DROCM_DIR= .. +cmake -DCMAKE_PREFIX_PATH=/opt/rocm .. make cd .. -Upon a successful build the binary, rocminfo, will be in the build folder. +Upon a successful build the binary, rocminfo, and the python script, rocm_agent_enumerator, will be in the build folder.