Mark C. Miller

@iulian787 and @vijaysm one option we're considering here is to do away with serial/parallel builds of HDF5. We would build only parallel HDF5 and everything in VisIt that depended on...

@cyrush if we can do that with HDF5, why can't we do that with all of VisIt and get away from building all of VisIt with `_par` and `_ser` variants...

> MPI support is controlled by compiler defines, which yield the serial and parallel libs. @cyrush...right...we simply adjust those `#if PARALLEL` code blocks to all be run-time conditionals and then...

Summarizing... Ok, so inputs from @cyrush, @qkoziol, and @vijaysm all suggest the right way to proceed is to do away with building dependencies in different ways (e.g. with and without...

@cyrush, @qkoziol, and @vijaysm, one issue I am encountering is all the libraries VisIt builds which depend on HDF5 (conduit, mfem, cgns, netcdf, xdmf, silo, h5part). They themselves may not...

@vijaysm and @qkoziol thanks for your inputs on this :muscle:. @qkoziol I like some of the ideas your are floating here. But, MPI stub functions scare me just a tad...

@cyrush I can answer some of the details of what is happening with `build_visit`. Most of the libs that depend on only sereial HDF5 are compiled using `build_visit`'s `C_COMPILER` and...

I would much prefer to live in a world where I am not required to specify a path to a header file (or for that matter a library file) my...

> OBJ doesn't let you directly export variables but if you want colors you need to choose a variable to export. So for OBJ we should not gray this out....

Not sure. That said, I am talking about *variables*. You are talking about *colors*. Are these one in the same?