Package Details: libcava 0.10.2-1

Git Clone URL: https://aur.archlinux.org/libcava.git (read-only, click to copy)
Package Base: libcava
Description: Fork to provide cava as a shared library, e.g. used by waybar. Cava is not provided as executable.
Upstream URL: https://github.com/LukashonakV/cava
Keywords: cava libcava waybar
Licenses: MIT
Submitter: mutoroglin
Maintainer: mutoroglin
Last Packager: mutoroglin
Votes: 4
Popularity: 1.04
First Submitted: 2023-10-18 10:27 (UTC)
Last Updated: 2024-05-23 20:57 (UTC)

Latest Comments

wsduvall commented on 2024-05-22 22:38 (UTC)

@mutoroglin thank you, that fixed it for me! It seems that waybar-cava also works!

mutoroglin commented on 2024-05-22 08:10 (UTC)

Thank you for your note @wsduvall. The new version 4.2.2 of iniparser has its include structure modified. There is an upstream pull request pending to fix the issue: Fix build compilation errors with new iniparser 4.2.2 #18. I added a patch to fix the issue temporarily, please try if it works with you now. Please be aware that the same issue currently inhibits waybar-cava to run. So I am unsure if you're able to verify libcava atm. I will update waybar-cava as soon as an upstream solution is published.

wsduvall commented on 2024-05-21 23:10 (UTC) (edited on 2024-05-22 00:11 (UTC) by wsduvall)

I get the following error: 

Has header "iniparser.h" : NO
Has header "iniparser4/iniparser.h" : NO

meson.build:72:3: ERROR: Problem encountered: iniparser library is required

A full log can be found at /home/$USER/.cache/paru/clone/libcava/src/cava-0.10.1/build/meson-logs/meson-log.txt
==> ERROR: A failure occurred in build().
    Aborting...
error: failed to build 'libcava-0.10.1-1':

I did confirm that iniparser is installed and /usr/include/iniparser/iniparser.h exists...

mutoroglin commented on 2024-03-30 10:46 (UTC)

the build issue has been solved. Switching off the link time optimisation did the trick (see [SOLVED] Linker error when building via makepkg for details).

mutoroglin commented on 2024-03-09 08:00 (UTC)

@beatsgo & @lm41 thanks for your messages on this package; I experience the same issue as @beatsgo, the package doesn't build but I caninvoke it manually. I will work to solve it, please be a bit more patient. Thanks

beatsgo commented on 2024-02-27 03:18 (UTC)

  • 'ninja -C build' failing

    [19/19] Linking target libcava.so FAILED: libcava.so ... {standard input}: Assembler messages: {standard input}:11: Error: file not found: example_files/config {standard input}:31: Error: file not found: src/output/shaders/bar_spectrum.frag {standard input}:51: Error: file not found: src/output/shaders/northern_lights.frag {standard input}:71: Error: file not found: src/output/shaders/pass_through.vert make: *** [/tmp/ccgCo6KP.mk:2: /tmp/ccLMBjXP.ltrans0.ltrans.o] Error 1

  • For whatever reason, manually building it works allowing anyone to continue after this process.

MarsSeed commented on 2023-10-22 11:27 (UTC)

Thank you for your checking and verifying the non-conflicting nature of this lib package with the cava application. Cheers.

mutoroglin commented on 2023-10-22 09:00 (UTC)

@MarsSeed Even though the package can build the standard cava app this libcava package doesn't build and install that; that is deliberate to avoid the conflict with the cava package

Thanks for the hint, I removed libcava from the provides array :)

MarsSeed commented on 2023-10-22 07:45 (UTC)

+1: Please remove 'libcava' from provides: a package should not (double) declare its own name in its provides. :)

MarsSeed commented on 2023-10-22 07:44 (UTC) (edited on 2023-10-22 07:45 (UTC) by MarsSeed)

Does this conflict with cava? I suspect it does (haven't checked yet). Because the fork's readme says this also provides the cava application executable.

In case my suspicion turns out to be true, then this package should have 'cava' in provides & conflicts arrays.

Could you please kindly check to verify or refute this? Thanks in advance!