@@ -276,4 +276,4 @@ Finally, you need to write the registration function and the de-registration fun
...
@@ -276,4 +276,4 @@ Finally, you need to write the registration function and the de-registration fun
From the above description, we can know that the core work of adding a custom device is to fill the `ir_device_t` structure. After the description is completed, all the work of device registration is completed. The modular `device` makes **Tengine Lite** very easy to expand and has enough flexibility.
From the above description, we can know that the core work of adding a custom device is to fill the `ir_device_t` structure. After the description is completed, all the work of device registration is completed. The modular `device` makes **Tengine Lite** very easy to expand and has enough flexibility.
## Surprise
## Surprise
In the `init_tengine(void)` function, when the `operator prototype` completes the registration, the registered ones are `serializer` and `devices`, but the function does not jump in the static code state, and the user can install an integrated development environment , Such as `Microsoft Visual Studio` or `Jetbrains Clion`, after opening the folder and generating the `CMake` process, you can jump.
In the `init_tengine(void)` function, when the `operator prototype` completes the registration, the registered ones are `serializer` and `devices`, but the function does not jump in the static code state, and the user can install an integrated development environment , Such as `Microsoft Visual Studio` or `JetBrains CLion`, after opening the folder and generating the `CMake` process, you can jump.