I noticed a incompatibility with the latest Qt 6.5.6 and Qt Map SDK 200.4.
When compiling my application with CMake I get the following linker error:
/usr/bin/ld: /home/user/Development/arcgis/maps_sdk/qt200.4.0/sdk/linux/x64/lib/libEsriCommonQt.so: undefined reference to `QFutureInterfaceBase::setContinuation(std::function<void (QFutureInterfaceBase const&)>, QFutureInterfaceBasePrivate*)@Qt_6_PRIVATE_API'
collect2: error: ld returned 1 exit status
ninja: build stopped: subcommand failed.
Downgrading to Qt 6.5.5 seems to workaround this issue.
Solved! Go to Solution.
Hi @HunterMorganBell. Thanks for reaching out with this info.
Unfortunately this is an ABI break in the Qt framework itself. We noted this in our previous release notes here: https://developers.arcgis.com/qt/release-notes/prior-releases/release-notes-for-200-3/#known-issues
To address this in our upcoming release we are moving up our builds to use Qt 6.5.6 minimum which addressed the issue.
In the meantime, hopefully you are able to use 6.5.5 for your development. Apologies for this, but it should be sorted out with our 200.5 release, which should available in a few months.
Hi @HunterMorganBell. Thanks for reaching out with this info.
Unfortunately this is an ABI break in the Qt framework itself. We noted this in our previous release notes here: https://developers.arcgis.com/qt/release-notes/prior-releases/release-notes-for-200-3/#known-issues
To address this in our upcoming release we are moving up our builds to use Qt 6.5.6 minimum which addressed the issue.
In the meantime, hopefully you are able to use 6.5.5 for your development. Apologies for this, but it should be sorted out with our 200.5 release, which should available in a few months.
So should the required version in https://developers.arcgis.com/qt/system-requirements/system-requirements-for-200-4/#:~:text=Framewor... be updated to be "6.5.1 to 6.5.5" ?
Hi @TroyFoster. No, it is still 6.5.1, but unfortunately the ABI break forces us into some strange Qt combinations. Our 200.4.0 minimum is still technically Qt 6.5.1, and everything works up to 6.5.5, but not with 6.5.6. That story changes next release when 6.5.6 becomes our minimum.
The story is more complicated with newer versions of Qt 6.6.x and beyond, but that will be sorted out next release as well. Currently 200.4.0 is restricted from Qt upgrades in 6.6 and 6.7 until next release.
I should add that all of these restrictions only apply to Linux and Android.