On 2002.02.25 15:05 Andreas Mohr wrote:
On Mon, Feb 25, 2002 at 11:47:31AM -0800, Alexandre Julliard wrote:
Andreas Mohr andi@rhlx01.fht-esslingen.de writes:
Maybe we should use libwinecore_XXX.so and libwinedll_XXX.so for the naming scheme. That'd be pretty reasonable and cleaner/better than the current approach IMHO, as it'd clearly separate core/dll
functionality
in a good way.
The separation will be done by putting dlls in a separate directory (usually /usr/lib/wine) which is a lot cleaner than creating 150 files in /usr/lib, no matter how they are named.
But some people DON'T separate it. (for various reasons, which might only be evident in the future)
Furthermore, having tons of hopelessly chaotically named libraries is everything but clean.
Andi... if Wine DLLs eventually go into a /usr/lib/wine then you cannot possibly argue that anybody in their right mind would put them in /usr/lib. I don't see any distributors putting the libraries in /usr/lib/xmms/* into /usr/lib, do you?
Wine dll path won't be added to /etc/ld.so.conf. But in any case the plan is that dlls in /usr/lib/wine are named without the lib prefix to make it clear you can't link to them.
Fact is that a LOT of people/distributors still add it to ld.so.conf.
We are not talking about libraries that people would want to link to in the normal UNIX sense. We are basically talking about what amounts to "plugins" for the wine emulator (in some sense). Therefore when wine is able to load the DLLs from a specific wine library directory then nobody is going to install them into /usr/lib, if they do then that is their own damn problem for being stupid.
Anyway, I didn't know about the "omit lib" plan yet. That'd actually be a rather usable choice, since that'd really eliminate the conflicts.
But are you sure that you can just omit the lib prefix on *all* supported environments ?
Does it really matter? If they are in a seperate plugins type directory then who cares if the "lib" is ommitted or not.
-Dave