Now with brendan's new compilation in place, we should also be able to check that we compile against the devtools frontend, which has slightly different compilation settings.
Basically i'm thinking we'll use latest devtools frontend, copy our renderer sources in there, and run its closure.
We have a few prerequisites:
- paul lands the ReportRenderer CL in devtools
- will adds a hook to compile_frontend.py to provide a custom path for protocol_externs
- paul adds a hook to our roll-to-devtools.sh to provide a different
$frontend_dir location.
Then I think the flow looks something like this
Add latest devtools frontend to devDeps:
"devtools-frontend-tot": "git://github.com/ChromeDevTools/devtools-frontend.git",
Probably add [ChromeDevTools/devtools-protocol) to devDeps as well.
Run roll-to-devtools.sh with ./node_modules/devtools-frontend-tot/front_end, which copies our renderer files over.
Reach into the frontend and run closure:
npm explore devtools-frontend-tot -- npm run closure
Now with brendan's new compilation in place, we should also be able to check that we compile against the devtools frontend, which has slightly different compilation settings.
Basically i'm thinking we'll use latest devtools frontend, copy our renderer sources in there, and run its closure.
We have a few prerequisites:
$frontend_dirlocation.Then I think the flow looks something like this
Add latest devtools frontend to devDeps:
Probably add [ChromeDevTools/devtools-protocol) to devDeps as well.
Run roll-to-devtools.sh with
./node_modules/devtools-frontend-tot/front_end, which copies our renderer files over.Reach into the frontend and run closure: