3 ms·
So you are saying this is why Windows users universally complain about "DLL Hell", and Linux users don't? Or is this how MS finally fixed Windows DLL Hell? (Pre
by ncmncm 5y ago
So you are saying this is why Windows users universally complain about "DLL Hell", and Linux users don't? Or is this how MS finally fixed Windows DLL Hell? (Presuming Windows DLL Hell is, indeed, fixed; I wouldn't know.)
- Dylan16807 5y agoLibraries in the program install folder completely bypass dll hell. It's the original fix!
- pjmlp 5y agoSo much that it has the code name of xcopy deploy, an alusion to how MS-DOS applications used to be delivered. However there is also the WinSxS alternative, adding a manifest file to the executable.
- pjmlp 5y agoIt is fixed since ages, more precisely since Windows 2000. https://en.wikipedia.org/wiki/Side-by-side_assembly https://en.wikipedia.org/wiki/Side-by-side_assembly
- kazinator 5y agoDLL hell is about program installers depositing some common libraries, like the MSVC redistributable run-time, into the system folder. So then every other application is using the most recently clobbered version of it instead of the one it came with. GNU/Linux doesn't have DLL hell only to the extent that there is an entire binary distro with maintainers beavering to keep all of the dependencies straight so that every program that needs a certain shared library is maintained to need the same version of it as any other program. You will experience shared library hell as soon as you have your own binary application that is not in the upstream distro, and it happens to depend on one of the lesser libraries that do not do symbol versioning like openssl, libbz2 and whatnot. I've dealt with this plenty in more than one Linux embedded dayjob. In one case, I hacked an elaborate library searching system around dlopen() into such a program.