Hi Kip,
> Perhaps another option is having a libceres-cuda-dev / libceres3-cuda
> packages that are built with CUDA?
Makes sense! However, it requires a brand new source package ceres-solver-cuda
to generate these CUDA specific binary packages which will be in the "contrib"
area. This would be s
On Thu, 2024-01-04 at 16:17 +0100, Francois Mazen wrote:
> The nvidia-cuda-dev package is part of the non-free area in the
> Debian archive [1] because if does not comply with the DFSG [2].
> If we set it as a build dependency of ceres-solver (and also the
> nvidia runtime as a package dependency),
Hi Kip,
> I think the solution is to simply explicitly add nvidia-cuda-dev to the Build-
> Depends stanza of of the ceres-solver source package in debian/control.
The nvidia-cuda-dev package is part of the non-free area in the Debian archive
[1] because if does not comply with the DFSG [2].
If we
Package: libceres3
Version: 2.1.0+really2.1.0+dfsg-2
Severity: wishlist
X-Debbugs-Cc: k...@thevertigo.com
Dear Maintainer,
The current ceres-solver source package may not always build with CUDA support,
even though it is enabled by default. In upstream's CMakeLists.txt CUDA is
enabled by default,
4 matches
Mail list logo
