Re: Bundling exception for CMPlayer
Here a t least two possibilities:
- You could build using the upstream sources. This an accepted way in
a situation like this if there is no library.
- You could cooperate with upstream and make them release a library.
Miro: are you listening?
--alec
On 1/25/14, Ben Reedy <thebenj88(a)gmail.com> wrote:
On 25/01/14 23:34, Miro Hrončok wrote:
> So 25. leden 2014, 14:05:08 CET, Alec Leamas napsal:
>> That said, I
>> don't really think it changes my overall conclusion that a try to push
>> this upstream should be done.
>
> As a maintainer of mpv, I'd say the same thing.
>
> --
> Miro Hrončok
> --
> Phone: +420777974800
> IRC: mhroncok
My concern is that even if these changes are successfully pushed
upstream, CMPlayer will still not build without an included MPV source
tree.
Looking at the build-mpv script, MPV is first built and the resulting
object files are placed in an ar archive at ./build/lib/
libcmplayer_mpv.a, which is then used while building CMPlayer.
The CMPlayer developer mentioned this earlier, stating that this is
necessary as there is no libmpv shared library to link to while building.
--Ben