electron/build/config/BUILD.gn

action("generate_mas_config") {
  outputs = [ "$target_gen_dir/../../mas.h" ]
  script = "../../script/generate-mas-config.py"
  if (is_mas_build) {
    args = [ "true" ]
  } else {
    args = [ "false" ]
  }

  args += rebase_path(outputs)
}
build: make is_mas_build a generated header instead of config (#43737) 2024-09-17 01:38:56 -07:00			`action("generate_mas_config") {`
			`outputs = [ "$target_gen_dir/../../mas.h" ]`
			`script = "../../script/generate-mas-config.py"`
build: move libcc patches to electron repo (#14104) In the GN build, libchromiumcontent is no longer a distinct library, but merely a container for a set of scripts and patches. Maintaining those patches in a separate repository is tedious and error-prone, so merge them into the main repo. Once this is merged and GN is the default way to build Electron, the libchromiumcontent repository can be archived. 2018-09-13 22:02:16 -07:00			`if (is_mas_build) {`
build: make is_mas_build a generated header instead of config (#43737) 2024-09-17 01:38:56 -07:00			`args = [ "true" ]`
refactor: change defined(MAS_BUILD) to IS_MAS_BUILD() (#36332) * refactor: change defined(MAS_BUILD) to IS_MAS_BUILD() This is missing-definition safe and thus allows us to move the definition of this macro away from "all compilation targets" to "just the compilation targets that depend on this macro". In turn this makes the rebuild time changing from mas <-> darwin only 80 seconds on my machine, instead of the 12-15 minutes it used to take. This will also allow us in the future to build both MAS and darwin on the same CI machine. Costing us ~2 minutes on one machine but saving us anywhere from 30 minutes to an hour of CI time on other parts of the matrix. * build: always define IS_MAS_BUILD even on non-mac builds * build: use extra_configs 2022-11-14 12:46:52 -08:00			`} else {`
build: make is_mas_build a generated header instead of config (#43737) 2024-09-17 01:38:56 -07:00			`args = [ "false" ]`
build: move libcc patches to electron repo (#14104) In the GN build, libchromiumcontent is no longer a distinct library, but merely a container for a set of scripts and patches. Maintaining those patches in a separate repository is tedious and error-prone, so merge them into the main repo. Once this is merged and GN is the default way to build Electron, the libchromiumcontent repository can be archived. 2018-09-13 22:02:16 -07:00			`}`
build: make is_mas_build a generated header instead of config (#43737) 2024-09-17 01:38:56 -07:00
			`args += rebase_path(outputs)`
build: move libcc patches to electron repo (#14104) In the GN build, libchromiumcontent is no longer a distinct library, but merely a container for a set of scripts and patches. Maintaining those patches in a separate repository is tedious and error-prone, so merge them into the main repo. Once this is merged and GN is the default way to build Electron, the libchromiumcontent repository can be archived. 2018-09-13 22:02:16 -07:00			`}`