Package Details: chromaprint-fftw 1.4.3-5

Git Clone URL: (read-only)
Package Base: chromaprint-fftw
Description: Extracts fingerprints from any audio source (uses fftw for FFT calculations instead of ffmpeg)
Upstream URL:
Keywords: chromaprint fftw
Licenses: GPL
Conflicts: chromaprint
Provides: chromaprint
Submitter: dbermond
Maintainer: dbermond
Last Packager: dbermond
Votes: 40
Popularity: 1.086954
First Submitted: 2015-12-27 19:32
Last Updated: 2019-07-15 01:56

Dependencies (3)

Required by (47)

Sources (1)

Latest Comments

1 2 Next › Last »

dbermond commented on 2018-11-09 04:12

@Jat fixed

Jat commented on 2018-11-09 02:42

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

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.

hrko commented on 2017-06-07 13:55


This package should contain the fpcalc by default. Not including the fpcalc is not a problem for an application which depends on the chromaprint-fftw, but it will be a problem for one which depends on the chromaprint, which has the fpcalc. In some cases, the both package are depended by the installed packages, so the modified package should have the same files with the original package.

dbermond commented on 2016-12-06 21:12

Thanks for the participation and talking. :)

Anonymous comment on 2016-12-06 20:53

I understand.
Thanks for taking time to investigate and explaining.

dbermond commented on 2016-12-06 20:31

I wasn't aware that fpcalc was built in examples. In versions prior to 1.4 it was impossible to build the fpcalc utility with normal CMake options and make NOT being linked against ffmpeg libraries. This new version 1.4 addresses this and now the ffmpeg libraries linkage goes only to fpcalc. I have updated the package and added instructions on top of PKGBUILD file. Please see the implications that I have mentioned, which are the reason that I don't have enabled it since this package is free of ffmpeg dependency.

Anonymous comment on 2016-12-06 20:20

Yep, in fact this is the same program.
fpcalc was the only "example" build with BUILD_EXAMPLES !

dbermond commented on 2016-12-06 20:17

'BUILD_TOOLS' option is for enabling the command line utility fpcalc. It does not create or enable any examples.
As far as I could see, the examples building was removed from upstream. CMakeLists.txt doesn't list anything related to it anymore.

This is the CMake variable description for 'BUILD_TOOLS':
// Build command line tools

Anonymous comment on 2016-12-06 19:00

I didn't see that upstream released a new version !
It seems to be "-DBUILD_TOOLS=ON" now (just checked :) ).
Thank you !