Chris White

Create tests for code beautifiers

1

None of the code beautifiers are currently tested (except in production). This should be remedied.

https://clang.llvm.org/docs/SourceBasedCodeCoverage.html

Investigate NVCC flag '-forward-unknown-to-host-compiler' on by default

3

https://docs.nvidia.com/cuda/cuda-compiler-driver-nvcc/index.html#options-for-guiding-compiler-driver-forward-host-compiler This seems extremely useful to always turn on.

#349 was proposed but forking FRUIT is less than desirable. Multiple options were presented but not explored.

We could better explain general best practices for CMake options and how the options in BLT work/expected to be used. * Add all options in BLT to a table and...

blt_print_target_info(): Add ability to print children target info

3

This would be helpful to track down where an inherited flag came from. Something like blt_print_target_info(NAME foo CHILDREN true) [Foo: CMake Target] ...lots of info about Foo... [Foo -> Bar]...

We are setting the global property, CMAKE_INSTALL_RPATH_USE_LINK_PATH, if BUILD_SHARED_LIBS is set to true but not the target property, INSTALL_RPATH_USE_LINK_PATH, when an individual library is shared.

It's our variable and should be prefixed to indicate this.

I've had two teams have a bug only show up in a release build and wanted a non-gross way of flagging a very small subset of files to compile as...

CMake's target property doesn't support C++17. It seems like there should be away around this. https://cmake.org/cmake/help/v3.14/prop_tgt/CUDA_STANDARD.html