Cyrus Harrison
Cyrus Harrison
@gzagaris yes, I think its pretty easy to do this cleanly in BLT
@white238 Conduit is using BLT 0.3.0, should we move to a newer version?
@sshudler -- for ascent, which spack config setup are you using? I suggest using: `scripts/uberenv/spack_configs/llnl/pascal_openmp/` To point to the proper MPI.
correct, our current sphinx builds are incremental. I am open to doing a force rebuild -- what do other folks think? @kennyweiss @white238 ?
the issue is for CMake cuda targets (created via macros in FindCUDA), you can't add any additional flags after the targets are created. The work around is to add the...
Update: setting `CMAKE_CXX_FLAGS` doesn't work w/ BLT's current cuda support. The only path I found was to add the defs to global `CUDA_NVCC_FLAGS` (along with keeping old and restoring them...
FYI: @mclarsen There is work to pivot to CMake's native cuda support: #154
+1 for adding `PUBLIC`, `PRIVATE` or `INTERFACE` option to `blt_add_target_compile_flags` We have a case where we need `PRIVATE` and it's going to be messy w/o blt
I think the support has atrophied. You definitely can compile with coverage flags. Many other folks use other services to generate reports. Codecov is a common one On April 12,...
@markcmiller86 Is the problem just with the mpi tests? I recall that with mpi coverage can crash b/c by default all the tasks try to write to the same file....