OLD | NEW |
(Empty) | |
| 1 ### tools/gritsettings README |
| 2 |
| 3 This directory contains several files that apply global to the Chrome resource |
| 4 generation system (which uses GRIT - see tools/grit). |
| 5 |
| 6 **resource_ids**: This file is used to assign starting resource ids for |
| 7 resources and strings used by Chromium. This is done to ensure that resource ids |
| 8 are unique across all the grd files. If you are adding a new grd file, please |
| 9 add a new entry to this file. |
| 10 |
| 11 **translation_expectations.pyl**: Specifies which grd files should be translated |
| 12 and into which languages they should be translated. Used by the internal |
| 13 translation process. |
| 14 |
| 15 **startup_resources_[platform].txt**: These files provide a pre-determined |
| 16 resource id ordering that will be used by GRIT when assigning resources ids. The |
| 17 goal is to have the resource loaded during Chrome startup be ordered first in |
| 18 the .pak files, so that fewer page faults are suffered during Chrome start up. |
| 19 To update or generate one of these files, follow these instructions: |
| 20 |
| 21 1. Build a Chrome official release build and launch it with command line: |
| 22 `--print-resource-ids` and save the output to a file (e.g. res.txt). |
| 23 |
| 24 2. Generate the startup_resources_[platform].txt via the following command |
| 25 (you can redirect its output to the new file location): |
| 26 |
| 27 ` |
| 28 tools/grit/grit/format/gen_predetermined_ids.py res_ids.txt out/gn |
| 29 ` |
| 30 |
| 31 In the above command, res_ids.txt is the file produced in step 1 and out/gn |
| 32 is you Chrome build directory where you compiled Chrome. The output of the |
| 33 command can be added as a new startup_resource_[platform] |
| 34 |
| 35 3. If this is a new file, modify `tools/grit/grit_rule.gni` to set its path |
| 36 via `grit_predetermined_resource_ids_file` for the given platform. |
OLD | NEW |