Closed
Bug 521674
Opened 15 years ago
Closed 9 years ago
manifest file not rebuild
Categories
(Thunderbird :: Build Config, defect)
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: joachim.herb, Unassigned)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; de; rv:1.9.1.3) Gecko/20090824 Firefox/3.5.3 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.5pre) Gecko/20091011 Shredder/3.0pre ID:20091011191540 As described in Bug 519956 comment #20 and in this thread http://forums.mozillazine.org/viewtopic.php?f=29&t=1529715&p=7723775#p7723775 rebuilding the sources of Thunderbird after changing the content of the jar.mn file in the directory mail/base/ does not correctly rebuild the file messenger.manifest in /obj/mozilla/dist/bin/chrome Reproducible: Always Steps to Reproduce: 1. Build the unmodified source: The icons in the customization dialog of the main tool bar are displayed correctly. 2. Build the source including the problematic line in the jar.mn(see first message). The icons are broken. 3. Remove the line in jar.mn again and rebuild. The icons are still broken. Actual Results: During the first build the file obj/mozilla/dist/bin/chrome/messenger.manifest is created. Of course it does not contain a reference to messageHeader.css. This file (messenger.manifest) is changed during the second build. Now it includes a reference to messageHeader.css. After the third build the file still contains the reference to messageHeader.css despite the fact, that the file jar.mn does not contain the corresponding line. In fact, the content of the file is the same as after the second build (the file date and time has changed). Expected Results: The messenger.manifest is rebuild correctly.
Reporter | ||
Comment 1•15 years ago
|
||
I am using the separate shared libraries build options (https://developer.mozilla.org/en/Configuring_Build_Options#Statically_Linking_Components).
Updated•9 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 9 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•