[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: KDE ABI stability?
From:       Dan Kegel <dank () kegel ! com>
Date:       2005-12-05 5:39:43
Message-ID: a71bd89a0512042139t6874e47ap87bd0cbd434bb071 () mail ! gmail ! com
[Download RAW message or body]

On 12/4/05, Daniel Molkentin <molkentin@kde.org> wrote:
> Here we go: http://developer.kde.org/policies/compatpolicy.html

Looks pretty good.
Section 4 should note that gcc-3.4 through gcc-4.1 share
the same ABI (i.e. change gcc-4.0 to gcc-4.1).
You should probably include text like this:

The <a href="http://www.codesourcery.com/cxx-abi">standard C++ ABI</a>
was first implemented by
<a href="http://gcc.gnu.org/gcc-3.2/">gcc-3.2 (Aug 2002)</a>;
ABI conformance bugs were found, and gcc's ABI was changed for
<a href="http://gcc.gnu.org/gcc-3.3/">gcc-3.3 (May 2003)</a>
and <a href="http://gcc.gnu.org/gcc-3.4/">gcc-3.4 (Apr 2004)</a>
to comply with the standard.
gcc's libstdc++ also affects binary compatibility; see
<a href="http://gcc.gnu.org/onlinedocs/libstdc++/abi.html">gcc.gnu.org/onlinedocs/libstdc++/abi.html</a>

Section 5 has a partial sentence:
"Compiler flags may additionally lead to chang"

Section 6 needs to explain what 'make bcheck' does,
and who should use it when.

Also, since the LSB is an important way ABI compatibility
will be ensured in the future, you should probably mention
that KDE would like its libraries to be
included in the LSB (see
http://wiki.kde.org/tiki-index.php?page=LSB)
but that there are licensing issues with Qt which complicate this
(see http://www.linuxbase.org/futures/ideas/issues/libqt/)

Thanks!
- Dan

--
Why can't Johnny run Linux?  See http://kegel.com/linux/comfort
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]