> I have found the forked Live456 project on GitHub that adds support for
> shared libraries, but which has had no changes for the last 2 years. If I
> were to port this support back to the Live555 codebase, what would the
> chances be of this work being accepted upstream and what would the acce
Greetings.
We are currently exploring the possibility of using Live555 in a product
consisting of a proprietary code base, that must run on both Windows and Linux.
In order to comply with the LGPL, but not have to release our entire codebase,
we must build Live555 as shared libraries. Currently
> Am Sonntag, den 23.12.2012, 16:40 +1000 schrieb Ross Finlayson:
>>> Spaces are used instead of the required tabs in the install target
>>
>> Oops - fixed now. (I understand why many people hate Makefiles :-)
>
> It's still not fixed in 2012.12.23
Argh! Brain fart! It's fixed for real now.
Am Sonntag, den 23.12.2012, 16:40 +1000 schrieb Ross Finlayson:
> > Spaces are used instead of the required tabs in the install target
>
> Oops - fixed now. (I understand why many people hate Makefiles :-)
It's still not fixed in 2012.12.23 and I actually like Makefiles.
--
Benjamin Drung
Debi
> Spaces are used instead of the required tabs in the install target
Oops - fixed now. (I understand why many people hate Makefiles :-)
Ross.
___
live-devel mailing list
live-devel@lists.live555.com
http://lists.live555.com/mailman/listinfo/l
Am Samstag, den 22.12.2012, 12:51 +1000 schrieb Ross Finlayson:
> > Thanks. The install target for the base Makefile is missing
>
>
> Oops - my mistake. I've just installed a new version of the code that
> fixes this (and also adds your proposed "distclean:" target).
Spaces are used instead of
> Thanks. The install target for the base Makefile is missing
Oops - my mistake. I've just installed a new version of the code that fixes
this (and also adds your proposed "distclean:" target).
> It would be a good idea to add a pkg-config file for the shared libraries.
I don't know what a "p
Am Freitag, den 21.12.2012, 15:55 +1000 schrieb Ross Finlayson:
> > 1) We need symbolic links on Linux for shared libraries. For
> > example,
> > libfoo.so.1.2.3 would required these symlinks:
> >
> > libfoo.so.1 -> libfoo.so.1.2.3
> > libfoo.so -> libfoo.so.1.2.3
> >
> > libfoo.so.1.2.3 and libf
> 1) We need symbolic links on Linux for shared libraries. For example,
> libfoo.so.1.2.3 would required these symlinks:
>
> libfoo.so.1 -> libfoo.so.1.2.3
> libfoo.so -> libfoo.so.1.2.3
>
> libfoo.so.1.2.3 and libfoo.so.1 will be shipped in the library package
> and libfoo.so will be shipped in
Am Samstag, den 15.12.2012, 17:37 +1000 schrieb Ross Finlayson:
> Benjamin,
>
>
> I've now installed a new release - 2012.12.15 - that adds a new
> configuration file "config.linux-with-shared-libraries".
Thanks.
> Please verify that this works properly for you (i.e., after first
> running "ge
Benjamin,
I've now installed a new release - 2012.12.15 - that adds a new configuration
file "config.linux-with-shared-libraries". Please verify that this works
properly for you (i.e., after first running "genMakefiles
linux-with-shared-libraries"). (Unfortunately I'm traveling for the rest
Am Samstag, den 08.12.2012, 19:31 -0800 schrieb Ross Finlayson:
> > > I'm not planning any changes to the 'build system' itself. I
> > > would
> > > hope, however, that things like shared libraries could be
> > > accommodated
> > > by using a different "config.*" file - e.g., perhaps named
> > > s
>> I'm not planning any changes to the 'build system' itself. I would
>> hope, however, that things like shared libraries could be accommodated
>> by using a different "config.*" file - e.g., perhaps named something
>> like "config.linux-with-shared-libraries" or
>> "config.debian-with-shared-libr
Am Samstag, den 08.12.2012, 06:26 -0800 schrieb Ross Finlayson:
> I'm not planning any changes to the 'build system' itself. I would
> hope, however, that things like shared libraries could be accommodated
> by using a different "config.*" file - e.g., perhaps named something
> like "config.linux-
There is one really good reason to support shared libraries and that is
to make it easier to full fill the obligations of the LGPL.
The way it is now if you have a closed source application using this
library and someone else wants to build thier own version of liveMedia
to use with your applica
I'm not planning any changes to the 'build system' itself. I would hope,
however, that things like shared libraries could be accommodated by using a
different "config.*" file - e.g., perhaps named something like
"config.linux-with-shared-libraries" or "config.debian-with-shared-libraries" -
an
Hi,
we like to have a shared library of liblivemedia in Debian and Ubuntu
[1]. This requires two things: First adjust the build system to create a
shared library and second take care of proper SONAME, ABI/API changes
management.
I would be willing to help changing the build system to create a sha
17 matches
Mail list logo
