On Tue, 2011-03-15 at 10:08 +0100, Esben Haabendal wrote: > The current dependency/staging model of OE basically has this feature > that a build can be influenced not only by it's own dependencies, but > also what has been build before it (or not). > > I strongly believe that this has to be fixed on the architectural level, > and not just on a case-by-case level as is currently needed.
Yes, agreed. This clearly sucks, and indeed I think it is probably the largest single area of architectural suckage in OE today. > I am still very much interested in discussing how to move this > technology from OE-lite to OE, but as it impacts all recipe metadata > (build dependencies has to be redefined), OE community at a large really > needs to value the benefits of solving this problem. The benefits of solving the problem are clearly very great, but I don't think OE itself is really in a position to embrace a "big bang" kind of change which would require redefining all the build dependencies. I think we need to find a technological solution which will work with our current DEPENDS scheme. I did do some work in that direction about a year ago, but I got sidetracked into dealing with some toolchain suckage (which was making it difficult to construct the per-recipe sysroots in the way that I wanted) and then ran out of time. I would like to get back to working on this stuff but right now it is difficult for me to set aside the time for it. p. _______________________________________________ Openembedded-devel mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
