Closed
Bug 70161
Opened 24 years ago
Closed 23 years ago
hook extensions/inspector into the Mac build
Categories
(Core :: DOM: Core & HTML, defect)
Tracking
()
VERIFIED
FIXED
People
(Reporter: scc, Assigned: hewitt)
Details
Attachments
(6 files)
84.04 KB,
application/octet-stream
|
Details | |
74.04 KB,
application/octet-stream
|
Details | |
82 bytes,
text/plain
|
Details | |
12 bytes,
text/plain
|
Details | |
4.25 KB,
patch
|
Details | Diff | Splinter Review | |
8.06 KB,
patch
|
Details | Diff | Splinter Review |
No description provided.
Reporter | ||
Comment 1•24 years ago
|
||
OK, I checked in a couple of mac projects and the associated prefixes and manifests. Didn't add it to the build, as we'll want smfr's advice on how to make it optional. Still need to add optimized libraries to match the debug ones...
Comment 2•24 years ago
|
||
To add an option to the build: 1. Add your new option to mozilla/build/mac/build_scripts/MozillaBuildFlags.txt, in the 'options_flags' group. The value there sets the default (on or off). 2. Test your option in the main script (e.g. $main::options{mathml}) to determine whether to build projects/manifests. 3. Inform users that they can turn the option on by setting options foobar 1 in their build prefs.
Comment 3•24 years ago
|
||
Ugh, these project files are really broken. I've made new ones, will attach them to the bug tomorrow, together with the necesary build script changes.
Comment 4•24 years ago
|
||
Comment 5•24 years ago
|
||
Comment 6•24 years ago
|
||
Comment 7•24 years ago
|
||
Comment 8•24 years ago
|
||
Comment 9•24 years ago
|
||
Comment 10•24 years ago
|
||
I've attached the changes I had to make for getting Document Inspector building and working on Mac. I have moved the .rdf files from the chrome dir to the res dir, because it's much easier to find the files there from JS (the hack that was used to find them in the chrome dir didn't work for Mac). So http://bugzilla.mozilla.org/showattachment.cgi?attach_id=26692 will need to be reviewed on other platforms too.
Assignee | ||
Comment 11•24 years ago
|
||
Wow, thanks for helping, Peter! I'll review these changes this weekend on windows and linux.
Status: NEW → ASSIGNED
Assignee | ||
Comment 12•24 years ago
|
||
Everything seems to work fine on Windows after the source changes. I'll check all this stuff in this weekend after I finish making some other changes I'm working on.
Assignee | ||
Comment 13•23 years ago
|
||
I see that peterv has already landed all this
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
Comment 14•23 years ago
|
||
Nope, I didn't. These still need to go in (you wrote you were going to do that): mozilla/extensions/inspector/resources/content/MANIFEST mozilla/extensions/inspector/resources/content/prefs/MANIFEST Patch to Document Inspector source files I think I'll also need to update the IDL project file, but I'll check. Please check in these files and then we can finally close the bug :-).
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Assignee | ||
Updated•23 years ago
|
Status: REOPENED → ASSIGNED
Assignee | ||
Comment 15•23 years ago
|
||
Ok, I just landed all the necessary stuff to make inspector build on mac. I have tested it with a debug build, but not optimized since my mac always runs out of memory when I try to do that. Peterv, can you verify this for me?
Comment 16•23 years ago
|
||
Just checked in a new version of the InspectorIDL.mcp project to fix the wrong output path for the headers. Inspector build, I haven't tried it out yet but marking this fixed and then verified.
Status: ASSIGNED → RESOLVED
Closed: 23 years ago → 23 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Component: DOM: Mozilla Extensions → DOM
Updated•5 years ago
|
Component: DOM → DOM: Core & HTML
You need to log in
before you can comment on or make changes to this bug.
Description
•