Skip to content

Instantly share code, notes, and snippets.

@oscarrodar

oscarrodar/edge-dev-script.md

Last active June 1, 2022 23:19
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save oscarrodar/d3605ddf9d61ba552c9723daa28909ac to your computer and use it in GitHub Desktop.
Save oscarrodar/d3605ddf9d61ba552c9723daa28909ac to your computer and use it in GitHub Desktop.
Download ZIP
Edge Development Script
Raw
edge-dev-script.md

Edge Development Script

This is meant to help as a guide when it comes to a Edge development workflow.

Steps

  1. Launch Edge C__edge commmand app located in your desktop and make sure it doesn't retrieve an error.
  2. Checkout main branch using git checkout main
  3. Make sure to pull latest change using git pull
  4. At this moment you can create your own development branch following this standard user/[your-user-name]/[branch-name-based-on-dev-work]. For example: user/orodriguez/pi-feature-flag
  5. Execute gclient sync -D to recreate the dependencies tree
  6. Generate compile_commands.json. Run vpython tools/clang/scripts/generate_compdb.py -p .\out\debug_x64\ -o compile_commands.json
  7. Run autogn x64 debug to create a version of Edge where you can debug your changes using VSCode
  8. Run autogn x64 release before creating new PR in order to see you didn't break anything and your feature is working as expected
  9. When above steps have been executed a new path will be created so you can navigate to it. Most likely, path generated will be something like pushd C:\Edge\src\out\debug_x64
  10. Once in pushd C:\Edge\src\out\debug_x64 you can execute autoninja chrome every time you create a change in the source code
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment