[jitsi-dev] libx264 contained in jitsi-lgpl-dependencies-1.0-SNAPSHOT


#1

I am not a lawyer, but I believe that libx264 is not compatible with the
LGPL. Is there a jar without the offending binary content or a means to
compile the jar without libx264?

Regards,
Paul[image: jitsilgpl-nope.png]


#2

Huh ... yeah, hadn't thought about it. We will remove it next week. It's
not used by the bridge anyway.

···

On Fri, Jan 27, 2017 at 3:27 PM, Mondain <mondain@gmail.com> wrote:

I am not a lawyer, but I believe that libx264 is not compatible with the
LGPL. Is there a jar without the offending binary content or a means to
compile the jar without libx264?

Regards,
Paul[image: jitsilgpl-nope.png]

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

--
https://jitsi.org


#3

When and if the bridge supports h264, you guys might want to add OpenH264
instead, its BSD licensed.

···

On Fri, Jan 27, 2017 at 2:29 PM Emil Ivov <emcho@jitsi.org> wrote:

Huh ... yeah, hadn't thought about it. We will remove it next week. It's
not used by the bridge anyway.

On Fri, Jan 27, 2017 at 3:27 PM, Mondain <mondain@gmail.com> wrote:

I am not a lawyer, but I believe that libx264 is not compatible with the
LGPL. Is there a jar without the offending binary content or a means to
compile the jar without libx264?

Regards,
Paul[image: jitsilgpl-nope.png]

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

--
https://jitsi.org
_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev


#4

When and if the bridge supports h264, you guys might want to add OpenH264
instead, its BSD licensed.

We already do support H.264 and we still don't need any H.264 library
because we don't decode packets.

Emil

···

On Fri, Jan 27, 2017 at 4:32 PM, Mondain <mondain@gmail.com> wrote:

On Fri, Jan 27, 2017 at 2:29 PM Emil Ivov <emcho@jitsi.org> wrote:

Huh ... yeah, hadn't thought about it. We will remove it next week. It's
not used by the bridge anyway.

On Fri, Jan 27, 2017 at 3:27 PM, Mondain <mondain@gmail.com> wrote:

I am not a lawyer, but I believe that libx264 is not compatible with the
LGPL. Is there a jar without the offending binary content or a means to
compile the jar without libx264?

Regards,
Paul[image: jitsilgpl-nope.png]

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

--
https://jitsi.org
_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

--
https://jitsi.org


#5

That's fine of course, but the issue is actually with library itself being
included in a mis-labeled jar (lgpl vs gpl) and not including the GPL
License text. On the other hand, you can decode just fine with ffmpegs h264
decoder, but they don't include an encoder. Lastly, you may or may not be
aware that any graphs that are set up internally to fmj / libjitsi do
depacketize, decode, swscale, hflip, encode, and packetize as part of
normal operations. If the bridge is somehow not using the graph nodes at
all then that bit is moot.

Regards,
Paul

···

On Fri, Jan 27, 2017 at 2:38 PM Emil Ivov <emcho@jitsi.org> wrote:

On Fri, Jan 27, 2017 at 4:32 PM, Mondain <mondain@gmail.com> wrote:

When and if the bridge supports h264, you guys might want to add OpenH264
instead, its BSD licensed.

We already do support H.264 and we still don't need any H.264 library
because we don't decode packets.

Emil

On Fri, Jan 27, 2017 at 2:29 PM Emil Ivov <emcho@jitsi.org> wrote:

Huh ... yeah, hadn't thought about it. We will remove it next week. It's
not used by the bridge anyway.

On Fri, Jan 27, 2017 at 3:27 PM, Mondain <mondain@gmail.com> wrote:

I am not a lawyer, but I believe that libx264 is not compatible with the
LGPL. Is there a jar without the offending binary content or a means to
compile the jar without libx264?

Regards,
Paul[image: jitsilgpl-nope.png]

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

--
https://jitsi.org
_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

--
https://jitsi.org
_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev


#6

That's fine of course, but the issue is actually with library itself being
included in a mis-labeled jar (lgpl vs gpl) and not including the GPL
License text.

Yes, and that's why I already said in my previous post that we will be
removing it. You said we could use openh264 instead and I replied we don't
need to use anything instead because we don't need a codec at all.

On the other hand, you can decode just fine with ffmpegs h264 decoder,

Except that we don't need to.

but they don't include an encoder. Lastly, you may or may not be aware that

any graphs that are set up internally to fmj / libjitsi do depacketize,
decode, swscale, hflip, encode, and packetize as part of normal operations.

If the bridge is somehow not using the graph nodes at all then that bit is

moot.

Yes, it is, the bridge is not doing any of those things because it simply
resends the same rtp packets it received.

The few changes that we do on those packets are done in the transformer
chain.

Emil

···

On Fri, 27 Jan 2017 at 19:21, Mondain <mondain@gmail.com> wrote:

Regards,
Paul

On Fri, Jan 27, 2017 at 2:38 PM Emil Ivov <emcho@jitsi.org> wrote:

On Fri, Jan 27, 2017 at 4:32 PM, Mondain <mondain@gmail.com> wrote:

When and if the bridge supports h264, you guys might want to add OpenH264
instead, its BSD licensed.

We already do support H.264 and we still don't need any H.264 library
because we don't decode packets.

Emil

On Fri, Jan 27, 2017 at 2:29 PM Emil Ivov <emcho@jitsi.org> wrote:

Huh ... yeah, hadn't thought about it. We will remove it next week. It's
not used by the bridge anyway.

On Fri, Jan 27, 2017 at 3:27 PM, Mondain <mondain@gmail.com> wrote:

I am not a lawyer, but I believe that libx264 is not compatible with the
LGPL. Is there a jar without the offending binary content or a means to
compile the jar without libx264?

Regards,
Paul[image: jitsilgpl-nope.png]

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

--
https://jitsi.org
_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

--
https://jitsi.org
_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

--
sent from my mobile