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 application the developer must provide all the object files for their closed source code so that the new static version of livemedia can be linked in. Supporting this requirement is much simpler with a shared library and that's why most open source libraries support shared libraries.

With regards to your build system I'd for one would very much appreciate a more traditional system I've thought of doing it myself a few times, the one you've got is one of the strangest, least flexible, and prone to errors that I've every seen.

For instance your makefiles for windows can't produce running executable for dev studio 2008 and above (they don't add the manifests to the executable) and I don't think it is possible to fix this with your current make structure.

Honestly Ross I like livemedia, it does the job very well and you do a pretty good job supporting the community of users but for an open source project you've got some pretty strange idea's regarding project management.

Regards
Matt S.



On 12/8/2012 6:26 AM, Ross Finlayson wrote:
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" - and then using the exiting "genMakefiles" tool. So that's the approach that I would pursue first.

(And as for the suggestion of switching to using 'CMake', see <http://lists.live555.com/pipermail/live-devel/2012-July/015600.html>)

Personally, though, I don't particularly like shared libraries; in this day and age (with disk space and memory being so abundant) they're just more trouble than they're worth. (The only 'dynamic link' that I hope you put in Debian distributions is a 'link' to the URL "http://www.live555.com/liveMedia/";, so that people can download the latest version of the code; the only version that we support :-) But of course, you're welcome to try building shared libraries if you wish.

Ross Finlayson
Live Networks, Inc.
http://www.live555.com/



_______________________________________________
live-devel mailing list
live-devel@lists.live555.com
http://lists.live555.com/mailman/listinfo/live-devel

_______________________________________________
live-devel mailing list
live-devel@lists.live555.com
http://lists.live555.com/mailman/listinfo/live-devel

Reply via email to