override with native, builtin

bill lam · Post by **bill lam** » Tue Mar 11, 2008 8:38 pm

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,

Dan Kegel · Post by **Dan Kegel** » Tue Mar 11, 2008 9:03 pm

On Tue, Mar 11, 2008 at 6:38 PM, bill lam <[email protected]> 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

L. Rahyen · Post by **L. Rahyen** » Tue Mar 11, 2008 9:04 pm

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.

bill lam · Post by **bill lam** » Tue Mar 11, 2008 9:29 pm

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,

James McKenzie · Post by **James McKenzie** » Tue Mar 11, 2008 9:57 pm

bill lam wrote:

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,

Bill:

When you set [native]. However, if the program CANNOT find the .dll or
a function in the .dll, wine will become 'sour' and the program will
stop working.

James McKenzie

bill lam · Post by **bill lam** » Tue Mar 11, 2008 10:39 pm

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?

Dan Kegel · Post by **Dan Kegel** » Tue Mar 11, 2008 10:53 pm

On Tue, Mar 11, 2008 at 8:38 PM, bill lam <[email protected]> wrote:

I still not yet fully understand override. Does the override operate on "per
file" or "per api" base?

Per DLL file. I'm pretty sure.

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?

No, it's all or nothing.
- Dan

L. Rahyen · Post by **L. Rahyen** » Tue Mar 11, 2008 10:55 pm

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.