Migration from ADTF <= 3.20

Splitted packages / adtfenvironment

With ADTF 3.21 we have extracted all UI content to this ADTF Qt5 package (v1.0++) and the CE itself to a standalone ADTF Configuration Editor package (v2.0++).
Please have a look at both deliveries which adaptions are required to use their components.
The CE will assist you to create an adtfenvironment where you can include adtf and adtf_qt5.

Plugin Paths

If you have created sessions with ADTF <= 3.20, you have to adjust some paths in the system file because all UI related plugins now have a different environment macro (ADTF_QT5_DIR vs ADTF_DIR).
The CE will assist you for clean up, just open the System Editor and perform a remove all / look up in the Plugins section (Release / Debug).
Check the Validation Protocol in the CE if there are remaining warnings / errors.

Conan Generator

If you make use of the ADTF Conan Generator, please also upgrade to v2.0++ which is compatible with the extracted CE package.

UI SDK

For developing UI filters/services, make sure to find the UI SDK extracted from ADTF to this delivery.
Therefore, the ADTF Qt5 package has been split into adtf_qt5 (runtime package) and adtf_qt5_sdk (developer package) That means, for developing an UI service, simply add

find_package(adtf_sdk COMPONENTS systemsdk REQUIRED)

find_package(adtf_qt5_sdk COMPONENTS adtfui REQUIRED) # or find_package(adtfui REQUIRED)

after your find_package call for the ADTF System SDK.

The same you have to add for UI filter development:

find_package(adtf_sdk COMPONENTS filtersdk REQUIRED)

find_package(adtf_qt5_sdk COMPONENTS adtfui REQUIRED) # or find_package(adtfui REQUIRED)

Finally

That's it! As always, you can still use and load already compiled plugins, no recompilation is required, but may help to unlock new features.

Table of Contents

Migration from ADTF <= 3.20