Re: How to get the application path

[development-2006-8ecbb5cc8aREMOVETHIS@ANDTHATm-e-leypold.de (Markus E.L.)]

> Markus E Leypold <development-2006-8ecbb5cc8aREMOVETHIS@ANDTHATm-e-leypold.de> writes:
>
>> Now, on Unix I'd just put a shell script wrapper in place of the executable:
>
> Why do you limit this to "Unix"? Any operating system that supports
> shells can do the same thing. 

Yes+No. In Unix I can just exec the real binary, so I don't have a
shell process waiting until the the binary proper returns. In Windows
the shell process will (AFAI understand it) exist until the
application terminates and AFAIS (worse) it will even have a command
line window open to the absolute irritation of the lay user. 

If I do the right things (use start.exe, for once) the shell window
will open only shortly, but will still irritate the user.

I find the Unix way more palatable.

>>    MYPATH="$0"
>>    MYAPP="$(which $MYPATH.bin)"  # locate the executable proper
>>
>>    export EXE_PATH="$MYPATH"
>>
>>    exec $MYAPP "$@"
>>
>> (untested, mind you).
>>
>> That would even put the full path in argv[0]. The power of shell
>> script wrappers in Unix is usually underestimated.
>
> Scratch the "in Unix", and I agree.

Could you tell me the equivalent of my script in CMD.exe? (Seriously,
that's a real question: What I got until now I consider kludgy).

> A Windows icon can launch a cmd shell wrapper. Or a Cygwin bash
> wrapper, for that matter!

Yes, but cygwin has problems of its own (security for once, it's
rather intrusive), so it's not OK in my opinion to run it at end user
machines (at least w/o much further research to be done which is a bit
difficult given the general attitude ("BWAM") at the cygwin mailing
lists :-(.)


Regards -- Markus