New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 920088 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Chrome
Pri: 3
Type: Bug



Sign in to add a comment

Include paths for wayland protocol headers shouldn't be added to public configs

Project Member Reported by hashimoto@chromium.org, Jan 9

Issue description

Currently, wayland protocol headers are included with #include <foo-protocol-header.h> style in .cc files.
This requires the include paths for those headers to be added to include_dirs GN variable as public configs, so that any code which (directly or indirectly) depends on the protocol can compile.

As piman@ pointed out in crrev.com/c/1375197, this is not good in terms of build speed.
We should stop adding include paths to public configs by doing something.
 

Sign in to add a comment