[Bug 16246] New: Setting WINEPATH has no effect.

[wine-bugs at winehq.org]

http://bugs.winehq.org/show_bug.cgi?id=16246

           Summary: Setting WINEPATH has no effect.
           Product: Wine
           Version: 1.1.9
          Platform: PC
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: kernel32
        AssignedTo: wine-bugs at winehq.org
        ReportedBy: aziz.koeksal at gmail.com


Hi,

The following doesn't work as expected:

$ export WINEPATH="C:\dir"
$ printenv | grep WINEPATH # Check if it's in the shell's environment.
WINEPATH=C:\dir
$ wine ./environment.exe # E.g.: printf("PATH=%s", getenv("PATH"));
PATH=C:\windows\system32;C:\Windows

I expect that by defining WINEPATH it would get appended to PATH. I also expect
wine to search in WINEPATH folders to locate a command, e.g. "wine
compiler.exe".
Before filing this report I did some research into this, and apparently there
has been only one person so far who complained about this feature not working
anymore (http://www.winehq.org/pipermail/wine-users/2006-August/023179.html).
I have also browsed the source code, and found the following identifiers that
should be of interest:

http://source.winehq.org/ident?i=__wine_main_environ
http://source.winehq.org/ident?i=build_initial_environment

I could help debugging this, but only if someone guided me through setting up
everything that is required to debug wine in a graphical and sane environment.


-- 
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.