7 Jan
2009
7 Jan
'09
7:31 a.m.
Vitaliy Margolen <wine-devel(a)kievinfo.com> writes:
Alexandre Julliard wrote:
The problem is not Unix paths, it's usually that the app expects the current directory to be the app directory. You have the same issue if you use a Windows path. If there are really issues caused by argv[0] being a Unix path and not just the wrong directory that can be fixed.
For years Borland been stating in their documents that argv[0] always contains full path to the executable. And many programs written in Boarland C++ / Delphi relay on that.
Their documents are wrong since argv[0] is determined by the parent process. Anyway, do you have a specific bug report for this? -- Alexandre Julliard julliard(a)winehq.org