On Wednesday 2013-09-04 00:31 -0700, Gregory Szorc wrote: > Assuming it sticks, bug 896797 just landed in inbound and changes > how EXPORTS/headers are installed. This may impact your developer > workflow if you modify EXPORTS in a moz.build file to add/remove > headers. > > Previously, headers were installed incrementally as part of make > directory traversal. In the new world, we write out a "manifest" of > headers when the build config is read from moz.build files and then > we install them in bulk at the top of the build.
Does this undo the protection that the build tiers were designed for, which is to prevent "backwards" dependencies between parts of the build? (In other words, things like preventing XPCOM from depending on headers in layout, so that XPCOM could be used standalone.) Do we still care about ensuring this? If so, should we have some other mechanism (like having standalone builds and showing them on tbpl)? -David -- 𝄞 L. David Baron http://dbaron.org/ 𝄂 𝄢 Mozilla https://www.mozilla.org/ 𝄂 Before I built a wall I'd ask to know What I was walling in or walling out, And to whom I was like to give offense. - Robert Frost, Mending Wall (1914)
signature.asc
Description: Digital signature
_______________________________________________ dev-platform mailing list [email protected] https://lists.mozilla.org/listinfo/dev-platform
