
This patch moves: "base/allocator/partition_allocator/..." into: "base/allocator/partition_allocator/src/partition_alloc/...". This tried to keep it as minimal as possible. Interesting follow-ups will happen outside of the rename. Context: -------- To protect against UAF, we want to make the PartitionAlloc library embeddable by some third_parties: pdfium, angle, dawn, swiftshader, ... PartitionAlloc do not declare yet where is its "include_dir". It means third parties must put the library files under "base/allocator/partition_allocator", even if they do not use "base" and would have liked to put it inside their "third_party" directory. We would like to make PartitionAllocator behave like a regular library. It should be importable using: #include <partition_alloc/...> That's why we are using: "src/partition_alloc" This implements step 1 of: 1. Move from files under `src/partition_alloc/` 2. Declare PartitionAlloc GN include_dirs. 3. Update the dependants to use #include <partition_alloc/...> Bug: chromium:1467773 Cq-Include-Trybots: luci.chromium.try:linux-chromeos-siso-rel Cq-Include-Trybots: luci.chromium.try:linux-lacros-siso-rel Cq-Include-Trybots: luci.chromium.try:linux-siso-rel Cq-Include-Trybots: luci.chromium.try:linux-wayland-siso-rel Cq-Include-Trybots: luci.chromium.try:linux-wayland-siso-rel Cq-Include-Trybots: luci.chromium.try:linux_chromium_asan_siso_rel_ng Cq-Include-Trybots: luci.chromium.try:win-siso-rel Change-Id: I1b25cdc9f8077a7041221f51441c72b04b800dcc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4812338 Commit-Queue: Arthur Sonzogni <arthursonzogni@chromium.org> Reviewed-by: Yuki Shiino <yukishiino@chromium.org> Owners-Override: danakj <danakj@chromium.org> Reviewed-by: danakj <danakj@chromium.org> Cr-Commit-Position: refs/heads/main@{#1204530}
Chromium
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.
To check out the source code locally, don't use git clone
! Instead,
follow the instructions on how to get the code.
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.
If you found a bug, please file it at https://crbug.com/new.