Thanks, we have a workaround and we're looking at perhaps adding a patch for this. <br><br>for those interested the workaround is to create a small batch file with these two lines.<br><br>set PATH=%PATH%;%EXPORTEDBASHVAR%;
<br>%1<br><br>run the thing like this:<br><br>export EXPORTEDBASHVAR="z:\path\to\dll_dir_1\;z:\path\to\dll_dir_2"<br>wcmd /c file.bat cmd_to_exec<br><br>It works. It's not pretty but it works.<br><br>Daniel<br><br>
<br><div><span class="gmail_quote">On 8/3/06, <b class="gmail_sendername">Vincent Povirk</b> <<a href="mailto:madewokherd+d41d@gmail.com">madewokherd+d41d@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Well, I don't know a thing about this and can't really give you any<br>answers, but since you have a simple way to test it, you could do a<br>"git bisect" to find the patch that caused this use of WINEPATH to<br>
stop working. That would at least tell you who made the change and<br>give some idea of what changed and why.<br><br><a href="http://wiki.winehq.org/GitWine">http://wiki.winehq.org/GitWine</a> has instructions on doing that.
<br><br>On 8/3/06, Daniel Leaberry <<a href="mailto:leaberry@gmail.com">leaberry@gmail.com</a>> wrote:<br>> Thanks for your response Vincent. Perhaps I was unclear.<br>><br>> About 5 months ago I could run from a bash shell,
<br>> export WINEPATH="/path/to/dll_dir_1"<br>> and running wcmd /c set would show that the PATH variable had the standard<br>> c:\windows\ wine paths but it would also have the paths I set in the<br>> WINEPATH variable in bash. It's this passing of the linux shell WINEPATH and
<br>> appending it to the wine WINEPATH that seems to have disappeared.<br>><br>><br>> Thanks,<br>> Daniel<br>><br>><br><br>--<br>Vincent Povirk<br></blockquote></div><br>