On Wed, Mar 9, 2011 at 10:15, Mads Kiilerich <m...@kiilerich.com> wrote:
>> 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.

More or less. What we need to support is the public API/ABI and the
plugins and like can be changed if it does not affect the used API/ABI
of the "public" library.

My concern is about exactly that. We are starting to delivery FreeRDP
on distributions (Debian, Gentoo, Ubuntu and so on) and I already had
to manage a breakage of Remmina on Debian due ABI changes.

Even not being on 1.0 version we need to handle soname bumps otherwise
every application linking to us will break.

So maybe we're near the time to review our libraries and see if those
are really required (as a matter of being public or not) and try to
reduce the amount of sonames to take care of.

> 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).

I see your point and I don't disagree however it mostly depends on how
we will use this library and what kind of code it will have.

I do think we ought to think seriously about it all and be
conservatibe about adding new libraries specially because we do need
to do a better job regarding maintaining ABI/API and handling sonames.
We have vendors (distributions) relying on it now.

-- 
Otavio Salvador                             O.S. Systems
E-mail: ota...@ossystems.com.br  http://www.ossystems.com.br
Mobile: +55 53 9981-7854              http://projetos.ossystems.com.br

------------------------------------------------------------------------------
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

Reply via email to