If GStreamer is that problematic to obtain, we could import these 30
symbols that we use from it via run-time dynamic linking. That way we don't
need the GStreamer libraries to link against at compile time, only the
header files:
DF *UND*0060
Sorry I missed this thread earlier, and just noticed the pointer to it in a mail
today. (Being already subscribed to the list, the extra CC to get my attention
didn't work, maybe I need to adjust some of my filters).
I'll look into this tomorrow.
BTW, filing a ticket at
Damjan Jovanovic wrote:
GStreamer 1.0.0 requires glib 2.32.0.
CentOS 6 ships with glib (package name: glib2) 2.28 as per
http://mirror.centos.org/centos/6/os/x86_64/Packages/
So this is indeed an issue: we would need a distribution that ships with
glib >= 2.32 (without considering other
Martin Groenescheij wrote:
I forward your mail to the developers list:
Error message from Sourceforge: The
"/17102/39/dict-en-20..dict-en-20180301.oxt" file could not be found or
is not available. Please select another file.
This has already been discussed, for example, here (link to dev
GStreamer 1.0.0 requires glib 2.32.0.
Regards
Damjan
On Wed, Mar 14, 2018 at 8:27 PM, Andrea Pescetti
wrote:
> Jim Jagielski wrote:
>
>> Either we make gstreamer 1.0 an external download dependency,
>> so we can continue to build on CentOS6, or else we decide that
>> we
Jim Jagielski wrote:
Either we make gstreamer 1.0 an external download dependency,
so we can continue to build on CentOS6, or else we decide that
we switch to Ubuntu as our "official" build platform for our
community releases.
Can we define the problem better?
I assume the gstreamer license
I thought the "external download dependency" you were talking about, meant
distribution of GStreamer with an AOO release, which is not allowed.
Building against GStreamer header files, and then only linking to the
GStreamer libraries on the end user's system, if present, sounds allowed
("Can
On Wed, Mar 14, 2018 at 10:30 AM, Jim Jagielski wrote:
> Just a FYI that until we decide on this, 4.2.0-dev is in a holding
> pattern...
>
> Either we make gstreamer 1.0 an external download dependency,
> so we can continue to build on CentOS6, or else we decide that
> we switch
On Wed, 14 Mar 2018 13:30:06 -0400
Jim Jagielski wrote:
> Just a FYI that until we decide on this, 4.2.0-dev is in a holding
> pattern...
>
> Either we make gstreamer 1.0 an external download dependency,
> so we can continue to build on CentOS6, or else we decide that
> we
Just a FYI that until we decide on this, 4.2.0-dev is in a holding
pattern...
Either we make gstreamer 1.0 an external download dependency,
so we can continue to build on CentOS6, or else we decide that
we switch to Ubuntu as our "official" build platform for our
community releases.
> On Mar
All this was discussed in:
https://lists.apache.org/thread.html/83231a4ff938cdd14c19a01d4ae4f8d185ff7a94e0fc7d47a3b1b7f6@%3Cdev.openoffice.apache.org%3E
I don't recall you bringing all this up there.
> On Mar 14, 2018, at 12:03 PM, Damjan Jovanovic wrote:
>
> Why? The
Why? The licence for GStreamer is LGPL, which is Category X.
Damjan
On Wed, Mar 14, 2018 at 4:25 PM, Jim Jagielski wrote:
> I think there was general consensus to make gstreamer
> a external download dependency. As of this date, this
> has not yet been folded in. Who can
I think there was general consensus to make gstreamer
a external download dependency. As of this date, this
has not yet been folded in. Who can take point on that?
-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
I've gone ahead and make the AOO 4.2 Release Wiki page
for us to start working on it.
I propose to take HEAD of trunk and create a -dev developers
build for test and "review" by March 16th. I'll sign up for macOS
and Linux.
14 matches
Mail list logo