Am 03.06.2024 um 10:20 schrieb Volker Hilsheimer via Development:

On 3 Jun 2024, at 09:08, Phil Thompson via Development 
<development@qt-project.org> wrote:

In my code I call QAudio::convertVolume() (yet to migrate to the QtAudio 
namespace).  This compiles fine against Qt v6.7.0 and v6.7.1 (from the online 
installers). However...

Compiled against v6.7.0 the compiler generates a call to 
QtAudio::convertVolume(). The library contains symbols for both 
QAudio::convertVolume() and QtAudio::convertVolume().

Compiled against v6.7.1 the compiler generates a call to 
QAudio::convertVolume(). The library only contains a symbol for 
QAudio::convertVolume().

The result is that code compiled against v6.7.0 will not work with v6.7.1.

Thanks,
Phil

Hi Phil,

we indeed tried to be too clever for our own good with the rename of the QAudio 
namespace to QtAudio.

https://code.qt.io/cgit/qt/qtreleasenotes.git/about/qt/6.7.1/release-note.md

documents that Qt 6.7.1 breaks BC with 6.7.0 in order to restore 6.7.1 
compatibility with Qt 6.6, so you have to recompile against 6.7.1.


Volker


Hi,

but you really have to look for it. I read the old release notes, and the ones from the QtCreator, which still follows the "old style", I also read. But the Qt release notes I do not read anymore. You'd think that such a situation would be right on top, but the contrary:

> Qt 6.7.1 does not add any new functionality but provides
> bug fixes and other improvements and maintains both forward and backward
> compatibility (source and binary) with Qt 6.7.0.

Most likely automatically generated.

I know why you made the decision to change the release notes, but from that point on I can not use them. I have no intent to read git hashes and commit messages. Because commit messages and release notes have a different target audience (which may overlap).

Kind regards,
Björn.
--
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Reply via email to