Has the time come to get rid of the "delivering" of public headers?
michael.meeks at suse.com
Thu Feb 23 02:07:21 PST 2012
On Thu, 2012-02-23 at 01:22 +0100, Bjoern Michaelsen wrote:
> It is neither an anachronism or has something to do with building over the
> network. Nobody sane did that on Windows anyway
Surely that is what Hamburg release engineering did for years :-)
> But for things like sw or sc, the lack of encapsulation and the need to include
> 75% of all the public headers in each and every compile (e.g. via
> sw/inc/doc.hxx) and reparse those are a real killer.
Ok - so, at least some better data. But this seems to suggest that the
problem is not multiple include-path sub-directories (as was suggested)
but badly structured includes - which is an orthogonal problem - right ?
At least, I share Tor's view that we should have some real numbers
about the cost of a given thing: multiple include paths, vs. single ones
before doing the re-licensing & then the code re-structuring ;-)
michael.meeks at suse.com <><, Pseudo Engineer, itinerant idiot
More information about the LibreOffice