# [Wine] WINEPATH disappeared?

Daniel Leaberry leaberry at gmail.com
Thu Aug 3 16:07:39 CDT 2006

Thanks, we have a workaround and we're looking at perhaps adding a patch for
this.

for those interested the workaround is to create a small batch file with
these two lines.

set PATH=%PATH%;%EXPORTEDBASHVAR%;
%1

run the thing like this:

export EXPORTEDBASHVAR="z:\path\to\dll_dir_1\;z:\path\to\dll_dir_2"
wcmd /c file.bat cmd_to_exec

It works. It's not pretty but it works.

Daniel

On 8/3/06, Vincent Povirk <madewokherd+d41d at gmail.com> wrote:
>
> answers, but since you have a simple way to test it, you could do a
> "git bisect" to find the patch that caused this use of WINEPATH to
> stop working. That would at least tell you who made the change and
> give some idea of what changed and why.
>
> http://wiki.winehq.org/GitWine has instructions on doing that.
>
> On 8/3/06, Daniel Leaberry <leaberry at gmail.com> wrote:
> > Thanks for your response Vincent. Perhaps I was unclear.
> >
> > About 5 months ago I could run from a bash shell,
> > export WINEPATH="/path/to/dll_dir_1"
> > and running wcmd /c set would show that the PATH variable had the
> standard
> > c:\windows\ wine paths but it would also have the paths I set in the
> > WINEPATH variable in bash. It's this passing of the linux shell WINEPATH
> and
> > appending it to the wine WINEPATH that seems to have disappeared.
> >
> >
> > Thanks,
> > Daniel
> >
> >
>
> --
> Vincent Povirk
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.winehq.org/pipermail/wine-users/attachments/20060803/024013b9/attachment.html