Open
Bug 1095256
Opened 10 years ago
Updated 2 years ago
Deleting an entry from EXTRA_JS_MODULES doesn't delete it from the obj. directory
Categories
(Firefox Build System :: General, defect)
Firefox Build System
General
Tracking
(Not tracked)
NEW
People
(Reporter: MattN, Unassigned)
Details
I deleted a file from EXTRA_JS_MODULES in bug 1091260 but the file was still being installed in the modules directory without a clobber. The file was still referenced from jar.mn but I made it require pre-processing. See bug 1095234.
Comment 1•10 years ago
|
||
IIRC how this all works, this is because EXTRA_JS_MODULES use install manifests and install manifests don't actually track what used to be installed but is not anymore. gps tell me if I'm wrong.
Flags: needinfo?(gps)
Comment 2•10 years ago
|
||
EXTRA_JS_MODULES uses INSTALL_TARGETS.
Comment 3•10 years ago
|
||
Ah yes, it only uses install-manifests for tests. So that should be fixed by moving EXTRA_JS_MODULES to install manifests, and I think there's an existing bug for that.
Flags: needinfo?(gps)
Comment 4•10 years ago
|
||
It appears not, but it's kind of a sibling of bug 1058051.
Comment 5•10 years ago
|
||
We can't move EXTRA_JS_MODULES into install manifests until $(FINAL_TARGET) is fully supported in moz.build. And that requires the XPI_NAME= $(MAKE) -C invocations to die.
Updated•7 years ago
|
Product: Core → Firefox Build System
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•