A couple of suggestions:
Please add a dependency for fmt. Build in clean chroot fails without it.
Using environment variables to change the dependencies for cuda/cpu builds seems to cause issues for paru. I believe this is because paru queries aur for dependencies, rather than executing the PKGBUILD to determine them. I think it would be better to split the package into two separate ones (such as "colmap" and "colmap-cuda"), rather than use environment variables. That way, the dependencies seen in aur web/api are correct and builds with paru work, and any other automated build tools should have consistent/reproducible results. This seems a pretty standard way other packages have dealt with different builds for cuda and cpu as well.
As a workaround for paru users, you can "paru -G colmap" to download the PKGBUILD and then "paru -B colmap" to build it from the local copy.
Pinned Comments
bartus commented on 2019-04-10 11:42 (UTC) (edited on 2025-11-05 09:22 (UTC) by bartus)
Please report
issuesandpatchesat GitHub: https://github.com/bartoszek/AUR-colmapThere are flags in the PKGBUILD that control the
cudaandfreeimagebuild:BUILD_CUDA=ONbuildcudadanse mesh solver (defaultON, set toOFFto disablecuda)CUDA_ARCH=nativedefinecudacompute arch (defaultnativeto autodetect current system GPU arch, can be set to e.g,sm_70for specific arch)DISABLE_FREEIMAGE=1replacefreeimagein favour ofopenimageio(default: 0) (upstream PR)Use with your AUR helper or directly with the
makepkg:yay/paru --mflags=DISABLE_FREEIMAGE=1 --mflags=CUDA_ARCH=sm_52makepkg BUILD_CUDA=OFF DISABLE_FREEIMAGE=0