Currently, we're only building the wheel and installing the wheel for this package. This leads to the produced shared libraries being put in lib/python{VER}/site-packages/onnxruntime/capi which doesn't make them readily accessible to the typical build toolchain, especially if someone is looking to build a C++ library/application and use the C/C++ API of onnx runtime.
We should split this package into C/C++ and Python packages. The C/C++ package should include the shared libraries and headers and then the Python package should depend on said C/C++ package.
Comment:
Currently, we're only building the wheel and installing the wheel for this package. This leads to the produced shared libraries being put in
lib/python{VER}/site-packages/onnxruntime/capiwhich doesn't make them readily accessible to the typical build toolchain, especially if someone is looking to build a C++ library/application and use the C/C++ API of onnx runtime.We should split this package into C/C++ and Python packages. The C/C++ package should include the shared libraries and headers and then the Python package should depend on said C/C++ package.