tree: a5539488acaea5d434e1cf2b4a4d707f2fe8b751 [path history] [tgz]
  1. chrome_debug_launcher/
  2. closure/
  3. compiler-runner/
  4. hosted_mode/
  5. js_build/
  6. jsdoc-validator/
  7. local_node/
  8. __init__.py
  9. build_debug_applications.py
  10. build_release_applications.py
  11. CodeGeneratorFrontend.py
  12. compile_frontend.py
  13. convert_svg_images_to_png.py
  14. devtools_file_hashes.py
  15. generate_devtools_extension_api.py
  16. generate_devtools_grd.py
  17. generate_protocol_externs.py
  18. generate_supported_css.py
  19. install_node_deps.py
  20. lint_javascript.py
  21. modular_build.py
  22. npm_test.js
  23. optimize_png_images.py
  24. OWNERS
  25. README.md
  26. rjsmin.py
  27. run_inspector_tests.sh
  28. start_chrome_and_server.js
  29. unzip.py
  30. utils.js
third_party/WebKit/Source/devtools/scripts/README.md

DevTools Scripts

Python build scripts

  • compile_frontend.py - runs closure compiler to do static type analysis
    • Note: the compiled outputs are not actually used to run DevTools
  • optimize_png_images.py - manually run when adding png images
  • convert_svg_images_to_png.py - manually run when adding svg images

Closure

DevTools manually rolls the closure compiler to ./closure. If you manually roll closure compiler, you will need to re-generate the compiler-runner and jsdoc-validator custom jars using the python scripts in their respective directory. Make sure you use JDK 7 to compile these jars, otherwise they won't run on buildbot. If you compile with JDK 7, anyone with Java 7 or Java 8 should be able to run the jar.