Adding --enable-extensions=inspector does not build Dom Inspector during a Firefox build

RESOLVED INVALID

Status

()

Firefox
Build Config
RESOLVED INVALID
8 years ago
8 years ago

People

(Reporter: Varun, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

8 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.3) Gecko/20090916 Firefox/3.5.3 (.NET CLR 3.5.30729)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.3) Gecko/20090916 Firefox/3.5.3 (.NET CLR 3.5.30729)

Adding ac_add_options --enable-extensions=inspector
ac_add_options --enable-inspector-apis
 does not build Dom Inspector during a Firefox build (like it does with Thunderbird.)

Reproducible: Always

Steps to Reproduce:
1. Add ac_add_options --enable-extensions=inspector ac_add_options --enable-inspector-apis to .mozconfig
2. start a firefox build
3. the build does not contain the dom inspector extension


Expected Results:  
the build should result in the dom inspector extension with the firefox binary.

Comment 1

8 years ago
Ted, any particular reason you CC'd me on this bug? I'm a tad lost, I confess.
I wanted some DOMi expertise, but you're a Venkman expert, aren't you? I guess I wanted sdwilsh. Man, I'm lost.
The makefiles don't check out the extra repositories like comm-central does.
Ah, yeah. You'll need to manually checkout the inspector code. (or you could just install it from addons.mozilla.org).
Status: UNCONFIRMED → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → INVALID
(Reporter)

Comment 5

8 years ago
Ted: I knew that the inspector code was missing from the Firefox source. I just need to know why is that so when Thunderbird and Seamonkey Suite have it and Firefox doesn't?
They explicitly pull it in client.py:
http://mxr.mozilla.org/comm-central/source/client.py#425

The Firefox build has no analog to that.
You need to log in before you can comment on or make changes to this bug.