 |
ADTF
|
|
ADTF
|
With ADTF 3.21 we have extracted all UI content to 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 (if required for non-headless sessions).
If you have created sessions with ADTF <= 3.20, you have to adjust some paths in the system file because all plugins are now located within the bin (bin/debug) folder, also the examples.
The same for the extracted content to adtf_qt5 packge (if you are using UI components).
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.
If you make use of the ADTF Conan Generator, please also upgrade to v2.0++ which is compatible with the extracted CE package.
For ADTF itself we still deliver the runtime (adtf_runtime CMake module found in package adtf) and SDK (adtf_sdk CMake module found in package adtf_sdk) - use each for the related purpose.
We cleaned up the adtf_sdk package so that it no longer contains any adtf plugins. To generate plugindescriptions or to run integration tests, the adtf_runtime module is required by the adtf_sdk module. To ensure that both packages can be found, provide their locations via CMAKE_PREFIX_PATH.
find_package(ADTF) to find_package(adtf_sdk) and replace all instances of the CMake ADTF_DIR variable with either adtf_sdk_DIR or adtf_runtime_DIR.Please note that when consuming the adtf_sdk for developing own components via conan, the same versioned adtf package will be installed automatically.
If you only want to run (launch) ADTF sessions, you only require the adtf package (without any SDK components).
If you are implementing UI filter/services, you have to adapt your setup.
Due to extraction of the UI SDK to ADTF Qt5, the cmake call
will fail. Please remove the ui component and add following line instead after your find_package(adtf_sdk ... REQUIRED) call:
CMake will give you this advise as well, please also have a look at the migration guide of ADTF Qt5 package itself.
If you previously have used the cmake function adtf_convert_plugindescription_to_dox for creating a documentation page from the plugindescription, you have to adapt your call.
The function has been renamed to adtf_convert_plugindescription_to_md and only the DIRECTORY argument is valid, FILENAME has been removed because we are creating a markdown page for each component within a plugin.
You will also have to support to append additional content, written also in a markdown file.
The cmake call may look like this, for example:
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.
Since ADTF 3.24, we have split all our packages to single build types, to get ready for conan 2.x.
For that, we also remove the debug subfolder for our binaries, means each binary is shipped in the bin folder, for each build type package.
Furthmore, we fused all plugins into one single plugin adtf_core.adtfplugin.
The CE and session will automatically find this plugin and its components, there is no need of adding them (automatically) to the adtfsystem file, as long as the plugin path is provided by any used adtfenvironment file, the CE and Launcher will find them.
In case you have old sessions with old plugin path, you may receive warnings but it will still run. \ilinebr<br> To get rid of the warnings, you can easily remove fromadtfsystemfile (recommended within CE and its System Editor). \ilinebr<br> Foradtffileplugin`, it is the same behavior.
Note that if you keep using multi build type packages, it is still working without any restrictions.