See #43895 for more info.
Keywords: arch, embed, nsbeta2
*** Bug 44091 has been marked as a duplicate of this bug. ***
the only places we should be linking against rdf are msgbaseutil and address book - Adding putterman to CC so he can verify my claim. Also adding ducarroz to the CC because I will need his help with the mac
Status: NEW → ASSIGNED
Target Milestone: --- → M17
as long as it builds there's no reason why we need to do this.
I'm not sure how mail/news is built out, but we definately want to minimize these static links (on a module level) from a footprint/bloat standpoint. Does all of mail/news build into a single shared lib?
sorry, my comment was meant to be that as long as we build without linking against this library then making this change is fine. I haven't tried it and for all I know that could be leftover from when we did need to link against it.
ok, so it looks like either we have to figure out how to re-export nsRDFResource from msgbaseutil.dll, or make msgbaseutil a static library itself (which I'm beginning to think is The Right Thing anyway)
jud this is turning out to be a whole lot more work than we thought at first. I'd like to take this off the nsbeta2 train... the rdf library we're linking to is VERY small (my DEBUG version is 41k) - we're not linking against RDF itself, just a static utility library.
On Mac, we are not linking against RDF. However, we are including nsRDFResources.cpp directly into the Mac project and we are also linking against MsgUtil.lib (as static)
ok, sounds like mac is doing the right thing.
mail news actually isn't even part of our current embedding solution, yanking from beta2
moving to future.
Target Milestone: M17 → Future
I'm marking WONTFIX. We can get past this by switching to resource delegates, but I think putterman already has a bug on this.
Status: ASSIGNED → RESOLVED
Last Resolved: 18 years ago
Resolution: --- → WONTFIX
Can someone verify this?
AFAIK, the new outliner code doesn't use any (or much) RDF in the thread pane (we still use it in the folder view). But based on the comments in this bug, verified.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.