Overview
View, explore and convert 3D CAD data on desktop, web and mobile
CAD Exchanger SDK The following section enumerates a list of redistributable dynamic libraries for CAD Exchanger SDK. For instance, CadExCore corresponds to CadExCore.dll on Windows, to libCadExCore.so on Linux and libCadExCore.dylib on MacOS.
Note that debug mode libraries (having d suffix, e.g. CadExCored.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 SDK libraries.
Required libraries for C#, Java and Python
The C#, Java and Python CAD Exchanger 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.
For example, if you use JT import in your application, you'd need:
- CadExJTNet.dll and CadExCoreNet.dll assemblies (CadExParaNet.dll is not needed);
- CadExJT, CadExPara, CadExCore, geom, tbb and tbmalloc native libraries.
Details
The following table enumerates dynamic library files must be redistributed depending on the required format:
Format or functionality | Required libraries |
---|---|
Common files |
|
3D PDF |
|
3D XML |
|
3DS (Windows only) |
|
3MF |
|
ACIS |
|
BRep |
|
CATIA |
|
Collada |
|
Creo |
|
DXF |
|
DWG |
|
FBX |
|
glTF |
|
IFC |
|
IGES |
|
INV |
|
JT |
|
NX |
|
OBJ |
|
Parasolid |
|
PLY |
|
PRC |
|
Revit |
|
Rhino |
|
Solid Edge |
|
SolidWorks |
|
STEP |
|
STL |
|
U3D |
|
USD |
|
VRML |
|
X3D |
|
Advanced geometry |
|
Computational meshers |
|
Visualization |
|
Unity |
|
UNIGINE | For single precision projects:
|
C3D plugin |
|