http://bugs.winehq.org/show_bug.cgi?id=25044
--- Comment #15 from Alexandre Julliard julliard@winehq.org 2010-11-11 07:13:22 CST --- (In reply to comment #14)
Who says so? If the app uses its path to locate files, then it makes sense that the behavior would be different if the launch path is different.
You are still not understanding the main issue: the launch path is different both when using the full path to the exec (no crash) and when using the symlink (crash).
If the program would use the launch path then also the non-symlink variant would crash, wouldn't it?
No, what matters is not the path you specify on the command line, it's where the binary was loaded from. If you use a symlink then the binary is loaded from a different directory, and that's the path that the app gets. It's the same on Windows.
Please don't reopen unless you can demonstrate that the app works fine on Windows when started through a symlink.
Using mklink on Windows 7 does not cause a crash when loading the DLL:
C:>mklink heidi.exe "c:\Program Files (x86)\HeidiSQL\heidisql.exe" symbolische Verknüpfung erstellt für sex.exe <<===>> c:\Program Files (x86)\HeidiSQL\heidisql.exe C:>heidi
That's interesting. It will need some test cases to find out if Windows handles symlinks specially for dll loading.