fcmartins wrote: > Thanks, out of curiosity, how does wine provide its dlls? As native ELF libraries with extra Wine-specific data. For apps they look exactly as regular windows dlls (otherwise many programs won't work). Unless you know how loader works it's useless to explain you how Wine does it. All you need to know: - Only the whole dll can be overridden (not per/function as you implied) - Depending on override order whole built-in or native dll is loaded (but not both at the same time) - Wine builtin dlls located outside of wineprefix (~/.wine). All you see in system32 are "placeholder dlls" - resources only
