Considerations on using static / dynamic library for EPs?

[Harry-Chen]

I am currently doing some packaging work for onnxruntime in Debian. We noticed that both static and dynamic libraries exist for EPs.

For example, in 1.19.2, we have:

• static (onnxruntime_add_static_library): cpu, xnnpack, dml, azure, acl, nnapi, webnn, js, qnn, snpe, rknpu, armn, coreml, tvm
• dynamic (onnxruntime_add_shared_library_module): shared, dnnl, cuda, rocm, migraphx, openvino, cann, vitisai, tensorrt

I looked into some EP plugins, and found that the types of libraries are mostly decided when they were added.

I also notice the following description in documentation:

Add your provider in onnxruntime_providers.cmake. Build it as a static lib.

I would like to know:

• What are the considerations behind these choices?
• If the documentation recommends static libraries now, is there any plan to migrate dynamic plugins?