Header Files and Library Files
This section describes the API category and the header files and library files that the APIs depend on.
API Categories
The API names are prefixed with acl and in the format of acl+API category abbreviation+*. The asterisk (*) indicates the operation verb and object, both of which are capitalized. In this document, APIs are referred to as acl APIs.
In acl APIs, the parameters are usually arranged in the sequence of input parameters followed by output parameters. You should not add new parameters to the end of an API. Instead, you should add new parameters that are used only as input parameters before the output parameters. For parameters that are used as both input and output, the situation is relatively complex. You may need to consider the consistency with other APIs and handle the parameters flexibly.
API Prefix |
Description |
|---|---|
acl |
System configuration APIs |
aclrt |
Runtime management APIs |
aclop |
Single-operator model execution APIs |
aclblas |
BLAS APIs |
aclmdl |
Model inference APIs |
acldvpp, aclvdec, or aclvenc |
Media data processing APIs The naming conventions are not applicable to media data processing V2 APIs that start with hi_mpi. |
aclprof |
Profiling configuration APIs |
acltdt |
Data transfer APIs |
aclfv |
Feature vector search APIs |
Dependent Header Files and Library Files
You can reference the header files and library files of acl APIs for compiling and running your apps only after the firmware, driver, and CANN software are installed.
Include the dependency header files based on the acl APIs to be called. Refer to the table below for details.
The header files of acl APIs are stored in the ${INSTALL_DIR}/include/ directory, and the library files are stored in the ${INSTALL_DIR}/lib64/ directory. Replace ${INSTALL_DIR} with the CANN component directory. For example, if the installation is performed by the root user, the default file storage path is /usr/local/Ascend/cann.
When building code based on acl APIs, depend on the corresponding library files based on the included header files. If redundant library files (such as libascendcl.a) are referenced, version functions may be abnormal or there may be compatibility issues during a version update.