On 03/09/2011 02:46 AM, Otavio Salvador wrote: > On Tue, Mar 8, 2011 at 20:54, Marc-André Moreau > <marcandre.mor...@gmail.com> wrote: >> I started a new library, called libfreerdputils, intended to be used for >> utilities. I have started it by moving the semaphore utils from xfreerdp to >> the library. This should help keeping our code clean and re-usable. I pushed >> it on master since it shouldn't break anything.
Can you clarify what should and shouldn't be in that library and which dependencies to and from this library are OK? > I fully agree about it however it would be nice if we keep it as a > static library to avoid needing to control so many ABI > compatilibities. This is a nightmare to be aware of possible ABI > breakage in many libraries and we need to keep in mind that other > applications will link against the dynamic libraries that we make > available. > > I vote to it to be a convenience library, by autotools definition. I don't agree. Yes, library versioning and stability is hard. So far we don't even try to handle it, but once we reach 1.0 we have to get the necessary processes in place and do it properly (IMHO). We already have 17 libraries and one extra do not _make_ a nightmare. I don't think making it a static library is an option, mainly for the same reasons as why static libraries generally isn't a good idea. It would be unnecesary waste of memory and cache if a xfreerdp process should contain the same code 17 times. The library might also end up encapsulating external libraries that needs initialization and are big (for example iconv). /Mads ------------------------------------------------------------------------------ Colocation vs. Managed Hosting A question and answer guide to determining the best fit for your organization - today and in the future. http://p.sf.net/sfu/internap-sfd2d _______________________________________________ Freerdp-devel mailing list Freerdp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freerdp-devel
