<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 25/01/14 23:34, Miro Hrončok wrote:<br>
</div>
<blockquote cite="mid:52E3BD53.6000203@redhat.com" type="cite">So 25. leden 2014, 14:05:08 CET,
Alec Leamas napsal:
<br>
<blockquote type="cite">That said, I
<br>
don't really think it changes my overall conclusion that a try
to push
<br>
this upstream should be done.
<br>
</blockquote>
<br>
As a maintainer of mpv, I'd say the same thing.
<br>
<br>
--
<br>
Miro Hrončok
<br>
--
<br>
Phone: +420777974800
<br>
IRC: mhroncok
<br>
</blockquote>
My concern is that even if these changes are successfully pushed
upstream, CMPlayer will still not build without an included MPV
source tree.<br>
<br>
Looking at the build-mpv script, MPV is first built and the
resulting object files are placed in an ar archive at ./build/lib/
<meta name="qrichtext" content="1">
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px;
margin-right:0px; -qt-block-indent:0; text-indent:0px;"><!--StartFragment-->libcmplayer_mpv.a,
which is then used while building CMPlayer.<br>
</p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px;
margin-right:0px; -qt-block-indent:0; text-indent:0px;"><br>
The CMPlayer developer mentioned this earlier, stating that this
is necessary as there is no libmpv shared library to link to while
building.<br>
</p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px;
margin-right:0px; -qt-block-indent:0; text-indent:0px;"><br>
--Ben<br>
</p>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<style type="text/css">
p, li { white-space: pre-wrap; }
</style>
</body>
</html>