ADTF  3.18.2
License and Dependencies

For any licence information have a look at the LICENSE file within this package.

ADTF License

{#License}
====================================================================
Copyright @ 2023 VW Group. All rights reserved.
Third party copyrights are property of their respective owners.
This software is provided by the copyright holders and contributors
"as is" and any express or implied warranties, including, but not
limited to, the implied warranties of merchantability and fitness
for a particular purpose are disclaimed. In no event shall Digitalwerk
or contributors be liable for any direct, indirect, incidental,
special, exemplary, or consequential damages (including, but not
limited to, procurement of substitute goods or services; loss of
use, data, or profits; or business interruption) however caused
and on any theory of liability, whether in contract, strict
liability, or tort (including negligence or otherwise) arising in
any way out of the use of this software, even if advised of the
possibility of such damage.
YOU will be only allowed to install and use this software or part
of it if any additional License Agreement is concluded between
- YOU as LICENSEE -
and
- Digitalwerk GmbH
Im Gewerbepark C15
93059 Regensburg
http://www.digitalwerk.net
=> further mentioned as "Digitalwerk"
or
- any authorized DISTRIBUTOR for this product
=> DISTRIBUTOR authorization can be granted by Digitalwerk
By installing and using this software you will accept these additional
License Agreements.

Used Open Source Software

For creation of our artifacts we make use of several 3rd party content.

Build and Runtime Dependencies

Open Source Software we are very glad to use:

Libraries Version License Homepage Repository
adtf_file_library 0.12.0 MPL-2.0 link link
advanced_docking_system_for_qt 4.2.1 LGPL-2.1 link link
asio 1.28.0 BSL-1.0 link link
catch2 2.13.7 BSL-1.0 link link
clipp 1.2.3 MIT link link
dev_essential 1.3.3 MPL-2.0 link link
easy_profiler 1.3.0 MIT link link
fep_sdk_participant 3.1.0 MPL-2.0 link link
fep_sdk_system 3.1.0 MPL-2.0 link link
gtest 1.14.0 BSD-3-Clause link link
hexdump rel-20160408 MIT link link
libarchive 3.3.2 BSD-3-Clause link link
linenoise 1.0 BSD-2-Clause link link
nlohmann_json 3.11.2 MIT link link
openssl 1.1.1j OpenSSL link link
qqmlsortfilterproxymodel 0.1.1 MIT link link
qt 5.15.2 LGPL-3.0 link link
quazip 1.1 LGPL-2.1 link link
qwt 6.1.6 Qwt License Version 1.0 link link
rice_coder_decoder 1.2 Zlib link link
sdl LGPL-2.1 link link
xerces-c 3.3.2 Apache-2.0 link link
zlib 1.2.11 Zlib link link
Build Tools

Following build tools helps us to compile, document and package our delivery:

Build Tools Version License Homepage Repository
cmake 3.23.2 BSD-3-Clause link link
conan 1.61.0 MIT link link
doxygen 1.9.1 GPL-2.0 link link
doxyqml 0.5.0 BSD-2-Clause link link
graphviz 2.47.3 EPL-v10 link link
openjdk 1.8.0 GPL-2.0 link link
Note
For the result of the entire OSS approval please have a look at OSS Appendix.

RTI License Agreements

For the usage of RTI DDS as transport layer of our FEP integration, we have a license agreements with REAL-TIME INNOVATIONS, INC.

This means as long as you do not develop own RTI DDS dependent content and only make use of the delivered runtime binaries required for the FEP components, you do not need any additional licenses from RTI and are ready to use as delivered within ADTF by having a valid ADTF license.

Please find the agreement as follows:

====================================================================
REAL-TIME INNOVATIONS, INC.
LICENSE ACKNOWLEDGEMENT CERTIFICATE
====================================================================
between
Real-Time Innovations, Inc.
(RTI)
and
Digitalwerk GmbH
(You)
====================================================================
This License Acknowledgement Certificate (“LAC”) is subject to the
RTI Software License Agreement (SLA) #4000 (Rev03-21) (“SLA”).
These terms are available at https://www.rti.com/terms.
In case of conflict, the order of precedence is this LAC, and then the SLA.
Capitalized terms that are not defined herein are defined in the SLA.
If You have an SLA that does not define a Source License,
then You have no license for the source code to the
Software even if a Source license is listed above.
These Licenses are provided under the Developer Volume Project licensing model
and the following additional terms and conditions apply:
a. All Development using any component of the Software on the Project at the Site
must be licensed under the terms of the SLA.
b. You may use any number of OEM Runtime CPU Licenses during the Term of Your Developer Licenses
to sublicense that Target Application, provided that such Target Application does not contain
the v4.x nor the v3.x versions of RTI Connext DDS, RTI Data Distribution Service, or NDDS.
c. Users within the Project are charged only for Development.
Any number of Users within the Project may use the Software for purposes other than Development without charge.
d. You may not use the Software for Internal End Use.