commit | 0352ca27bd7761c1c327953291055627fe515ef1 | [log] [tgz] |
---|---|---|
author | Alex Rudenko <alexrudenko@chromium.org> | Thu Aug 08 05:49:17 2024 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Aug 08 05:49:17 2024 |
tree | 9165442280f3af18cc1935a552e0957f62fb2110 | |
parent | 6781147c40d8ed318c8899c7c7a66aa2bda9bef6 [diff] |
Add setup.exe to chromium archives Similar to Chrome for Testing archives, Chromium archives could make use of setup.exe to properly configure the browser on Windows. Bug: 338553158 Change-Id: I395a7dcb549500c961ba0c3166c47f37e3f88369 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5764985 Reviewed-by: Gregory Guterman <guterman@google.com> Commit-Queue: Alex Rudenko <alexrudenko@chromium.org> Cr-Commit-Position: refs/heads/main@{#1338886}
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.