[Development] binary compatibility promise (was: Re: Frameworks on Mac?)

Peter Hartmann phartmann at rim.com
Fri Nov 23 11:07:01 CET 2012


On 11/23/2012 12:12 AM, André Pönitz wrote:
> (...)
> The reality is that this guarantee often enough does not hold in
> practice. Vendors of "binary" Qt based application typically test their
> setup against one specific (often enough patched) version of Qt which
> is then shipped with the application. Users are not expected to switch
> Qt versions, except when upgrading the whole application. Insofar are
> rules like "we can't add symbols in patch releases" not much more then
> self-inflicted pain without measurable gain.

This situation is different on mobile (and I guess embedded as well); 
for BlackBerry10 we have one version of Qt on the device and often 
cross-compile apps with another version of Qt; so we depend on the 
binary compatibility promise for patch releases (and in fact were bitten 
by the new symbols as well when people reported their app was not 
launching with "unknown symbol: _ZNK20QFutureInterfaceBase4refTEv" etc.).

Peter


>
>> Isn't it true that duplicate copies of Qt in every application will
>> result in duplicate copies being loaded into RAM too?
>
> Better double memory consumption then unexpected behaviour changes.
>
> Andre'
> _______________________________________________
> Development mailing list
> Development at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development
>


---------------------------------------------------------------------
This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.



More information about the Development mailing list