commit | 3de25fd8e13de066b0dddb4688c6c76f3053ca56 | [log] [tgz] |
---|---|---|
author | Mirko Bonadei <[email protected]> | Thu Jun 25 22:19:14 2020 |
committer | Commit Bot <[email protected]> | Thu Jun 25 22:19:14 2020 |
tree | 26453d2b7c13e56d080cdb57d43feaa2b1947d3a | |
parent | 8bd7c1914789f7f702b98b5e57381188c027d2b1 [diff] |
Reland "Abseil component build (default symbols visibility)." This is a reland of 5906c258bf69b7b1f4276b1215e5afbf0dd80704 This CL adds .def files for release builds (and changes the generator script to generate them at roll time). The issue was that release component builds (is_debug=false) were trying to link symbols that were not available in release mode .obj files. Original change's description: > Abseil component build (default symbols visibility). > > This CL introduces an Abseil component on which all Chromium Abseil > clients will have to depend on. > > Abseil doesn't export symbols explicitly, so for the moment Chromium > exports all of them when is_component_build=true. On Android, Linux and > Mac -fvisibility=default is used while on Windows a .def file is > generated at Abseil roll time. > > Bug: 1046390 > Change-Id: I1697eb9e0179cee01badcf1b687acd94160e5f6d > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2174434 > Commit-Queue: Mirko Bonadei <[email protected]> > Reviewed-by: Nico Weber <[email protected]> > Cr-Commit-Position: refs/heads/master@{#781225} Bug: 1046390 Change-Id: Ieb48ec9eff6d08a0770c4b22521536bb29a76121 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2264062 Commit-Queue: Nico Weber <[email protected]> Reviewed-by: Nico Weber <[email protected]> Cr-Commit-Position: refs/heads/master@{#782701}
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.