Wine's path VS host path

[lawson_whitney at juno.com]

On Thu, 14 Feb 2002, David D. Hagood wrote:

> The project is a rather large one, comprised of over 9000 files in many
> different directories. Having the tools always in CWD isn't an option.
>
Well, maybe I am stupid, but I don't see why you can't just install the
tools somewhere, and add the windows path to that somewhere to Wine's
"Path" =
and be done with it.  Unless the leafnames of the tools have different
meanings depending where they are called from, and they are called only
by leafname, that should about do it.  You mentioned binfmt_misc, and
GNU make, IIRC, so maybe what you miss is that you can always call an
executable by absolute or relative pathname as well as by leafname; if
called by leafname from *NIX, it will be searched for in the *NIX path,
and the wine path doesn't matter.  If it is not any other kind of
executable, and binfmt_misc finds it to be a wine executable, it will
call on wine to execute it, and IIRC it will give Wine the absolute path
to find it by.  What exactly is the problem?  :-)

Lawson

Probable user head space error. - Dennis A. Moore