[webkit-dev] What's the rationale for not including config.h in any header files?
mcatanzaro at igalia.com
Tue Aug 1 15:48:30 PDT 2017
On Tue, Aug 1, 2017 at 11:33 PM, Keith Miller <keith_miller at apple.com>
> P.S. There is also a reasonable chance that we will do some form of
> unified sources (compiling multiple cpp files at the same time). In
> that case we don’t need to change our config.h rules.
Do you have experience with unified source builds on macOS? We
basically never do these on Linux, but it's of course possible. These
builds are typically great for production but terrible for development,
since everything needs to be recompiled when any file is changed. Also,
using static to mark functions as file-private no longer works. This is
sure to cause headache. But the benefits may be worthwhile.
Some good description:
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the webkit-dev