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.000659
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 .. 39 40 41 42 43 44 45 46 47 48 49 .. 55 Next › Last »

graysky commented on 2012-01-22 21:21 (UTC)

@decaturguy - builds fine using bluez 4.98-1for me (i686)

graysky commented on 2012-01-22 21:12 (UTC)

Why is this flagged out-of-date

decaturguy commented on 2012-01-15 10:46 (UTC)

I use xbmc-pvr-git I had to downgrade bluez to 4.96-3. You can download it from Arch Rollback Machine http://arm.konnichi.com/2012/01/03/extra/os/ I hope it get fixed soon and don't forget to add bluez to IgnorePkg in /etc/pacman.conf

mrohnstock commented on 2012-01-14 19:06 (UTC)

Won't compile with bluez 4.98, too

<deleted-account> commented on 2012-01-14 17:03 (UTC)

Build was failing for me when I had Bluez 4.97 installed, I haven't tried it with 4.98 yet.

Huulivoide commented on 2012-01-05 15:18 (UTC)

But I still don't undestand why isin't the building of debugging symbols disabled, as those get removed anyhow.... as faar as I know one should put --disable-debug into the PKGBUILD, if debugging symbols defined to be built by default or just simply leave it away if the package doesn't build em unless told to.

donvla commented on 2012-01-02 09:10 (UTC)

BTW, here is my namcap output for this (20111226-1) package: http://pastebin.com/US4Zdrkm

donvla commented on 2012-01-02 09:05 (UTC)

@Huulivoide: Sometimes it works, sometimes it doesn't with external ffmpeg. You're on the safe side using xbmc's ffmpeg. You don't need the debug information inside the package once it is successfully built. @B: I´ll reverse the changes later this week. To get it right, only "glew" and "libxrandr" is still needed?

Huulivoide commented on 2012-01-02 01:15 (UTC)

It would aso seem to be working without problems on system ffmpeg....

Huulivoide commented on 2012-01-01 21:21 (UTC)

I don't see the logic of --enable-debug as debugging symbols are removed after packaging....

« First ‹ Previous 1 .. 39 40 41 42 43 44 45 46 47 48 49 .. 55 Next › Last »