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