Closed
Bug 148444
Opened 24 years ago
Closed 10 years ago
Bad pref file references in embedding configurations
Categories
(Core Graveyard :: Embedding: Mac, defect)
Core Graveyard
Embedding: Mac
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: bnesse, Unassigned)
Details
Attachments
(1 file)
|
5.30 KB,
patch
|
adamlock
:
review+
netscape
:
superreview+
|
Details | Diff | Splinter Review |
This is not mac specific, but none of the other categories make sense, and the
mac is somewhat more affected than the other platforms, so I'm defaulting this
to Embedding:Mac.
While building Chimera, I've noticed warnings/errors during the make process
referencing initpref.js & unix.js. Initpref.js no longer exists and is invalid
on all platforms, and for the mach-o and cocoa builds I think we should be
referencing macprefs.js and macxprefs.js instead of unix.js.
Comment 1•24 years ago
|
||
is this a Makefile.in-related thing? (I've never build chimera before)
cc'ing seawood
| Reporter | ||
Comment 2•24 years ago
|
||
The specific files are basebrowser-<insert_your_platform_here> and the cocoa
embed project builder file.
http://lxr.mozilla.org/seamonkey/search?string=initpref.js
Comment 3•24 years ago
|
||
The warnings are harmless. Since the files aren't capable of ifdefs, they list
files that aren't be needed for specific configurations. Wrt the mac prefs
files, I was under the impression that the mach-o build used the unix prefs like
it does the unix fileio. Cc'ing Adam Lock.
| Reporter | ||
Comment 4•24 years ago
|
||
Sure, I realize the warnings are harmless... But it's not a configuration
thing... InitPrefs.js is not valid on *any* platform... the file no longer
exists. I'm just saying the script(s) should be changed to reflect that.
As for the macprefs thing... These are application level prefs. As this is a Mac
build I think the Mac prefs are appropriate. The mach-o Mozilla build is
currently using the mac files... if this is wrong for some reason, we need to
change that too.
Comment 5•24 years ago
|
||
it's a mac app, we want to use mac prefs
| Reporter | ||
Comment 6•24 years ago
|
||
This is what I believe the various configurations (and the cocoa embed project)
should look like.
Comment on attachment 86088 [details] [diff] [review]
Proposed patch
r=adamlock on the non-Macho manifest changes. Mike do you want to r= those?
Attachment #86088 -
Flags: review+
Comment 8•24 years ago
|
||
r=pink on the mach-o stuff and pb changes
Comment 9•24 years ago
|
||
I want seawood to r/sr this....
Comment 10•24 years ago
|
||
Comment on attachment 86088 [details] [diff] [review]
Proposed patch
r/sr=cls
Attachment #86088 -
Flags: superreview+
| Reporter | ||
Comment 11•24 years ago
|
||
Fix checked in.
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
Comment 13•23 years ago
|
||
patch checked into corresponding files. verified it on latest trunk build.
Marking the bug verified.
Status: RESOLVED → VERIFIED
Comment 14•23 years ago
|
||
The patch says that initpref.js is no longer valid. I verified it on branch
build(2002-10-09-05-1.0) for PPEmbed and MFCEmbed. Both of them still contains
initpref.js.
However the trunk builds donot have that. Should it be removed from branch.
Status: VERIFIED → REOPENED
Resolution: FIXED → ---
Updated•16 years ago
|
Assignee: bnesse → nobody
QA Contact: dsirnapalli → mac
Comment 15•10 years ago
|
||
Mass change of bugs in the Embedding: Mac component in preparation for archiving it. I don't believe any of these are useful any more, as we don't have a mac embedding API. If they are relevant, they should be moved to an alternate component.
Status: REOPENED → RESOLVED
Closed: 24 years ago → 10 years ago
Resolution: --- → INCOMPLETE
| Assignee | ||
Updated•10 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•