can you EXPORT_FUNCTIONS a function which is not a task?
"Robert P. J. Day" <[email protected]> Fri, 26 Jun 2026 08:07:19 -0400 (EDT)
| Newsgroups | org.yoctoproject.lists.docs |
|---|---|
| Message-ID | <[email protected]> |
digging into that whole class function inheritance thing as explained in the bitbake manual: https://docs.yoctoproject.org/bitbake/2.18/bitbake-user-manual/bitbake-user-manual-metadata.html#flexible-inheritance-for-class-functions and the first couple paragraphs: "Through coding techniques and the use of EXPORT_FUNCTIONS, BitBake supports exporting a function from a class such that the class function appears as the default implementation of the function, but can still be called if a recipe inheriting the class needs to define its own version of the function. "To understand the benefits of this feature, consider the basic scenario where a class defines a task function and your recipe inherits the class. In this basic scenario, your recipe inherits the task function as defined in the class..." bounce back and forth between talking about inheritance, first, simply of "functions", then switch to referring to "task functions." so which is it? can you export non-task functions? does that even make any sense? i tested by adding a non-task function (base_do_rday) to base.bbclass, did not "addtask" it, and parsing did not complain when i added it to the EXPORT_FUNCTIONS line. should that have worked? rday