Distributing Your Application

When distributing any application built against HOOPS Exchange or HOOPS Publish, you will need to distribute HOOPS binaries as well. In general you should deploy all HOOPS binaries excluding those that you have identified as unnecessary for your build.

For instance, if you provide users with U3D support you will want to distribute your application with u3dstep30.dll.

Please see the section for the platform you're interested in:


Distributing your application for Windows

On Windows, in order to run an application built against HOOPS Exchange, the execution environment must have the MSVC Redistributables for the following versions:

HOOPS Exchange and Publish on Windows is a modular distribution. Apart from mandatory core binaries, you may remove any unnecessary libraries for your deployment.

Whatever your distribution is, it should include all core binaries:

Resources

The resource folder is required for any application using HOOPS Publish. Moreover, the font file resource/Font/MyriadCAD.otf is used by both HOOPS Exchange and HOOPS Publish and thus is required.

C++ API

The C++ API is available through A3DLIBSCpp.dll. If you want to link against the API from a debug build, you may use A3DLIBSCppd.dll.

Multi-process loading

A3DHELF.dll is required for any multiprocess loading function. Multi-process loading is available through the A3DRWParamsGeneralData structure.

Parasolid

Readers

This list groups all binaries required for each reader:

*.TX Files

These files are required by DWG and Revit readers:

Revit needs additionnal files:

Writers

This list details which binaries are required for each writer:

TableToPDF

TableToPDF is a free add-on to HOOPS Publish, dedicated to the creation of tables in PDF documents.

TableToPDF uses third-party libraries that require LGPL conformance for distribution. TableToPDF can be downloaded from the TableToPDF download page. TableToPDF binaries have to be redistributed in the same folder as HOOPS Publish binaries.


Distributing your application for Linux

On Linux, HOOPS Exchange is distributed under one shared object file, libA3DLIBS-VERSION.so (and a symbolic link to it: libA3DLIBS.so).

The Linux distribution is provided in two versions, one version with support for DWG and Revit, and another version without support for DWG and Revit.

C++ API

The C++ API is available through libA3DLIBSCpp.so.

Multi-process loading

A3DHELF.so is required for any multiprocess loading function. Multi-process loading is available through the A3DRWParamsGeneralData structure. Please ensure the file attributes for A3DHELF.so are set with execute permission.

Parasolid

DWG and Revit

If you deploy the binaries with DWG and Revit support, you must include the following files:

Revit needs additionnal files:

TableToPDF

TableToPDF is a free add-on to HOOPS Publish, dedicated to the creation of tables in PDF documents.

TableToPDF uses third-party libraries that require LGPL conformance for distribution. TableToPDF can be downloaded from the TableToPDF download page. TableToPDF binaries must be redistributed in the same folder as HOOPS Publish binaries.


Distributing your application for macOS

On macOS, HOOPS Exchange is distributed in one dynamic library file, libA3DLIBS-VERSION.dylib (and a symbolic link to it: libA3DLIBS.dylib).

C++ API

The C++ API is available through libA3DLIBSCpp.dylib.


Distributing your application for Android

On Android, HOOPS Exchange is distributed in one dynamic library file, libA3DLIBS-VERSION.so (and a symbolic link to it: libA3DLIBS.so).

C++ API

The C++ API is available through libA3DLIBSCpp.so.


Distributing your application for iOS

HOOPS Exchange for iOS is provided as a static library. Thus no binary is required to be distributed with your application.

top_level:1