I have asked this question on the OE list, but wanted to ask here as well (just in case anyone that reads this does not read the oe list).
We've run into the problem where developers who are busily making changes to their code, building it, testing it and then doing that all over again and again are being bogged down because in one particular use case, several dependent objects (from different recipes/packages) are statically lined together into a single kernel module. Unfortunately when one recipe is rebuilt, the dependant recipe (that links all the modules together) is not: if A depends on (the staging output of) B, and B is rebuilt, A is not (automatically rebuilt). The conventional wisdom on the OE list is that "this is not supported though it would be nice to have" In reading thru the bitbake-dev archive I came accross this posting: https://lists.berlios.de/pipermail/bitbake-dev/2008-February/000385.html in which Richard Purdie seems to have resolved this issue. though, I never saw a corresponding formal patch. 1) Did this code make it into Bitbake somehow? 2) If so how to I make use of it. 3) if not does anyone have any comments on how to resolve this problem. I'm trying to come up to speed on how bitbake works internally, but its slow going, if anyone could offer a hand to give me a clue where to start, I'd be eternally grateful.
_______________________________________________ Bitbake-dev mailing list [email protected] https://lists.berlios.de/mailman/listinfo/bitbake-dev
