commit | a95e1204777ae7d75fc7962ea16131cc2447b369 | [log] [tgz] |
---|---|---|
author | Tom Anderson <[email protected]> | Wed Sep 09 23:08:00 2020 |
committer | Commit Bot <[email protected]> | Wed Sep 09 23:08:00 2020 |
tree | 415f3b6b5216e2e4ce47f8d9baae7091e35e53da | |
parent | 68a391b7f238cdc169dd5904134dbc75788d91f8 [diff] |
[XProto] Remove usage of all Xlib headers This CL removes <X11/Xlib.h> from //ui/gfx/x/x11.h. What was provided by Xlib.h is now provided with inline declarations. The intent is that I'll incrementally remove declarations from x11.h until there's nothing left, at which point the dependency on Xlib will be removed and therefore x11.h can be removed. Doing it this way will ensure no additional usages of Xlib are introduced, and it gives a nice way of tracking progress as usages are removed. * All Xlib macros are now gone, so it's safe to remove the XProto "undef" files. * For some usages of Xlib (events in particular), it's easier to port to XProto now rather than add declarations to x11.h. * ui/gfx/x/keysyms/keysyms.h is added in its own directory because it's needed by xkbcommon code, which is also built on ChromeOS, but ui/gfx/x/BUIDL.gn asserts that the platform is desktop Linux. BUG=1066670 R=sky Change-Id: If8679721548d45bdea48bcd8a898191b3f87eb10 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2392140 Auto-Submit: Thomas Anderson <[email protected]> Commit-Queue: Scott Violet <[email protected]> Reviewed-by: Scott Violet <[email protected]> Reviewed-by: Nick Yamane <[email protected]> Reviewed-by: Zhenyao Mo <[email protected]> Cr-Commit-Position: refs/heads/master@{#805533}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure .
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.