On 1 May, Peter kovacs wrote:
> I think we do have the pain only with Linux. Since some distributions
> move slower then others.
>
> We could bundle the only 1.0.0 with Windows and Mac I think. For Linux
> we would need some logic, that identifies the right gstreamer
> available on the
Thanks for this info, Damjan. It would be very useful if we could identify
the Linux media player that would likely be used -- as DirectX is for WNT
and QuickTime for Mac. Maybe VLC? This would mean defining a new
AVMEDIA_MANAGER_SERVICE_NAME, right?
On Tue, May 1, 2018 at 6:51 AM, Damjan
In main/avmedia/source/inc/mediamisc.hxx, the media player is chosen with
the following code. Note how GStreamer is only used on non-Windows non-Mac
platforms.
#ifdef WNT
#define AVMEDIA_MANAGER_SERVICE_NAME
"com.sun.star.comp.avmedia.Manager_DirectX"
#define AVMEDIA_MANAGER_SERVICE_IS_JAVABASED
I think we do have the pain only with Linux. Since some distributions move
slower then others.
We could bundle the only 1.0.0 with Windows and Mac I think. For Linux we would
need some logic, that identifies the right gstreamer available on the
distribution.
Maybe we could even reduce the
So that would mean that our 'official' community builds would
not longer bundle/include it by default? Would we have 2 different
versions of the extension (0.10 and 1.0) or just one?
I like the idea, btw :)
> On Apr 26, 2018, at 1:14 AM, Peter Kovacs wrote:
>
> Does it make
On 04/25/2018 10:14 PM, Peter Kovacs wrote:
> Does it make sense to reorg the gstreamer module into an extention?
> We could then have multiple versions of it.
>
> I mean after all this is only a optional feature, thats important to
> some not all.
I think this idea is very good and deserves
Does it make sense to reorg the gstreamer module into an extention?
We could then have multiple versions of it.
I mean after all this is only a optional feature, thats important to
some not all.
On 25.04.2018 16:18, Jim Jagielski wrote:
I think this shows that we need to come to *some*
I think this shows that we need to come to *some* consensus on
how to handle the gstreamer stuff. Either we provide both CentOS6
and Ubuntu builds to our community or we fold in the proposed
gstreamer "work-around" which makes it a purely runtime
concern.
I would love to see how far we can go
On Mon, Apr 23, 2018 at 1:50 AM, Peter Kovacs
wrote:
> Does the build work without gstreamer activated?
>
Yes, without gstreamer as part of the my config, I can build without
issue.
>
> Am 23. April 2018 03:09:49 MESZ schrieb Kay Schenk :
> >On
On Sun, Apr 22, 2018, 15:47 Andrea Pescetti wrote:
> Matthias Seidel wrote:
> > Am 23.04.2018 um 00:15 schrieb Andrea Pescetti:
> >> Correct. Jim's builds (not only releases) are done with CentOS 6, so
> >> they will work on CentOS 6 too, and Kay can try with the latest link
Matthias Seidel wrote:
Am 23.04.2018 um 00:15 schrieb Andrea Pescetti:
Correct. Jim's builds (not only releases) are done with CentOS 6, so
they will work on CentOS 6 too, and Kay can try with the latest link
you gave. Only buildbots builds won't.
And that's the problem, even Jim's build won't
Am 23.04.2018 um 00:15 schrieb Andrea Pescetti:
> Matthias Seidel wrote:
>> I was under the impression that Jim built with CentOS 6
>
> Correct. Jim's builds (not only releases) are done with CentOS 6, so
> they will work on CentOS 6 too, and Kay can try with the latest link
> you gave. Only
Am 22.04.2018 um 21:57 schrieb Andrea Pescetti:
> Matthias Seidel wrote:
>> The problem may be that the buildbot is running on Ubuntu 14.04.
>> Normally we build releases on CentOS (5 for 4.1.x, 6 for 4.2.x).
>
> That's the issue indeed. CentOS 6 has glibc 2.12, Ubuntu 12.04 has
> 2.15, Ubuntu
Matthias Seidel wrote:
The problem may be that the buildbot is running on Ubuntu 14.04.
Normally we build releases on CentOS (5 for 4.1.x, 6 for 4.2.x).
That's the issue indeed. CentOS 6 has glibc 2.12, Ubuntu 12.04 has 2.15,
Ubuntu 14.04 has 2.19.
Your errors show that glibc >= 2.15 is
Hi Kay,
Am 21.04.2018 um 23:38 schrieb Kay Schenk:
>
> On 04/21/2018 10:40 AM, Matthias Seidel wrote:
>> Hi Kay,
>>
>> Am 21.04.2018 um 19:25 schrieb Kay Schenk:
>>> The latest output build I installed --
>>> rpm_en-US_2018-04-15_22_15_10_1829228
>> Assuming you downloaded from buildbot, can you
On 04/21/2018 10:40 AM, Matthias Seidel wrote:
> Hi Kay,
>
> Am 21.04.2018 um 19:25 schrieb Kay Schenk:
>> The latest output build I installed --
>> rpm_en-US_2018-04-15_22_15_10_1829228
>
> Assuming you downloaded from buildbot, can you try:
>
Hi Kay,
Am 21.04.2018 um 19:25 schrieb Kay Schenk:
> The latest output build I installed --
> rpm_en-US_2018-04-15_22_15_10_1829228
Assuming you downloaded from buildbot, can you try:
The latest output build I installed --
rpm_en-US_2018-04-15_22_15_10_1829228
on my 32-bit CentOS 6.9 is non-functioning. Errors attached.
--
--
MzK
"Less is MORE."
18 matches
Mail list logo