Alexander Grund

Updated this with the sanity-check and test for supported driver versions as per nvidia-smi And yes this is a pretty complicated thing as the driver version AND the GPU has...

> you can say with some certainty that the compat libraries will fail on consumer cards. Is that correct? Yes, from the [NVIDIA site](https://docs.nvidia.com/deploy/cuda-compatibility/index.html#forward-compatible-upgrade) > Forward Compatibility is applicable only...

Double checking the boost sources this shouldn't occur when `--layout=tagged` is used. For reference can you attach your EC and the build log? And have you modified the EasyBlock somehow?...

So this is not an issue with the upstream EasyBlock but only with yours: You changed the build to not add the suffix but did not change the sanity check...

If you are really keen on that removal of -x64 why not do it in a hook which creates symlinks?

Pinging in here after discovering an issue caused by not using pip: https://github.com/easybuilders/easybuild-easyblocks/issues/2389

> I'm a bit worried about breaking changes in serialization Then maybe factor out the other changes into separate PRs. E.g. the use of enum-IDs for the controls, the image-handling...

> The thing is, image handling was required to make portraits in lobby in reasonable shape. Splitting settings and lobby portrait into separate PRs seems like an overkill to me....

Thanks, looks good! If you need help with the tests feel free to ask.

@ocaiso: There is a bug with the includes. `-DHAVE_DFTD3 -I -ffree-form` This looks like a shell expansion of a variable that turned out to be empty but isn't supposed to....