Manuel Klimek <klimek_at_[hidden]> writes:

> One interesting problem in the discussion is that there is an underlying
> assumption that the build system / compiler doesn't give you support to
> prevent including private headers in the combined layout - this is not true
> for all build systems.

Wouldn't this require (at least in a portable implementation) "exporting"
(i.e., copying) public headers into a separate location in order to prevent
the compiler from seeing the private stuff? In other words, once we have
-Ifoo, the compiler will "see" every header in foo/.