I want to know will builtin dll always call other builtin dll or it depends on winecfg setting just like other dll? Is it reliable that these dll mixed togther? For example, the builtin gdiplus depend on and call ole dll, does the builtin gdiplus designed to work with both builtin and native ole dll? Will there be any incompatibilities, like different memory allocator? regards,
On Wed, Mar 12, 2008 at 7:15 AM, bill lam <cbill.lam at gmail.com> wrote:> I want to know will builtin dll always call other builtin dll or it depends on > winecfg setting just like other dll?Depends on winecfg setting just like other dlls.> Is it reliable that these dll mixed > togther? For example, the builtin gdiplus depend on and call ole dll, does the > builtin gdiplus designed to work with both builtin and native ole dll? Will > there be any incompatibilities, like different memory allocator?Good question. That's why we recommend staying away from native libraries except when you absolutely need them. - Dan
bill lam skrev:> I want to know will builtin dll always call other builtin dll or it > depends on winecfg setting just like other dll? Is it reliable that > these dll mixed togther? For example, the builtin gdiplus depend on and > call ole dll, does the builtin gdiplus designed to work with both > builtin and native ole dll? Will there be any incompatibilities, like > different memory allocator?For "outer-layer" DLLs like gdiplus, this should work fine (unless there's a bug; and if, in such dlls, builtin and native don't use the same allocator, then that's a bug).