Package Details: chromaprint-fftw 1.5.1-4

Git Clone URL: https://aur.archlinux.org/chromaprint-fftw.git (read-only, click to copy)
Package Base: chromaprint-fftw
Description: Library for extracting fingerprints from any audio source (uses fftw for FFT calculations instead of ffmpeg)
Upstream URL: https://acoustid.org/chromaprint
Keywords: chromaprint fftw
Licenses: GPL-2.0-or-later
Conflicts: chromaprint
Provides: chromaprint, libchromaprint.so
Submitter: dbermond
Maintainer: dbermond
Last Packager: dbermond
Votes: 61
Popularity: 0.71
First Submitted: 2015-12-27 19:32 (UTC)
Last Updated: 2025-04-03 19:45 (UTC)

Required by (79)

Sources (4)

Latest Comments

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

dbermond commented on 2020-06-19 17:07 (UTC)

@serrana It is building fine for me. Are you using Arch Linux or an Arch derivative?

serrana commented on 2020-06-19 12:35 (UTC)

Mine has build error, the file gtest-all.cc is not found. If change DGTEST_SOURCE_DIR:PATH from '/usr/src/googletest' to '/usr/src/gtest' it's building ok. And with package gtest-py3, only work with the value '/usr/src/googletest/googletest'. In other words, users may have to search gtest path and adjust according.

dbermond commented on 2020-06-12 23:36 (UTC)

@mjuarezm Reproduced. I've pushed a fix and now it's building fine.

mjuarezm commented on 2020-06-12 21:57 (UTC)

I'm having the same problem as @cookiecaper. Building in a clean chroot also fails for me.

dbermond commented on 2019-09-13 03:04 (UTC)

@cookiecaper Package is building fine at the current state. Try to use @adsun suggestion and build and a clean chroot.

adsun commented on 2019-09-12 21:05 (UTC)

@cookiecaper this builds fine for me in a clean chroot. Does it work for you using a clean chroot?

cookiecaper commented on 2019-09-12 20:51 (UTC)

Not building for me -- some error with gtest not initializing correctly it looks like. I took the mainline chromaprint PKGBUILD and manually added the FFT_LIB option, swapped the dependency on ffmpeg for fftw, and added the conflicts/provides options and things work that way. Would appreciate an update. :)

dbermond commented on 2018-11-09 04:12 (UTC)

@Jat fixed

Jat commented on 2018-11-09 02:42 (UTC)

CMake Error at /usr/share/cmake-3.12/Modules/FindPackageHandleStandardArgs.cmake:137 (message): Could NOT find GTest (missing: GTEST_SOURCE_DIR GTEST_INCLUDE_DIR) Call Stack (most recent call first): /usr/share/cmake-3.12/Modules/FindPackageHandleStandardArgs.cmake:378 (_FPHSA_FAILURE_MESSAGE) cmake/modules/FindGTest.cmake:75 (find_package_handle_standard_args) tests/CMakeLists.txt:1 (find_package)

Please add gtest to makedepends, thanks.

dbermond commented on 2017-07-16 03:53 (UTC)

@ootaharuki99 Thank you for sharing your thoughts. I understand your point, and it really is valid. But I'm doing this to avoid a circular dependency between chromaprint-fftw and ffmpeg packages that need chromaprint. There is a note about this at the top of PKGBUILD file. Circular dependency between AUR packages can be a pain and I tend to avoid them as much as I can. Since chromaprint-fftw was designed mainly to compile ffmpeg-full-git/ffmpeg-full with chromaprint support, it seems a good idea to avoid this circular dependency.

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