I would like to know if there is any difference between [native] and [native,builtin]? Is there any function that native dll missing and need builtin version to step in? regards,
On Tue, Mar 11, 2008 at 6:38 PM, bill lam <cbill.lam at gmail.com> wrote:> I would like to know if there is any difference between [native] and > [native,builtin]? Is there any function that native dll missing and need builtin > version to step in?[native,builtin] is less likely to kill you if you happen to be missing the dll in question. (This might be handy while running a complex installer than can limp by with Wine's version of a dll initially but needs the real one before it's done.) - Dan
On Wednesday March 12 2008 01:38:24 bill lam wrote:> I would like to know if there is any difference between [native] and > [native,builtin]?[native] means if there is no native library in the path and an application you trying to launch need it - it will just fail. [native,builtin] means if there is no native library in the path try to use builtin one. The default is [builtin, native] for all dlls - that is, first try to load builtin dll and if this fails try to load native one.
L. Rahyen wrote:> The default is [builtin, native] for all dlls - that is, first try to load > builtin dll and if this fails try to load native one.Thank Dan & Rahyen for response. With a working wine installation, when will builtin dll be not available? regards,
On Wednesday March 12 2008 03:38:57 bill lam wrote:> Thanks James. > I still not yet fully understand override. Does the override operate on > "per file" or "per api" base? > Eg. override with [builtin, native] > if both builtin and native dll are there, but one api is missing in > builtin, will that api from native dll be called, while other api still > from builtin?overrides are just an order in which WINE tries to load dlls and which ones it should try to load - native, builtin or both. If important api is missing in already loaded dll, - no matter builtin or native one, - then application will probably crash.