25.04.2017, 01:45, "Carlos Alberto Lopez Perez" <clo...@igalia.com>: > On 24/04/17 21:02, Konstantin Tokarev wrote: >> 24.04.2017, 21:10, "Alex Christensen" <achristen...@apple.com>: >>> Thanks for the data, Carlos! This is a growing problem that is hurting >>> productivity. We’ve discussed it a bit and haven’t done enough about it. >>> Here are some of the ideas I’ve heard: >>> >>> 1) Reduce #includes by doing more forward declaring and less inlining. We >>> would probably need link time optimization to not lose performance benefits >>> of inlining functions in headers. >>> 2) Use distributed build tools and caches to cover up the problem. WebKit >>> would still be prohibitively hard to compile for people without lots of >>> expensive computers, but we could greatly improve the productivity of large >>> teams. >>> 3) Use C++ modules >>> 4) Put more commonly included headers into precompiled headers >> Note that CMake-based ports don't use PCH on non-Windows platforms >> currently. > > Right. > > I tried to enable that some years ago using the Cotire CMake module, but > I didn't managed to get it working.
I think generating precompiled header contnents automatically is a horrible idea. However, forcing CMake to build hand-crafted header with gcc/clang using the same flags as C++ source files is very ugly as well. See my attempt at https://github.com/annulen/webkit/commit/951149b083fb697cfb769a75e78f17afe4df3a77 > > https://bugs.webkit.org/show_bug.cgi?id=139438 > > If someone wants to take over it, please feel free. > > , > > _______________________________________________ > webkit-dev mailing list > webkit-dev@lists.webkit.org > https://lists.webkit.org/mailman/listinfo/webkit-dev -- Regards, Konstantin _______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
