Benchpark output build params

[pearce8]

For those unable/unwilling to use Spack, we need to generate the equivalent of Building instructions

• Check if the benchmark uses auto tools or cmake @scheibelp
• Build the benchmark in CI @slabasan
• Output appropriate params to a file @scheibelp
• If the run passed, add the new instructions to the Sphinx page like this one @slabasan

[becker33]

Here's my idea of approximately what that looks like when put into a documentation page

AMG build section

LLNL will be building AMG with Spack through benchpark. The Spack package is available at … and benchpark is available at …

On El Capitan, Spack uses the following commands to build:

./configure .………..       <——this can be extracted by echo “./configure $(cat $(spack location -i amg)/.spack/spack-configure-args.txt)"
make
make install

For explanations of the AMG build options, run …

[becker33]

Spack extracts this information for both autotools and cmake, but it looks like there's a bug with the cmake extraction. @scheibelp have you looked at this code on the Spack side recently?

[scheibelp]

This is easy for us to do if we have completed build (the result of benchpark setup; ramble workspace setup), and we agreed that this will not be a problem because we are already running the experiments for CUDA, ROCm, and openmp for various systems. Spack generates a complete log of build commands (e.g. if the build is cmake-based, the options we passed to it), and we can also collect the expanded Ramble experiment scripts. I can make a command in benchpark to retrieve these (it would be short).

(this is paraphrased from slack discussion)