"Zebediah Figura (she/her)" zfigura@codeweavers.com writes:
On 9/1/21 2:05 AM, Alexandre Julliard wrote:
"Zebediah Figura (she/her)" zfigura@codeweavers.com writes:
On 8/31/21 2:30 PM, Alexandre Julliard wrote:
"Zebediah Figura (she/her)" zfigura@codeweavers.com writes:
On 8/31/21 1:25 PM, Alexandre Julliard wrote:
Remember that we need the libs to have custom names, to avoid conflicts with Windows apps shipping the same libs.
Yep, I've been keeping that in mind. If we want to distribute shared libraries I'm inclined to think the best solution there is to copy (or symlink, or fake-symlink) them into the prefix with different names.
This won't work for nested dependencies. For instance the PE libpng is going to import the PE zlib, so it needs to have been renamed at build time already.
Indeed; that's annoying, but thanks for pointing it out.
Note that there would also need to be some sort of DLL versioning scheme, to handle ABI changes.
As far as I understand, this is already dealt with by appending the major version number to the DLL name, e.g. "libfreetype-6.dll", or do you mean something different?
Something like that, yes. Of course there isn't necessarily a correlation between major version numbers and ABI changes...