René Widera

Thanks for the link: https://github.com/boostorg/mp11 The problem is that the CI is covering only compiler for the CPU, important HPC setups Intel, IBM XL, nvcc and hipcc is not covered....

> Maybe you can test this implicitely if we test LLAMA on these compilers. You would only get a real meaningful result if you test the stand-alone version of mp11....

Doxygen can be very useful because you get an overview of namespaces. The problem is that is very hard to see for the user which namespace is for users and...

Than you can not use CUDA. If you install MPI before you install CUDA you can not have a CUDA-aware MPI. If you activate CUDA after you installed alpaka you...

You sill have the possibility to use alpaka via `add_subdirectory` to be able to switch accelerator backends.

With the current approche the admin who provides alpaka as module has hard times to guarantee that alpaka works because what 'make test' checks is not what the iser later...

A possible way would be to keep the live search in cmake after the installation but only allow backends those was activated and therefore could be tested during the install...

@dappchandu Could you please explain your workflow and why do you like to compile within the source code. Currently we do not have a switch to allow compiling within the...

Is your question related to PIConGPU or CMake in general? I am asking because I am wondering what you do with vsomeip and PIConGPU. I would like to understand more...

The failing CI test is the KHi with double precision. It is running into the time limit of 3h.