The pull-request contains three commits. The OpenVG package is maybe the least controversial one. It's a new software package for the RPI.
The two others are worth more discussion:
custom task dir. We've been using this for a few months now, and it makes us very happy. The gist of it is that you can keep a out-of-repo directory with custom tasks that then are combined together to create the actual configuration. Through this we achieved much more flexibility when working with OpenADK. Also for privacy reasons, we don't want to commit our tasks to the mainline repo, meaning it becomes an additional burden to maintain OpenADK for us. This feature removes this requirement.
To give you an example how this works: when creating the defconfig, we use
ADK_APPLIANCE=ourboard\|development\|diez
to create a combination of three distinct tasks into one. This removed all need for us to tinker with .config after defconfig, greatly enhancing our workflow.
-D option for pre-population of data-partition content
This is useful for us through our custom tooling around OpenADK, where be build a set of applications and custom kernel modules, and want these to end up on the device during re-flashing.
The pull-request contains three commits. The OpenVG package is maybe the least controversial one. It's a new software package for the RPI.
The two others are worth more discussion:
- custom task dir. We've been using this for a few months now, and it makes us very happy. The gist of it is that you can keep a out-of-repo directory with custom tasks that then are combined together to create the actual configuration. Through this we achieved much more flexibility when working with OpenADK. Also for privacy reasons, we don't want to commit our tasks to the mainline repo, meaning it becomes an additional burden to maintain OpenADK for us. This feature removes this requirement.
To give you an example how this works: when creating the defconfig, we use
ADK_APPLIANCE=ourboard\\|development\\|diez
to create a combination of three distinct tasks into one. This removed all need for us to tinker with .config after defconfig, greatly enhancing our workflow.
- -D option for pre-population of data-partition content
This is useful for us through our custom tooling around OpenADK, where be build a set of applications and custom kernel modules, and want these to end up on the device during re-flashing.
The pull-request contains three commits. The OpenVG package is maybe the least controversial one. It's a new software package for the RPI.
The two others are worth more discussion:
To give you an example how this works: when creating the defconfig, we use
ADK_APPLIANCE=ourboard\|development\|diez
to create a combination of three distinct tasks into one. This removed all need for us to tinker with .config after defconfig, greatly enhancing our workflow.
This is useful for us through our custom tooling around OpenADK, where be build a set of applications and custom kernel modules, and want these to end up on the device during re-flashing.
Hi, nice patchset. Could you add some documentation to the new custom task dir feature under docs/?
best regards wbx
@wbx I've added a bit of documentation. Let me know what you think.