Closed
Bug 191927
Opened 22 years ago
Closed 22 years ago
incorrect build order for statically linked TestGtkEmbed
Categories
(SeaMonkey :: Build Config, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: bryner, Assigned: bryner)
Details
Attachments
(1 file)
1.56 KB,
patch
|
netscape
:
review+
asa
:
approval1.3b+
|
Details | Diff | Splinter Review |
In a static build, we link all of the components into the library created in embedding/browser/gtk/src. However, not all of the components we want to link in have been built at the time this directory is traversed. Because of the way the Makefile in that directory works, it won't cause a build failure, it will just silently skip linking in some of the components.
Comment 1•22 years ago
|
||
Looking at this closer, I'm not even sure if this is an issue. embedding/browser/gtk/src/Makefile.in creates a static library. So in a static build, those extra components that we depend upon never show up in the link (ar cr) line at all anyway. Ok, I see the real problem. The component names are used to create the entrypoints in EmbedComponents.cpp. The initial list of component names are grabbed from embedding/config/basebrowser-unix but only the names that actually show up in the generated FINAL_LINK_COMPS list are actually used by EmbedComponents.cpp. And since someone decided to add various add-on bits like psm & wallet to basebrowser-unix, gtkembedmoz misses out on them.
Assignee | ||
Comment 2•22 years ago
|
||
Assignee | ||
Updated•22 years ago
|
Attachment #113542 -
Flags: review?(seawood)
Comment 3•22 years ago
|
||
Comment on attachment 113542 [details] [diff] [review] patch r=cls
Attachment #113542 -
Flags: review?(seawood) → review+
Assignee | ||
Updated•22 years ago
|
Attachment #113542 -
Flags: approval1.3b?
Comment 4•22 years ago
|
||
Comment on attachment 113542 [details] [diff] [review] patch a=asa.
Attachment #113542 -
Flags: approval1.3b? → approval1.3b+
Assignee | ||
Comment 5•22 years ago
|
||
checked in.
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•