Package Details: kodi-addon-inputstream-adaptive-18-git 2.3.13.r3.gf782dcc-1

Git Clone URL: https://aur.archlinux.org/kodi-addon-inputstream-adaptive-18-git.git (read-only)
Package Base: kodi-addon-inputstream-adaptive-18-git
Description: InputStream client for adaptive streams for Kodi 18
Upstream URL: https://github.com/peak3d/inputstream.adaptive
Licenses: GPL2
Conflicts: kodi-addon-inputstream-adaptive-18
Provides: kodi-addon-inputstream-adaptive-18
Submitter: Niklas
Maintainer: None
Last Packager: Niklas
Votes: 5
Popularity: 0.213831
First Submitted: 2018-03-20 20:11
Last Updated: 2019-02-08 18:43

Latest Comments

1 2 Next › Last »

Niklas commented on 2019-02-08 20:12

@fotoniker: not necessary since good AUR helpers should give you the option to choose between e.g. kodi-git and kodi-devel

XavierCLL commented on 2019-01-30 19:10

missing a dot "." at the end of the cmake line

Rotgruen commented on 2019-01-29 22:25

When trying to install the package I get the following error message: "no source or binary directory provided". I have installed kodi-devel in advance

fotoniker commented on 2019-01-15 17:07

please add 'kodi-devel' to the depends, thanks.

knappster commented on 2018-10-27 10:57

It looks like the colorspace code coincides with changes that were made to Kodi 18 beta 4. I am able to build inputstream 2.3.3 once beta 4 is installed (but not when beta 3 was)

Hagar commented on 2018-10-15 08:06

2.2.28 from 8 days ago does build.

Hagar commented on 2018-10-15 07:24

I am unable to build after colorspace additions.

src/kodi-addon-inputstream-adaptive-18-git/src/main.cpp

error: ‘struct INPUTSTREAM_INFO’ has no member named ‘m_codecFourCC’

error: ‘struct INPUTSTREAM_INFO’ has no member named ‘m_colorSpace’

error: ‘COLORSPACE_UNKNOWN’ is not a member of ‘INPUTSTREAM_INFO’

error: ‘struct INPUTSTREAM_INFO’ has no member named ‘m_colorRange’

error: ‘COLORRANGE_UNKNOWN’ is not a member of ‘INPUTSTREAM_INFO’

Any Suggestions ?

Niklas commented on 2018-09-13 15:22

oh sorry

tadly commented on 2018-09-13 15:14

I might as well explain the issue.
With your source you are telling makepkg to clone the repository into the gitsrc directory.
Later on, in the pkgver, build and package functions, you're navigation to "${srcdir}/${pkgname}" which obviously doesn't exist.

tadly commented on 2018-09-13 15:11

I'm pretty sure it doesn't because it can't work the way it is.
I guess whatever you are testing is hitting a cache :)