Closed
Bug 452760
Opened 16 years ago
Closed 16 years ago
relative l10n-base problems with comm-central
Categories
(MailNews Core :: Build Config, defect)
MailNews Core
Build Config
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: kairo, Assigned: kairo)
Details
Attachments
(1 file)
|
818 bytes,
patch
|
standard8
:
review+
|
Details | Diff | Splinter Review |
If we specify a relative dir for l10n-base on comm-central, we run into a failure because it would need to be a different relative path for the embedded mozilla-central. This can be solved easily by forwarding an absolute path for our configure to the mozilla configure.
|
Assignee | |
Comment 1•16 years ago
|
||
This forwards the absolute path we keep internally anyway to the mozilla configure if an l10n-base is set. (This patch is the only one so far I needed to get a locale build factory working, the rest is all buildbot stuff for now!)
Attachment #336034 -
Flags: review?(bugzilla)
|
||
Updated•16 years ago
|
Attachment #336034 -
Flags: review?(bugzilla) → review+
|
|
||
Comment 2•16 years ago
|
||
Comment on attachment 336034 [details] [diff] [review] forward the absolute path to mozilla configure I've been testing with an absolute path up until now, otherwise I'd have probably seen it earlier.
|
|
Assignee | |
Comment 3•16 years ago
|
||
pushed as http://hg.mozilla.org/comm-central/rev/92b407424302
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
|
|
Assignee | |
Updated•16 years ago
|
Product: SeaMonkey → MailNews Core
QA Contact: build-config → build-config
You need to log in
before you can comment on or make changes to this bug.
Description
•