Package Details: kodi-git r67165.504c69cc3b2b-1

Git Clone URL: https://aur.archlinux.org/kodi-git.git (read-only, click to copy)
Package Base: kodi-git
Description: A software media player and entertainment hub for digital media (master branch, gles renderer)
Upstream URL: https://kodi.tv
Licenses: GPL2
Conflicts: kodi, kodi-gbm, kodi-gles, kodi-wayland, kodi-x11
Provides: kodi-common, kodi-gbm, kodi-wayland, kodi-x11
Submitter: BlackIkeEagle
Maintainer: graysky
Last Packager: graysky
Votes: 85
Popularity: 0.000672
First Submitted: 2014-10-23 06:38 (UTC)
Last Updated: 2024-12-08 16:30 (UTC)

Dependencies (105)

Required by (0)

Sources (9)

Pinned Comments

graysky commented on 2022-06-11 11:49 (UTC)

@laichiaheng - kodi is bound to a specific version of ffmpeg which is generally older than Arch's package. We avoid incompatibilities by using that specific version (ie internal ffmpeg). Recommend that you build kodi in clean chroot. See: https://wiki.archlinux.org/title/DeveloperWiki:Building_in_a_clean_chroot

I wrote a script that automates much of that called clean-chroot-manager offered here in the AUR.

Latest Comments

« First ‹ Previous 1 .. 34 35 36 37 38 39 40 41 42 43 44 .. 55 Next › Last »

graysky commented on 2012-10-18 19:58 (UTC)

checking for nfsc/libnfs.h... yes checking for libnfs soname... libnfs.so.1 checking afpfs-ng/libafpclient.h usability... yes checking afpfs-ng/libafpclient.h presence... yes checking for afpfs-ng/libafpclient.h... yes checking for libafpclient soname... libafpclient.so.0 checking plist/plist.h usability... yes checking plist/plist.h presence... yes checking for plist/plist.h... yes checking for libplist soname... libplist.so.1 checking shairport/shairport.h usability... no checking shairport/shairport.h presence... no checking for shairport/shairport.h... no configure: == Could not find libshairport. AirTunes support disabled. == checking shairport/ao.h usability... no checking shairport/ao.h presence... no checking for shairport/ao.h... no checking for UDEV... yes configure: == libusb disabled. == will not check for RPi support (unsupported cpu: i686) checking for CEC... no configure: error: == libcec disabled. CEC adapter support will not be available. == ==> ERROR: A failure occurred in build(). Aborting...

<deleted-account> commented on 2012-10-12 09:22 (UTC)

@Beretta92: the needed version of libcec changed (now it is >=2.0) and the packaged one is 1.9. Installing libcec-git from AUR should work (or disabling it as you did if not needed would work as well). Note for the ones trying to install libcec-git: if you receive an error while linking against liblockdev then you have to recompile lockdev package manually with -fPIC.

Beretta92 commented on 2012-10-11 22:59 (UTC)

looks like CEC is broken.. disable CEC works

dejavu commented on 2012-10-08 11:30 (UTC)

@BlackIkeEagle: It's nice that you are so motivated to provide us an uptodate PKGBUILD. But would it be possible to update the package only when you change something. For sure you can test the PKGBUILD locally. Thanks.

BlackIkeEagle commented on 2012-10-08 04:49 (UTC)

@gtmanfred: thx a lot for this input. this will come in handy when the new xorg stuff hits extra :)

gtmanfred commented on 2012-10-07 22:14 (UTC)

for people who are using testing, you need to install glu

BlackIkeEagle commented on 2012-10-04 20:38 (UTC)

@Beretta92: the latest pkgbuild has _commit, if you uncomment it and put your desired hashtag there it should do the trick

Beretta92 commented on 2012-10-04 15:05 (UTC)

thanks for the work blackeagle! but latest git is unusable for me looks like the library is broken, how do I go for compiling an older commit?

BlackIkeEagle commented on 2012-10-02 16:18 (UTC)

for me it is a confirmation the pkgbuild still works with the latest source

tuborg commented on 2012-10-02 11:53 (UTC)

Can I ask why you are updating the package version daily without changes to the PKGBUILD? I understand the source is from git, but every other package like that updates only when changes are made to the PKGBUILD. Otherwise it is up to the user to rebuild as needed.