Package Details: dlib 19.22-2

Git Clone URL: (read-only, click to copy)
Package Base: dlib
Description: A general purpose cross-platform C++ library designed using contract programming and modern C++ techniques
Upstream URL:
Keywords: algebra convolutional deep dlib learning linear machine networks neural
Licenses: custom
Submitter: pingplug
Maintainer: pingplug (swiftscythe, xantares)
Last Packager: xantares
Votes: 34
Popularity: 0.20
First Submitted: 2015-08-19 09:02
Last Updated: 2021-06-09 16:05

Latest Comments

1 2 3 4 Next › Last »

swiftscythe commented on 2021-01-17 15:15

@xantares, I don't have the rights to do that... but I can set it up in the following days :)

xantares commented on 2021-01-17 11:01

can you add me to the package maintainers, I'll try to set up the ENABLE_CUDA var

xantares commented on 2021-01-08 17:40

that would be cool

bartus commented on 2021-01-07 11:33

@swiftscythe: You can use env var like ENABLE_CUDA to gave users ability to control if build with or without cuda. I'm already doing this for some of my PKGBUILDs: e.g: blender, luxcorerender

xantares commented on 2021-01-06 12:35

could the dlib-cuda be moved to a separate PKGBUILD ?

this would avoid to install the huge cuda packages (4GB once installed) if we only use the regular dlib


swiftscythe commented on 2021-01-04 07:01

@Kicer, oops, I forgot to add the provides=(dlib) to dlib-cuda. Should be fine now.

Kicer commented on 2020-12-29 20:57

@swiftscythe then maybe this package should be split into two?

Kicer commented on 2020-12-29 11:51

I have installed dlib-cuda variant of this package. Then in another package I setup make dependency like this: makedepends=('dlib'). I would expect it will work with both dlib and dlib-cuda variants, but it does not. It explicitly demands dlib variant. Do I misunderstand something, or it simply won't work this way?

swiftscythe commented on 2020-12-15 06:03

@kailua, I completely agree with you. I guess if this was in the official repositories, it would make sense, because the packagers must generate all the packages in the PKGBUILD, but in the AUR it's probably not the best, since users without Nvidia graphics cards will have to install CUDA just to build the CPU-only version. I am for removing from the makedepends of the complete package as well, even if namcap is not happy about it. We have reasons.

kailua commented on 2020-12-11 11:41

@bartus and @swiftscythe I would rather not add cuda and cudann to makedepends for the complete package. It will install giga bytes of packages even if you are just building the split package without cuda.

Is there a better way to satisfy namcap?