We have a directory called content/shared that both content and layout link against. The problem is that this directory has been growing ever since the split. More and more of the deCOMification work that we do will involve a need to get to the implementation of some deCOMified class from both DLLs.
If we don't re-merge the DLLS, then we'd end up linking against an ever-growing content/shared, and we'd end up with duplicated code in the layout and content DLLs. Our code footprint has already increased because of content/shared, and if we don't remerge, that problem is just going to get worse. Dave ([EMAIL PROTECTED]) Axel Hecht wrote: > Hi, > all we need AFAICT is having link time dependencies between layout and > content? Why not introduce them, but keep the dynamic libraries > separate? > (Consider that I'm not really knowing what happens if you have both > dynamic linking deps and xpcom loading a lib, and circular link > dependencies). > > Of course this link dependency would only harm those, that need to > access non-XPCOM interfaces. > > Axel >
