Google Git
Sign in
fuchsia / fuchsia / HEAD / . / scripts
tree: 489316df447f2b1e89a093ef78fd84231d6fa790 [path history] [tgz]
  1. autoconf/
  2. check_deps/
  3. clang/
  4. cog/
  5. debug/
  6. devshell/
  7. disable_ctf_tests/
  8. docker/
  9. emacs/
  10. ffx_complete/
  11. fish/
  12. fortunes/
  13. fxtest/
  14. gce/
  15. git/
  16. gn/
  17. gn_complete/
  18. jiri/
  19. lib/
  20. memory/
  21. mkinstaller/
  22. move_source/
  23. owner/
  24. prebuilts/
  25. puppet/
  26. rust/
  27. sdk/
  28. shac/
  29. style/
  30. tests/
  31. third_party/
  32. unification/
  33. verify_cmdline_params/
  34. versioning/
  35. vim/
  36. wconversion/
  37. youcompleteme/
  38. zsh-completion/
  39. fuchsia-vendored-python ⇨ fuchsia-vendored-python3.11
  40. bootstrap
  41. build-qemu.sh
  42. BUILD.bazel
  43. BUILD.gn
  44. build_id_conv.py
  45. build_id_conv_test.py
  46. build_id_to_debug_id.py
  47. change_testability_review_analyzer.py
  48. collect_lines_to_tree.py
  49. colorize_logs
  50. compare_elf_sizes.py
  51. fd.py
  52. fetch-build-artifacts
  53. fidl_project_schema.json
  54. find_integration_revision.py
  55. flog
  56. fuchsia-vendored-python3.11
  57. fx
  58. fx-env.fish
  59. fx-env.sh
  60. fx-help.awk
  61. fx-reentry
  62. fx-wrapper
  63. generate-fidl-project.py
  64. generate-fidl-tags.py
  65. generate_cargo.py
  66. generate_gn_desc.py
  67. git_utils.py
  68. gn_to_cmake.py
  69. hermetic-env
  70. OWNERS
  71. paths.py
  72. README.md
  73. run-zircon-arm64
  74. run-zircon-x86
  75. simplify_stacktraces
  76. start-unsecure-internet.sh
  77. sync-from-stem.py
scripts/README.md

Scripts

This repository is for scripts useful when working with the Fuchsia source code.

fx

fx is the front-door to a collection of scripts that make many tasks related to Fuchsia development easier. It contains a large number of subcommands, which can be discovered by running fx help. If you use bash or zsh as a shell, you can get some auto-completion for fx by sourcing scripts/fx-env.sh into your shell.

OWNERShip

Given the wide breadth of the code under //scripts and the project's desire to encourage more local ownership, there are intentionally no OWNERS of //scripts itself (only per-file entries). Rather, the addition of new subdirectories or top-level files is expected to fall back toward requiring an OWNERS override.