Package Details: python-dlib-cuda 19.24.6-1

Git Clone URL: https://aur.archlinux.org/python-dlib.git (read-only, click to copy)
Package Base: python-dlib
Description: Dlib is a general purpose cross-platform C++ library designed using contract programming and modern C++ techniques.
Upstream URL: http://www.dlib.net/
Licenses: boost
Conflicts: python-dlib
Provides: python-dlib
Submitter: u1bmoW1r16
Maintainer: petronny (AutoUpdateBot)
Last Packager: petronny
Votes: 16
Popularity: 0.25
First Submitted: 2016-10-27 15:05 (UTC)
Last Updated: 2024-08-10 03:07 (UTC)

Required by (6)

Sources (1)

Pinned Comments

petronny commented on 2024-03-30 13:11 (UTC) (edited on 2024-03-30 13:13 (UTC) by petronny)

Set _build_cpu and _build_cuda to 1 and 0 to build or not build the CPU or CUDA version.

If options=(!lto) has no effect, please check if it's still enabled in /etc/makepkg.conf.

petronny commented on 2023-11-28 04:57 (UTC)

Prebuilt binaries of this package can be found in arch4edu.

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 Next › Last »

Kicer commented on 2018-08-27 19:49 (UTC)

I think provides section should contain entry python-dlib=${pkgver} (version included). Otherwise pakages like python-face_recognition won't install due to insufficient version.

AbysmalBiscuit commented on 2018-07-21 09:17 (UTC)

@Kicer You are correct about gcc6 not being needed. In the past dlib and cuda programs did need gcc6 to compile properly, but it seems that is no longer the case.

@flipflop97 I have added the provides and conflicts.

@petronny I have gone through all the optional dependencies. Only sqlite and neon can be removed and python-dlib will still work. If any of the others are removed it will fail to import due to missing libraries of the shared object: dlib.cpython-36m-x86_64-linux-gnu.so. Note: removing sqlite will likely break parts of your system. :p

Kicer commented on 2018-07-19 20:19 (UTC)

Hi

Why is there gcc6 needed? I've modified PKBUILD to use system gcc and it works fine.

flipflop97 commented on 2018-07-04 19:50 (UTC) (edited on 2018-07-04 19:58 (UTC) by flipflop97)

Hi,

I have a package that depends on either python-dlib or python-dlib-cuda. I'd like to let it depend on either of them.

Right now both packages are totally separate. Can you maybe add a provides/conflicts/replaces rule for python-dlib so that both packages are treated as the same?

petronny commented on 2018-07-03 05:02 (UTC)

@accensi fixed.

accensi commented on 2018-07-03 04:55 (UTC)

Problems: - Even if just installing python-dlib, it is downloading all CUDA support - 1.4GB - Error (4/4) Updating the desktop file MIME type cache... ==> ERROR: python-dlib is not available for the 'x86_64' architecture. 2018-07-03 01:51:41,601 - wrappers - makepkg - ERROR - makepkg query makepkg -cf --noconfirm failed in directory ...../python-dlib

Kicer commented on 2018-07-01 16:10 (UTC)

@petronny, Hi, sorry, I've not noticed you are the new owner. I've been trying contact previous one before filling request.

petronny commented on 2018-07-01 13:13 (UTC)

@AbysmalBiscuit Thanks for your answers and I'm clear to my first question.

My second question, or the other questions are:

  1. If I build and install python-dlib with sqlite, then remove sqlite with pacman -Rdd sqlite, will python-dlib run?
  2. If I build and install python-dlib with lapack, then remove lapack with pacman -Rdd lapack, will python-dlib run?
  3. If I build and install python-dlib with libpng, then remove libpng with pacman -Rdd libpng, will python-dlib run?

etc.

petronny commented on 2018-07-01 13:09 (UTC)

@Kicer Hi I just took over this package and I will update it in a few days. Sorry for the delay but please leave comments to contact me before filing a request.

AbysmalBiscuit commented on 2018-06-28 08:15 (UTC)

@petronny Sorry for the delay in answering your questions.

  1. If you remove cuda or cudnn (since both are needed to compile and run dlib with cuda support) with pacman -Rdd cuda cudnn, python-dlib-cuda will not fallback to using only the cpu. In fact importing dlib will simply fail with an ImportError with not being able to open the shared object file(s) (either cuda or cudnn).

  2. I do not fully understand your question, I will assume that you are asking if it is possible to replace cuda with another dependency and still have be capable of using dlib in python. You cannot replace cuda with something else, or only with cudnn. You need both cuda and cudnn, hence why they are not only make dependencies, but also dependencies.

The dependency issue and the need to recompile if you would want to switch from having cuda support to using cpu only are likely the reason why python dlib was originally split into a cuda and non-cuda version.

If you have any other questions please don't hesitate to ask.

« First ‹ Previous 1 2 3 4 5 6 Next › Last »