The following section enumerates a list of redistributable dynamic libraries for MTK. For instance, CadExMTK corresponds to CadExMTK.dll on Windows, to libCadExMTK.so on Linux and libCadExMTK.dylib on MacOS.
Note that debug mode libraries (having d suffix, e.g. CadExMTKd.dll) as well as header files (*.hxx) may not be redistributed.
To ensure that you re-distribute all required dynamic libraries, you can use tools like Depends.exe
on Windows, or ldd
on Linux specifying the library of your application that is linked with any of the MTK libraries.
The C#, Java and Python MTK libraries act as wrappers for the functionality contained in the native libraries. For your application to function correctly you need to use those .NET assemblies, Java JARs and Python modules, classes from which you use in your code, plus all the native libraries required by the utilized components. The transitive dependencies listed in the table below apply only to native libraries, not .NET assemblies, Java JARs and Python modules.
The following table enumerates dynamic library files must be redistributed:
Functionality | Required libraries |
---|---|
Common files |
|
Manufacturing Toolkit |
|