| 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.001097 |
| First Submitted: | 2014-10-23 06:38 (UTC) |
| Last Updated: | 2024-11-23 20:01 (UTC) |
Is there a good reason not to switch to the gles render backend? Note that this enables HDR support now (at least on Intel platforms if using GBM and maybe wayland?), and the performance is also generally way better. I can't imagine there's many platforms that don't have gles2 support...
I just added: -DAPP_RENDER_SYSTEM=gles
Also your clean-chroot-manager script is really cool - I had a bunch of crappy bash scripts doing similar things but this is way nicer. Thanks!
@graysky Should I create the buildroot with distcc(What is this)?
Should I Nuke the buildroot and external repo (if defined)<---What is this?
@graysky It also fails when I use the internal FFmpeg.
https://forum.kodi.tv/showthread.php?tid=368574&pid=3101040#pid3101040
@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.
[ 19%] Built target windowing_X11 make: *** [Makefile:146：all] 錯誤 2 ==> 錯誤： build() 遭遇失敗。 正在中止... -> error making: kodi-git
It always fails to build without internal ffmpeg.
It's a split package just like the one in community. You want to install the -git flavors if you want the latest code. Bad idea to mix them.
Slightly confused here.
I've just built this and have in front of me four *.zst install files.
Is it the case that the independently available git packages eventclients, dev and texturepacker have been bundled in with the main kodi package?
I know I need eventclients. Do I need the dev and texturepacker files to run kodi as I did from the community repo?
Thank you for providing these packages.
@EndlessEden - try the latest commit
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.