The introduction of modules made the process of developing a module for ARTist a lot easier. It's not necessary to checkout AOSP anymore. However it is still messy to develop modules. The developer has to build the module, push it to the device, import the module and instrument the desired app using the module. A lot of room for improvement.
What we want is to press a button in the IDE of the user which builds the module, pushes it to the device, instruments the desired app and starts the app. We have a CMakeLists.txt file for IDE support (syntax highlighting, auto completion, ...).
It's possible to let CMake build the module automatically¹ and push the module onto a device. ArtistGui can import it, instrument an app and start it automatically using a custom broadcast. We can trigger it then after pushing the module to the device.
The introduction of modules made the process of developing a module for ARTist a lot easier. It's not necessary to checkout AOSP anymore. However it is still messy to develop modules. The developer has to build the module, push it to the device, import the module and instrument the desired app using the module. A lot of room for improvement. What we want is to press a button in the IDE of the user which builds the module, pushes it to the device, instruments the desired app and starts the app. We have a CMakeLists.txt file for IDE support (syntax highlighting, auto completion, ...).
It's possible to let CMake build the module automatically¹ and push the module onto a device. ArtistGui can import it, instrument an app and start it automatically using a custom broadcast. We can trigger it then after pushing the module to the device.
¹ https://cmake.org/cmake/help/v3.6/manual/cmake-toolchains.7.html
Affected Projects (ticked = done)