You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It is sometimes useful to be able to change the version tag of a given symbol.
One good example of this use case is a recent breaking change in Qt6.
Older Qt6 versions used to export all symbols with the Qt_6 version tag which led to standard library instantiated symbols like std::string methods to be re-exported using the same tag.
Any executables that were linked with Qt could possibly end-up with the Qt_6 version tag for standard library symbols. Starting from 6.6 this is no longer the case and these symbols cannot be found although similar instantiations would be the same as long as the C++ standard library is backwards-compatible.
Patching such executables built with an older Qt6 version to change the tag to that of the standard library's would definitely be very helpful. There are no good alternatives for such cases.
The text was updated successfully, but these errors were encountered:
It is sometimes useful to be able to change the version tag of a given symbol.
One good example of this use case is a recent breaking change in Qt6.
Older Qt6 versions used to export all symbols with the
Qt_6
version tag which led to standard library instantiated symbols likestd::string
methods to be re-exported using the same tag.Any executables that were linked with Qt could possibly end-up with the
Qt_6
version tag for standard library symbols. Starting from 6.6 this is no longer the case and these symbols cannot be found although similar instantiations would be the same as long as the C++ standard library is backwards-compatible.Patching such executables built with an older Qt6 version to change the tag to that of the standard library's would definitely be very helpful. There are no good alternatives for such cases.
The text was updated successfully, but these errors were encountered: