On Tue, 19 Apr 2022 at 09:00, Lisandro Damián Nicanor Pérez Meyer <perezme...@gmail.com> wrote: [snip] > > > The point of those private APIs is that they change at every new version, > > > so > > > you want to require rebuilding stuff built with private APIs of the wrong > > > version. If the symbol versioning does not ensure that, it is essentially > > > useless. > > > > Yes and that's very useful for Linux distributions. That patch should be > > upstreamed and enabled by default... but there should be an opt-out for > > developers. Those of us who recompile Qt often and do regression testing may > > need to run code across the version change boundaries without recompiling. > > ACK, I'll see what I can do.
The only patch I found is https://build.opensuse.org/package/view_file/KDE:Qt:6.2/qt6-base/0001-Tell-the-truth-about-private-API.patch?expand=1 which changes the symbol to have the full major.minor.patch version on it. That and the output of Thiago's eu-readelf makes me think something is wrong on my side, as the code seems to be there. -- Lisandro Damián Nicanor Pérez Meyer https://perezmeyer.com.ar/ _______________________________________________ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
