Closed
Bug 216505
Opened 21 years ago
Closed 21 years ago
Support using $topsrcdir in mozconfig
Categories
(SeaMonkey :: Build Config, defect)
SeaMonkey
Build Config
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: bryner, Assigned: bryner)
Details
Attachments
(1 file)
749 bytes,
patch
|
cls
:
review+
asa
:
approval1.5b+
|
Details | Diff | Splinter Review |
For including product-specific default configure options (i.e. for Firebird, Thunderbird, or MiniMo), it's useful to be able to include a checked-in mozconfig file with ".". This allows you to add extra options to your own mozconfig, without having to worry about updating it when the defaults change. To make this work well, we need $topsrcdir to be available for use in mozconfig.
Assignee | ||
Comment 1•21 years ago
|
||
Use |topsrcdir| consistently in mozconfig2configure and mozconfig2client-mk.
Assignee | ||
Updated•21 years ago
|
Attachment #129963 -
Flags: review?(cls)
Attachment #129963 -
Flags: review?(cls) → review+
Assignee | ||
Comment 2•21 years ago
|
||
Comment on attachment 129963 [details] [diff] [review] patch Can I get this in for 1.5b? It's a low-risk build system change.
Attachment #129963 -
Flags: approval1.5b?
Comment 3•21 years ago
|
||
Comment on attachment 129963 [details] [diff] [review] patch a=asa (on behalf of drivers) for checkin to 1.5beta
Attachment #129963 -
Flags: approval1.5b? → approval1.5b+
Assignee | ||
Comment 4•21 years ago
|
||
checked in.
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → FIXED
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•