Bug 24917 – Finish support for disabling the JavaScript Debugger at compile time

• Component: Web Inspector (Deprecated)
• Status: RESOLVED FIXED

[Laszlo Gombos]

ChangeSet 37820 (http://trac.webkit.org/changeset/37820) laid the foundation of turning off JavaScript Debugger compile time. 

This bug is to finish the work and - similarly to other feature flags - enable turning of JavaScript Debugger. 

The intention is to keep supporting JavaScript Debugger by default, but enable individual ports/builds to turn it of.

[Laszlo Gombos]

Created attachment 29041 [details]
Fix/Enable turning off JavaScript Debugger

Made an attempt to make sure that in all ports JavaScript Debugger support remains as it was before the patch.

Introduced guards not only where the JavaScript Debugger is used, but also in JavaScript Debugger implementation itself - to stay consistent with other feature flags, like the App Cache (e.g. see http://trac.webkit.org/browser/trunk/WebCore/loader/appcache/ApplicationCacheStorage.h)

Enable the Gtk and Qt ports to turn off JavaScript Debugger support, other ports can enable turning off JavaScript Debugger support later (if there is interest).

[Mark Rowe (bdash)]

Comment on attachment 29041 [details]
Fix/Enable turning off JavaScript Debugger

This is not something that warrants a build-webkit or ./configure option, if this is even useful at all. 

Revision 37820 was contributed by someone from Google.  My assumption is that they wanted to be able to disable debugging in the inspector as it was not easily hooked up to their JavaScript engine at that time.  I don't see the benefit in being able to disable JavaScript debugging when being used with JavaScriptCore.

[Laszlo Gombos]

(In reply to comment #2)

Mark, thanks for the quick feedback. 

Would it be acceptable if the build system changes are local to QtWebKit port (WebCore.pro) - which is my primary interest -  and not global.

I have not found an easy way to add defaults (that are enabled by default) to generate-bindings.pl, so to stay consistent with the rest of the build system, it might make sense to change the define to NO_JAVASCRIPT_DEBUGGER so that it could be set to 0 by default (instead of forcing JAVASCRIPT_DEBUGGER to 1).

The primary motivation for this work is to be able to reduce the binary size for embedded systems (typically not need for JavaScript debugging in production). 

The secondary motivation was to make the build system more consistent (flag should either do its job properly or should be removed).

[Laszlo Gombos]

Created attachment 29989 [details]
Finish/Fix support for disabling the JavaScript Debugger and Profiler 

ChangeSet http://trac.webkit.org/changeset/43072 introduced a global build flag for Debuggerless  builds, and also extended the cover to disable Profiler. 

This patch fixes the build if the ENABLE_JAVASCRIPT_DEBUGGER is set to 0 (changes under page directory) and also explicitly disables some of the .h|.cpp files to reduce the binary size (as it was proposed in the first patch attached to this bug).

[Laszlo Gombos]

Created attachment 30216 [details]
Bring the patch up-to-date

[Eric Seidel (no email)]

Committing to http://svn.webkit.org/repository/webkit/trunk ...
	M	WebCore/ChangeLog
	M	WebCore/bindings/js/JSInspectorControllerCustom.cpp
	M	WebCore/bindings/js/JSJavaScriptCallFrameCustom.cpp
	M	WebCore/inspector/JavaScriptCallFrame.cpp
	M	WebCore/inspector/JavaScriptCallFrame.h
	M	WebCore/inspector/JavaScriptCallFrame.idl
	M	WebCore/inspector/JavaScriptDebugListener.h
	M	WebCore/inspector/JavaScriptDebugServer.cpp
	M	WebCore/inspector/JavaScriptDebugServer.h
	M	WebCore/inspector/JavaScriptProfile.cpp
	M	WebCore/inspector/JavaScriptProfile.h
	M	WebCore/inspector/JavaScriptProfileNode.cpp
	M	WebCore/inspector/JavaScriptProfileNode.h
	M	WebCore/page/Console.cpp
	M	WebCore/page/Console.h
	M	WebCore/page/Console.idl
Committed r43761