[onert] Introduce ONE Runtime Python binding

[KangInyeong]

What

Let's support NNFW Python API.

Why

• ONE provides APIs for efficient AI development across multiple hardware and software platforms.
• However, ONE APIs are written in the C/C++ language, so this makes high barriers to start to develop.
• NNFW API is one of APIs provided from ONE Runtime(onert)
• Binding NNFW API to Python can provide an environment where AI models can be easily built, optimized, and executed within devices in various environments, so it can be highly competitive.

Expected benefits

• Even those who know only Python can easily use the ONE Runtime NNFW API.
• By publishing to PyPI, it will be easy to install and use API within python code.

Tasks

• 11589

• 11591

• 11639

Draft : #11541

[jaemaning]

We want to proceed with binding by targeting the runtime/onert/api/include/nnfw.h file.

• CMakeLists.txt
• nnfw_api_pybind11.cc
• nnfw_api_pybind11_tutorial.py

I think it will be done by creating the above 3 files, but I wonder which working folder you think would be better to work in.

if there are better way to work, please suggest to me.

[glistening]

Welcome! I think new directory of runtime/onert/python/api would be introduced as working directory for python API binding.

@Samsung/one_onert, @hseok-oh, @chunseoklee Please give your opinion.

@KangInyeong, @jaemaning Please don't wait for our decision. You may work in any directory. The location will be reviewed when you push a draft PR. Relocating home for python binding would not require much time. :)

[ragmani]

I agree with @glistening. runtime/onert/python/api looks good.

I think we can consider the location of nnfw_api_pybind11_tutorial.py depending on what role it is. If you have a plan to implement nnfw_api_pybind11_tutorial.py with the bound python modules without installing the published python package, it would be a good choice to put the python file in runtime/onert/python/api as well. Or If you mean the tutorial will be implemented with the published python package, another location may be better.

Anyway, please don't wait for our discussion as @glistening said.

[hseok-oh]

IMO, it's enough to use runtime/onert/python without api directory because python will be used for API only under onert directory.

Additionally, we may need to rename runtime/onert/api to runtime/onert/capi.

[glistening]

When I suggest python/api, I was thinking of the following structures:

$ tree runtime/onert/python/
runtime/onert/python/
├── api
├── samples
└── tests

But I am okay for @hseok-oh's suggestion.

We may put

• Python tests under tests/python_api (in the same level of tests/nnfw_api).
• Python samples under runtime/onert/sample (though python and c will be mixed, it looks okay, because it has only 1 sample at this moment.)

Later, move python to under api:

• runtime/onert/api/c and runtime/onert/api/python or
• runtime/onert/capi and something

I like @hseok-oh's suggestion, which looks simpler.