Re: wine/ libs/wine/loader.c libs/wine/config.c in ...
I have some code that can figure out the absolute address of the binary by either: a) Looking for itself in /proc/self/maps ... or b) using r_map and /proc/self/exe I dunno how Linux specific this is, but it works pretty well and lets you make a relocatable binary every time. Would this be an acceptable 2nd implementation for init_argv0_path() that works when wine is invoked from the path also? On Tue, 07 Oct 2003 19:36:09 -0500, Sir Alexandre Julliard scribed thus:
http://cvs.winehq.com/patch.py?root=/home/winehq/opt/cvs-commit&id=9669
Mike Hearn <mike(a)theoretic.com> writes:
I dunno how Linux specific this is, but it works pretty well and lets you make a relocatable binary every time. Would this be an acceptable 2nd implementation for init_argv0_path() that works when wine is invoked from the path also?
I don't think that's needed, we only use argv0 to execute the wine binaries anyway, and we already look in the path for them. -- Alexandre Julliard julliard(a)winehq.com
participants (2)
-
Alexandre Julliard -
Mike Hearn