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

Git Clone URL: https://aur.archlinux.org/kodi-git.git (read-only, click to copy)
Package Base: kodi-git
Description: Kodi Texturepacker tool (master branch)
Upstream URL: https://kodi.tv
Licenses: GPL2
Conflicts: kodi-tools-texturepacker
Provides: kodi-tools-texturepacker
Submitter: BlackIkeEagle
Maintainer: graysky
Last Packager: graysky
Votes: 85
Popularity: 0.000607
First Submitted: 2014-10-23 06:38 (UTC)
Last Updated: 2024-12-08 16:30 (UTC)

Dependencies (63)

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 .. 20 21 22 23 24 25 26 27 28 29 30 .. 55 Next › Last »

cgirard commented on 2014-08-18 09:42 (UTC)

CrystalHD support has been removed: https://github.com/xbmc/xbmc/pull/5105

morbidj commented on 2014-08-18 09:19 (UTC)

@BlackIkeEagle Sorry, Ill try to be a little more clear. Previously I would add " --enable crystalhd " at the bottom of the configure section of the PKGBUILD after it would build I could confirm it was working and also showed in xbmc settings under the acceleration menu. When I add the " --enable crystalhd " configuration to the PKGBUILD now it will build however framerates and the lack of Crystalhd showing in the video/acceleration menu of xbmc lead me to believe I have a problem. Here is a pastebin link http://pastebin.com/mZBZ61TE line #175 that would work in the past. I havent attempted to build with out the configuration option for crystalhd yet, are you saying it should just work out of the box?

BlackIkeEagle commented on 2014-08-18 05:31 (UTC)

@morbidj what do you mean ? it does no longer compile with libcrystalhd ? it should detect libcrystalhd automatically when you have installed it.

morbidj commented on 2014-08-17 23:13 (UTC)

@BlackIkeEagle was libcrystalhd support dropped from the master branch? If possible how can re-enable it my build? --enable crystalhd is no longer valid in build config?

BlackIkeEagle commented on 2014-08-16 07:17 (UTC)

updated dependencies, dropped systemd service, and libnfs patch seems no longer needed

BlackIkeEagle commented on 2014-08-08 09:41 (UTC)

The reason we will drop the xbmc.service file is because we have to change/add files which should not be under control of the xbmc package. I have added the 'display manager' method and the xbmc.service method to the wiki. So everyone is free to do with it what he/she wants.

Beretta92 commented on 2014-08-07 18:32 (UTC)

sad, it was a great feature.... Will stick with the Xwrapper.config solution for a while....

BlackIkeEagle commented on 2014-08-07 17:36 (UTC)

https://wiki.archlinux.org/index.php/Xbmc#Autostarting_at_boot xbmc.service will dissapear since it is no longer a viable option

adolchristin commented on 2014-08-07 15:38 (UTC)

To get this working again you can create a file called /etc/X11/Xwrapper.config with the contents "allowed_users=anybody" and that will allow the new X to be started as the xbmc user. ~/Builds/xbmc-git$ cat /etc/X11/Xwrapper.config allowed_users=anybody

justinkb commented on 2014-08-07 12:46 (UTC)

Any update on this? What is the cause of the problem with the xbmc.service anyway?