MatX: Efficient C++17 GPU numerical computing library with Python-like syntax

Re:MatX: Efficient C++17 GPU numerical computing library wit... by dheera on Wednesday October 04, 2023 @12:38AM (#37760921)

Usually the CUDA versions end up uninstalling other CUDA versions and drivers due to package manager issues.

I wish nvidia would just release a `sudo apt install cuda-all` that just keeps you updated with ALL possible cuda versions simultaneously. I know it would be 20GB but that's fine, it's a drop in the bucket compared to the datasets I play with.

[ Parent | on HN ]

Re:MatX: Efficient C++17 GPU numerical computing library wit... by cburdick13 on Wednesday October 04, 2023 @01:03AM (#37761029)

If you use the run files rather than the package manager files it's always installed in completely separate folders inside /use/local/cuda.

What you're describing with an "all" install can somewhat be accomplished with containers right now and none of the dependency problems.

[ Parent | on HN ]

Re:MatX: Efficient C++17 GPU numerical computing library wit... by dheera on Wednesday October 04, 2023 @01:09AM (#37761053)

But containers, X forwarding, visualization, and OpenGL is a complete shitshow. I have apps that work outside of a container but freeze the UI that the mouse pointer won't even work when run from within a container.

[ Parent | on HN ]

Re:MatX: Efficient C++17 GPU numerical computing library wit... by touisteur on Thursday October 05, 2023 @10:58AM (#37779447)

+1 for runfiles but beware of the multi-gigabyte installer + installed footprint. Not complaining per-se, just plan for it.

[ Parent | on HN ]

Re:MatX: Efficient C++17 GPU numerical computing library wit... by dheera on Thursday October 05, 2023 @05:57PM (#37784800)

Problem with runfiles is I've run into other .deb packages that I'd like to use that are marked as dependent on 'cuda'.

Using a runfile is ditching the package manager on a package-managed system, instead of using the package manager correctly.

[ Parent | on HN ]