Hello,
When you open the Wine configuration, you will find a list of DLL's in the Libraries tab.
My question refers to this list. So not on what you have already selected, but on what is available for selection.
I have compared 3 lists of different winecfg from different wine-prefixes.
https://www.bilder-upload.eu/bild-8961d ... 4.png.html
winecfg 4.1:
This is from a 7-Zip installation I made with PlayOnLinux.
winecfg 5.6:
This is from a Wine installation without any software installed.
winecfg 4.12
This is from a Visio installation that I did with crossover.
What is interesting: There are differences in the lists of available DLL's.
I assume that the only reason for the differences is the Wine version; and the programs installed in the corresponding prefixes have no influence.
It is interesting to note that Wine 5.6 has significantly fewer DLL's in the list. You can see that ...
1. at the scrollbar, because the middle bar is longer in version 5.6 than in version 4.1 and...
2. you can see that the 10th entry of 4.1 is already missing in 5.6. So there are more entries in the list in 4.12 than in 5.6.
Question: Why is that so?
As wine is always being developed: Shouldn't then be more and more DLL's been added with each new wine version?
Confused. Thank you.
winecfg: tab libraries. Differences between wine-versions
Re: winecfg: tab libraries. Differences between wine-versions
It looks like all the api-ms-* ones were removed at some point, apparently they weren't useful? But that's a big chunk of missing ones. I think winecfg (at least the current version) just looks at the wine dll directory/ies and excludes some.
Re: winecfg: tab libraries. Differences between wine-versions
Thank you. I had now a closer look at it.
And I found now in wine 5.6 this:
https://www.bilder-upload.eu/bild-2f86b ... 8.png.html
-> So the api-ms-* are in fact there. So it seems your assumption is right, that the current wine versions do exclude some dll's.
So this means, when I am searching a dll in the list of available dll's and the dll is not there, it can be, that this dll is nevertheless able as a wine-self-made-version.
I am confused. The rule: All wine-self-made dll's are in this list seems to be wrong.
So in which case is a dll in the list of selectable dll's and when not? What is the rule?
Thank you.
And I found now in wine 5.6 this:
https://www.bilder-upload.eu/bild-2f86b ... 8.png.html
-> So the api-ms-* are in fact there. So it seems your assumption is right, that the current wine versions do exclude some dll's.
So this means, when I am searching a dll in the list of available dll's and the dll is not there, it can be, that this dll is nevertheless able as a wine-self-made-version.
I am confused. The rule: All wine-self-made dll's are in this list seems to be wrong.
So in which case is a dll in the list of selectable dll's and when not? What is the rule?
Thank you.
Re: winecfg: tab libraries. Differences between wine-versions
I was looking here: https://source.winehq.org/git/wine.git/ ... ies.c#l212
It looks like the api-ms-whatever are excluded and another list of dlls defined further up are excluded as well: is_builtin_only()
It looks like the api-ms-whatever are excluded and another list of dlls defined further up are excluded as well: is_builtin_only()
Re: winecfg: tab libraries. Differences between wine-versions
Thank you for the link. We're getting closer and closer.
So when I understand right, the rule is:
So when I understand right, the rule is:
- Only dll's built from wine itself are offered in the drop-down list. (Original windows dll's that are in the prefix are never offered.)
and - Dll's from wine itself, that should never be set to "native", but always should be builtin are not offered in the drop-down list.
