[Wine] Native and Builtin dll

James Mckenzie jjmckenzie51 at earthlink.net
Thu Jul 24 14:56:10 CDT 2008


Vitally:

Good explanation.  Is this not covered in a FAQ on the Wine HQ site?

James McKenzie

vitamin on Jul 24, 2008 12:44 PM (MST) wrote about Native and Builtin dll:
>
>
>Batt212 wrote:
>> Ok, I didn't write bad my question. If I've source code for an dll I can produce a builtin dll (with winelib) 
>
>Not correct. Wine built-in dlls are those dlls that are part of Wine itself. Everything else is a native DLL.
>
This should also be expanded to state:

Any dll that is a part of the Wine package is a built-in dll.  Substitution with a dll that is part of any Windows distribution is considered a native replacement.  Installation packages may also install dlls in the installation directory.  These are also considered native dlls.
>
>Batt212 wrote:
>> but if I dot not have it I must use only native dll.
>
>If Wine doesn't have such dll, then yes you have to use native dll instead.
>
Correct.  Wine does not, at this time, include all of the dlls distributed with Windows or any installation product.  Windows does not ship with some dlls, such as the Visual C++/Visual C#/Visual J# dlls.  These dlls are normally included with the product as part of the installation package.
>
>Batt212 wrote:
>> For example I copy and paste an exe file into linux enviroment and run it.
>
>Not correct. You don't copy anything. Most programs have to be properly installed with their installer. This is true even on windows.
>
This really needs to be pointed out.  You CANNOT just copy a program from a Windows installation to a Wine installation.  You CANNOT just point to your Windows Program Files directory and run a program from there.  And lastly you CANNOT just overlay a Wine installation with a Windows installation for many reasons, the main one is that you will break Wine and prevent it from running.
>
>Batt212 wrote:
>>  Why cannot I take iexplorer.exe and its dlls and run it?
>
>This is special case. IE is a part of the system and depends on big number of undocumented functions. And to run it you have to replace big parts of Wine. This is strongly discouraged. Especially in this case, since Wine has it's own IE replacement.
>
You can try to use ies4linux/ies4MacOSX to run IE.  However, unless you really require IE functionality, use FireFox instead.




More information about the wine-users mailing list