Package Base Details: kodi-devel

Git Clone URL: https://aur.archlinux.org/kodi-devel.git (read-only)
Keywords: kodi kodi-devel
Submitter: alucryd
Maintainer: MarcinWieczorek (graysky)
Last Packager: graysky
Votes: 32
Popularity: 0.191236
First Submitted: 2014-08-11 23:33
Last Updated: 2019-06-12 21:29

Latest Comments

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

M-Reimer commented on 2018-07-21 11:34

This package definitively is missing the "fmt" make dependency.

I've tried on a clean build system and always get:

/home/build/builddir/kodi-pre-release/src/xbmc-18.0a2-Leia/xbmc/utils/StringUtils.h:41:10: fatal error: fmt/format.h: No such file or directory

#include <fmt/format.h>

^~~~~~~~~~~~~~ compilation terminated.

"fmt" is also a "make" dependency in the "kodi-devel" PKGBUILD here on AUR. It is enough to make it a "make" dependency as it seems to be a statically built library which is linked with the kodi binary.

graysky commented on 2018-07-11 19:31

@DSi - Builds fine in a clean chroot. The cmake step can get confused if your system has certain deps installed that aren't needed.

DSinapellido commented on 2018-07-11 16:32

[ 98%] Building CXX object CMakeFiles/kodi.dir/xbmc/platform/posix/main.cpp.o make[2]: No hay ninguna regla para construir el objetivo 'build/lib/libfmt.a', necesario para 'kodi-x11'. Alto. make[1]: [CMakeFiles/Makefile2:300: CMakeFiles/kodi.dir/all] Error 2 make: *** [Makefile:141: all] Error 2

It fails at 98% Transcription: «No hay ninguna regla para construir el objetivo...» - There is no rule to build the objective 'build/lib/libfmt.a', needed for kodi-x11. Stop.

graysky commented on 2018-06-22 19:19

@michaudg - Dunno what happened, fixed.

michaudg commented on 2018-06-22 00:16

18.0a2-1 - Integrity check fails on lib* files.

Thanks.

graysky commented on 2018-04-18 19:06

Updated in -13.

rpcameron commented on 2018-04-18 17:37

@graysky - Below find a diff with a few tweaks for the provides/conflicts. WRT chroot-building: Using makechrootpkg I was able to successfully build your package otherwise without issues. (The DeveloperWiki:Building in a Clean Chroot page on the wiki really ought to be linked from the main wiki somewhere in the PKGBUILD or makepkg pages, as I had to manually troll through the DeveloperWiki pages to find it ...)

diff --git a/PKGBUILD b/PKGBUILD
index [`24e6b28`](https://aur.archlinux.org/cgit/aur.git/commit/?h=kodi-pre-release&id=24e6b28)..9fd55b1 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -132,7 +132,7 @@ package_kodi-pre-release() {
     'upower: Display battery level'
   )
   provides=('xbmc' 'kodi')
-  conflicts=('xbmc' 'kodi' 'kodi-git' 'kodi-devel' 'kodi-devel-dev')
+  conflicts=('xbmc' 'kodi' 'kodi-git' 'kodi-devel')
   replaces=('xbmc')

   _components=(
@@ -214,7 +214,7 @@ package_kodi-dev-pre-release() {
   pkgdesc="Kodi dev files (pre-release versions)"
   depends=('kodi-pre-release')
   provides=('kodi-dev')
-  conflicts=('kodi-dev')
+  conflicts=('kodi-dev' 'kodi-devel-dev')

   _components=(
     'kodi-addon-dev'

graysky commented on 2018-04-16 22:13

@rpc - Is -12 correct wrt to provides/conflicts? I was confused about this previously (and perhaps presently too). If not, post a patch. Regarding the build problems you're having: build in a clean chroot. Don't use ccm. See the wiki. It works and is the recommended method of building/it is how all official Arch packages are built.

rpcameron commented on 2018-04-16 20:50

@graysky - re: -11, your "conflicts" array in the main package function still contains a -dev (kodi-devel-dev); also, you did not duplicate the conflicts array in the dev package function "conflicts=('kodi-dev' 'kodi-devel-dev')".

With regards to a clean chroot: I generally dislike building sources as root, and your tool requires such privileges to manage its chroot. The standard build tools ought to be enough to properly build any AUR PKGBUILD, and if the PKGBUILD relies upon such a tool, I consider it an error. I should be able to "git clone https://aur.archlinux.org/${PKGNAME} && cd ${PKGNAME} && makepkg -s" and find built packages without any extra user intervention excepting settings/variables that need to be (re-)defined in the PKGBUILD, or for dependencies found only in the AUR. I suppose I'll just maintain my own modified PKGBUILD until the package finds its way into the main repos.

graysky commented on 2018-04-16 19:56

@rpc - I understand now. Please review -11 to see that the provides= is correct. As to your build problems, please try clean-chroot-manager from the AUR. Build with it and you'll be fine.