Files
brave-core/script/lib
Aleksey Khoroshilov 97a5f35253 Always use "brave" as branding_path_product, fix strings generation.
Chromium change:
https://chromium.googlesource.com/chromium/src/+/79ca9265d25f26dd9dc3c8fad2a72241054e14ae

commit 79ca9265d25f26dd9dc3c8fad2a72241054e14ae
Author: Henrique Ferreiro <hferreiro@igalia.com>
Date:   Wed Aug 23 10:17:33 2023 +0000

    Simplify the build for branded strings

    Branded strings are defined in *chromium_strings.grd and
    *google_chrome_strings.grd files. Both kind of files contain different
    messages for the same ids. Those ids are compiled into generated header
    files by their corresponding targets. Both the targets and the header
    files are named differently, similarly to the grd files. This requires
    that the correct target and header file is used depending on the build
    but, in practice, most code sites just depend on both targets and
    include both header files.

    This CL merges those targets so that from now on only the chromium
    version is used (e.g.
    //chrome/app:chromium_strings and chrome/grit/chromium_strings.h,
    //components/strings/component_chromium_strings and
    components/strings/grit/components_chromium_strings.h, etc.). The
    targets are parameterized by `branding_path_product` so that the correct
    grd and pak filenames are used.

    Future CLs will change the targets and generated files to be named
    *branded_strings.

    Bug: 1470725
2023-09-27 13:08:20 +03:00
..