Closed
Bug 918187
Opened 12 years ago
Closed 9 years ago
Exports should be done during incremental builds
Categories
(Firefox Build System :: General, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: cpearce, Unassigned)
References
Details
We seem to no longer be exporting header files when we do incremental builds. We used to do this, but now we don't. This is terrible. It means when I change a header file that's exported I need to rebuild the entire source tree before the change (or an error...) is reflected. On Windows the build is very slow, even on the best hardware that money can buy. Agonizingly slow.
Please put the export step back into incremental builds.
Comment 1•12 years ago
|
||
I guess you mean partial, not incremental, right?
| Reporter | ||
Comment 2•12 years ago
|
||
I mean `./mach build dir/dir2`, so if that means partial, sure. I'm not a build expert.
This combined with the lack of symlinks is making it impossible to do anything other than toplevel builds on windows. Can we please get this fixed?
Severity: normal → blocker
Comment 4•12 years ago
|
||
(In reply to Kyle Huey [:khuey] (khuey@mozilla.com) from comment #3)
> This combined with the lack of symlinks is making it impossible to do
> anything other than toplevel builds on windows.
That is a surprising claim, actually. Unmodified headers should be left untouched by install manifests.
Comment 5•12 years ago
|
||
(In reply to Mike Hommey [:glandium] from comment #4)
> (In reply to Kyle Huey [:khuey] (khuey@mozilla.com) from comment #3)
> > This combined with the lack of symlinks is making it impossible to do
> > anything other than toplevel builds on windows.
>
> That is a surprising claim, actually. Unmodified headers should be left
> untouched by install manifests.
Ah, the problem might be that nspr and mfbt are always new after make export...
Comment 6•12 years ago
|
||
(In reply to Mike Hommey [:glandium] from comment #5)
> Ah, the problem might be that nspr and mfbt are always new after make
> export...
as well as mozilla-config.h.
So *that* would be what to fix.
Comment 7•12 years ago
|
||
Workaround:
NO_REMOVE=1 mach build install-manifests
Comment 8•9 years ago
|
||
Marking WORKSFORME because `mach build binaries` makes this workflow reasonable.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WORKSFORME
Updated•8 years ago
|
Product: Core → Firefox Build System
You need to log in
before you can comment on or make changes to this bug.
Description
•