ASCEND_CUSTOM_OPP_PATH
Description
Installation path of the custom operator package. After this path is configured in the scenario where the operator is inserted into the graph, the GE framework searches for the operator binary file based on the environment variable and uses it during graph build and execution. Multiple paths can be configured, which are separated using colons (:).
The following custom operator compilation modes and path configurations are supported:
- Custom operator package: The operator is compiled into a custom operator package and installed in a specified path. (This environment variable does not need to be configured if the default path is used.) Set this environment variable to the installation path of the operator package.
- Dynamic library: When the operator is compiled into a dynamic library, you need to configure the installation path of the dynamic library. In this case, you can also use the dynamic library in dynamic library link mode. The dynamic library link mode has a higher priority than the environment variable configuration mode.
If the dynamic library compilation and custom operator package compilation functions are used at the same time, the dynamic library generated by the former has a higher priority.
Example
In the following example, <path1> and <path3> are the operator package installation directories specified by developers, and <path2> and <path4> are the directories for storing the dynamic library compilation products. The priority order of the compilation products is 2 > 4 > 1 > 3.
export ASCEND_CUSTOM_OPP_PATH=<path1>/vendors/vendor_name1:<path2>/op_api/lib/:<path3>/vendors/vendor_name3:<path4>/op_api/lib/
Restrictions
None