Having one component linked against one vendor's run time library and another component linked against yet another vendor's run time library could make life interesting. Yeah, I know NSPR is supposed to protect us from this but I'd be much more comfortable supporting an installation whose pieces were all built with the same compiler. Beyond that everything should work since XPCOM is interface based and requires DLLs to export a small number of C functions. As Ari points out, everything else is pointers and vtables so there's nothing for a linker/loader to resolve. Ari Heitner wrote: > Isn't the point of COM (and XPCOM) to avoid this nonsense? > > It should work just fine, since all objects in mozilla are XPCOM objects. > > ari
- Re: Building Mozilla under GCC/free compiler on Win32 Valeri Todorov
- Re: Building Mozilla under GCC/free compiler on Win32 Rick Parrish
- Re: Building Mozilla under GCC/free compiler on Win32 Ari Heitner
- Re: Building Mozilla under GCC/free compiler on Win32 Valeri Todorov
- Re: Building Mozilla under GCC/free compiler on Win32 Ari Heitner
- Re: Building Mozilla under GCC/free compiler on Win32 Ken Kozman
- Re: Building Mozilla under GCC/free compiler on Win32 Ari Heitner
- Re: Building Mozilla under GCC/free compiler on Win32 Ken Kozman
- Re: Building Mozilla under GCC/free compiler on Win32 Ari Heitner
- Re: Building Mozilla under GCC/free compiler on Win32 Valeri Todorov
- Re: Building Mozilla under GCC/free compiler on Win32 Valeri Todorov
- Re: Building Mozilla under GCC/free compiler on Win32 Ken Kozman
