Bug 32462 – build-webkit: Add --inspector-frontend flag to copy inspector front-end changes to the built framework

• Component: Tools / Tests
• Status: RESOLVED FIXED

[Daniel Bates]

We should make inspector development more consistent with the rest of WebKit development.

Currently, any changes that are made to the front-end inspector files must be manually copied over to the built WebCore framework in order to test the changes. Instead, we should have a flag, say --inspector-frontend, that will do this. Moreover, build-webkit should be smart enough to know which front-end files have changed so that we don't have to copy over all the front-end files.

[Timothy Hatcher]

Note building with Xcode works fine.

[Daniel Bates]

Created attachment 44726 [details]
Patch

Briefly read through the Qt and GTK build files, but I am unclear what the default installation directory for the inspector front-end files is for the Qt and GTK builds. In particular for the Windows platform. For reference, on my Ubuntu Qt build it defaults to /usr/share.  I'll try reading through these files again. Does anybody know offhand?

[Daniel Bates]

Created attachment 44742 [details]
Patch

Minor stylistic change. Changed ordering of variables $sourceInspectorPath and $inspectorResourcesDirPath in subroutine copyInspectorFrontendFiles.

Spoke to Timothy on IRC, and this patch should be sufficient to land. That is, the assumptions for the Qt and GTK builds are not unreasonable. Optionally, the user can set the environment variable WebKitInspectorResourcesDir to specify where the built inspector front-end files are located.

[WebKit Review Bot]

style-queue ran check-webkit-style on attachment 44742 [details] without any errors.

[WebKit Commit Bot]

Comment on attachment 44742 [details]
Patch

Clearing flags on attachment: 44742

Committed r52393: <http://trac.webkit.org/changeset/52393>

[WebKit Commit Bot]

All reviewed patches have been landed.  Closing bug.