| 1 | | The GHC folks are also looking into this stupid problem: http://blog.omega-prime.co.uk/?p=138 describes a nasty undocumented feature which can't be scripted AFAICT. On https://ghc.haskell.org/trac/ghc/wiki/DynamicByDefault/Windows there's some more information on how to fix linking on Windows. The "side by side" assembly stuff sounds promising, but I haven't found any docs that are actually human-readable enough to figure out how to make use of this. |
| | 1 | The GHC folks are also looking into this stupid problem: [http://blog.omega-prime.co.uk/?p=138 This blog post] describes a nasty undocumented feature to allow absolute paths instead of plain DLL names, but it can't be scripted AFAICT. On [https://ghc.haskell.org/trac/ghc/wiki/DynamicByDefault/Windows the GHC wiki] there's some more information on how to fix linking on Windows. The "side by side" assembly stuff sounds promising, but I haven't found any docs that are actually human-readable enough to figure out how to make use of this. |
| | 2 | |
| | 3 | I've also read that there's [http://www.codeguru.com/cpp/w-p/dll/article.php/c99/Application-Specific-Paths-for-DLL-Loading.htm application-specific DLL path support] but that requires messing about with the Registry, which means installation/uninstallation is no longer simple. |
