Kenny Weiss

Thanks @white238 - I was able to build and test `blt` on blueos with clang+ gfortran using the llnl-ray host-config with your suggested additions. More details that I accidentally omitted:...

Is anyone interested in developing the Fortran smoke test for openmp and cuda? (@ltaylor16? @aaroncblack? others?) The `C++` ones can be found here: https://github.com/LLNL/blt/tree/master/tests/smoke

I had a second user request for this set of smoke tests.

Thanks @aaroncblack!

@markcmiller86 -- We already support `gcov` and `lcov`, but it looks like it is not documented. The functionality can be found here: https://github.com/LLNL/blt/blob/master/cmake/SetupCodeCoverageReports.cmake I think you have to define a...

If I'm understanding this properly, it sounds like we should be using ```cmake blt_list_append(TO foo ELEMENTS bar) ``` instead of ```cmake set(foo "foo bar") ``` for all the lines in...

The assumption is that all unit tests are independent and the order of tests is random. This appears to be a gtest feature (rather than a bug), see: https://stackoverflow.com/questions/12743114/how-does-google-test-make-test-sequence EDIT:...

Thanks @zbeekman -- our documentation is still very much a work in progress, and some of the existing documentation is already out of date. ``blt_register_library`` definitely \*should\* be documented. In...

> @kennyweiss , do you like which set of parameter names: > * `PROP_NAME_REGEX` and `PROP_VALUE_REGEX` > * `PROPERTY_NAME_REGEX` and `PROPERTY_VALUE_REGEX` > The latter is verbose but at least I...

Thanks for the suggestion. I wasn't aware of this macro. This seems like it could clean up some of our internal logic.