Closed
Bug 645166
Opened 14 years ago
Closed 13 years ago
Use mozconfig option to trigger PGO builds instead of profiledbuild target
Categories
(Release Engineering :: General, defect, P5)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 658313
People
(Reporter: glandium, Unassigned)
References
Details
(Whiteboard: [mozconfig][simple])
With bug 643704, we added support for a mozconfig option to trigger PGO builds. This also means that the converse, disabling PGO, is also possible through mozconfig... but not while buildbots call the profiledbuild target of client.mk.
The build target should be called like on other non PGO builds, and the following added to windows mozconfigs:
mk_add_options MOZ_PGO=1
This has only landed on m-c so far, but we'll likely want to get this on stable branches as well.
Comment 1•14 years ago
|
||
Is it possible to have profiledbuild be a no-op target that depends on build until this is landed on all stable branches?
something like
.PHONY: profiledbuild
profiledbuild: build
@echo using make -f client.mk profiledbuild is deprecated
Reporter | ||
Comment 2•14 years ago
|
||
The profiledbuild target is still used to to the actual work.
The build target either calls profiledbuild or realbuild depending on that MOZ_PGO variable. And profiledbuild calls realbuild twice.
Updated•14 years ago
|
Priority: -- → P5
Whiteboard: [mozconfig][simple]
Comment 3•13 years ago
|
||
This is a very small subset of the work happening in bug 658313
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
Assignee | ||
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•