[WIP] Output More Versions

[ax3l]

Add more build information and dependency information to our output on startup. This increases reproducibility by tracking more software dependencies and build options.

Example output when built with CMake:

MPI initialized with 1 MPI processes
MPI initialized with thread support level 3
OMP initialized with 8 OMP threads
AMReX (22.01-16-g7314e78fecda) initialized
WarpX (22.01-27-g73858579e907-dirty)
Build options:
  Build type: Release
  OS:         Linux-5.4.0-56-generic
  arch:       x86_64
  CXX:        GNU (9.3.0)
  accelerate: OpenMP (4.5)
Third party:
  CMake:      3.22.1
  MPI:        
    standard: 3.1
    flavor:   OpenMPI (4.1.2)
  PICSAR:     7b5449f92a4b
  openPMD:    0.14.3 (standard: 1.1.0; files: json,bp,sst,ssc,h5)

[ax3l]

@cyrush is there an "include + macro / runtime API query" way to query the version of Ascent/Conduit? :)

@c-wetterer-nelson s there an "include + macro / runtime API query" way to query the version of SENSEI? :)

@mgates3 is there an "include + macro / runtime API query" way to query the version of BLAS++/LAPACK++? :)

[dpgrote]

Since you are changing this, can the version information be printed earlier? A number of things happen before WarpX::InitData is called and if something goes wrong there, the version info won't be output. A user I'm working with has a case where a problem is happening in ParseGeometryInput for example and there is no version info to help debug it.

[ax3l]

I think we can move our info definitely up. Only the AMReX info will first be printed here, I think.

[cyrush]

@ax3l yes, here is an example of how to get the ascent version:

conduit::Node n_about_ascent;
ascent::about(n_about_ascent);
amrex::Print() << n_about_ascent["version"].as_string();

[ax3l]

Can also use

set_property(SOURCE source.cpp PROPERTY COMPILE_DEFINITIONS 
VAR1=${MY_VAR1} VAR2=${MY_VAR2})

for ablastr/version/VersionFormat.cpp

[ax3l]

Suggested change

	std::map< int, std::string > mapOpenMP = {
	std::map< int, std::string > const mapOpenMP = {

[mgates3]

Found this buried in my inbox. @ax3l Yes, BLAS++ and LAPACK++ have C++ macros BLASPP_VERSION and LAPACKPP_VERSION, and also runtime functions blaspp_version() and lapackpp_version().

// Version 2022.05.00
#define LAPACKPP_VERSION 20220500
int lapackpp_version();

// Version 2022.05.00
#define BLASPP_VERSION 20220500
int blaspp_version();

Incidentally, we released those versions last month.