Package Base Details: kodi-devel

Git Clone URL: (read-only)
Keywords: kodi kodi-devel
Submitter: alucryd
Maintainer: MarcinWieczorek (graysky)
Last Packager: graysky
Votes: 32
Popularity: 0.157310
First Submitted: 2014-08-11 23:33
Last Updated: 2019-06-26 19:13

Latest Comments

« First ‹ Previous ... 5 6 7 8 9 10 11 12 13 14 15 ... Next › Last »

rpcameron commented on 2018-04-16 14:29

@graysky - I just attempted a fresh build of your pkgrel=10 version. I'm not sure how you're getting a clean build, as I removed my 'fmt' package, then attempted to build your PKGBUILD with a fresh/new directory root, and still have a no-go with libfmt.

Also, you may have added "provides=('kodi-dev')" to the kodi-dev package function, but you left the 'kodi-dev' in the provides array for the main package, as well as 'kodi-dev' and 'kodi-devel-dev' elements in the conflicts array of the main package, ensuring that your versions of the main and dev subpackages cannot be installed together.

graysky commented on 2018-04-15 23:59

@rpc - No, it builds fine as-is. Again, I direct you to doing so in a clean chroot. Also, bumped to -10 for the provides. Please review and comment.

rpcameron commented on 2018-04-15 23:48

@graysky - Actually, the first time was with an outdated PKGBUILD. However, while you added "provides=('kodi-dev')", you put it in the 'kodi' package function, not in the 'kodi-dev' package function.

Also, even when using "-DENABLE_INTERNAL_FMT=ON", it still won't properly build. Removing the line and using the 'fmt' package from AUR results it a successful build.

graysky commented on 2018-04-14 18:01

Perhaps you could add "provides=('kodi-dev')" to the package ... @rpcameron - See line 137 and the recent commit.

@rotgruen - I suspect you are building outside of a clean-chroot and the build is detecting some components on your host system. Build in a clean-chroot. Use clean-chroot-manager if you want.

rpcameron commented on 2018-04-14 17:24

@Rotgruen - There seems to be some problem with Kodi linking with its internal copy of libfmt. The build is setup to use Kodi's internal copy of libfmt (-DENABLE_INTERNAL_FMT=ON), but it still doesn't link properly. To fix this, install fmt from AUR, and remove that line from the build() function.

@graysky - Perhaps you could add "provides=('kodi-dev')" to the package_kodi-dev-pre-release() function, so that other packages will recognize it. Building things like kodi-platform-git and kodi-addon-pvr-* will otherwise try to pull in kodi-dev from 17.6 instead of realizing these files are already present.

graysky commented on 2018-04-14 10:56

On Arch-Linux, building always terminates with the error message: No rule to make target 'build/lib/libfmt.a', needed by 'kodi-x11'.

Did you modify the PKGBUILD in any way? Builds fine for me.

Rotgruen commented on 2018-04-14 08:05

On Arch-Linux, building always terminates with the error message: No rule to make target 'build/lib/libfmt.a', needed by 'kodi-x11'.

graysky commented on 2018-03-25 23:31

@Basxto - Wish granted, long live jambi.

Basxto commented on 2018-03-25 22:50

Please add provides=('kodi-dev')

That will make it easier to install and

graysky commented on 2018-03-11 11:42

Again, I am unfamiliar with the addon. I adapted the PR package based on what Ike is providing in community. If that inputsteam was included in the past, I dunno why it's not in 18 without some digging.