This is the mail archive of the cygwin mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Setting the Windows Path variable for children of a bash script....

Hash: SHA1

Okay, I could have *sworn* I tried that before and it didn't work, but I tried it again, and it seems to be exactly what I wanted/hoped for. Ugh...sorry for the unnecessary traffic and thanks for the quick response!

-- Matt

On Feb 8, 2005, at 15:07, Igor Pechtchanski wrote:

On Tue, 8 Feb 2005, Matthew Bogosian wrote:


I'm trying to execute a cygwin-ignorant Windows binary from a bash script.
However, the DLLs required to load this binary are not in the system- or
user-wide Windows Path variable (nor do I want them to be). I'm trying to
modify the environment before execution of this binary, but it doesn't seem to
work. Here's what I've got:

# ...
Path="$(cygpath -pw "${PATH}");$(cygpath -pw "${LD_LIBRARY_PATH}")"
export Path
exec /cygdrive/c/path/to/windows/binary.exe

LD_LIBRARY_PATH contains the paths in which the DLLs specific to binary.exe
reside. Unfortunately, binary.exe doesn't seem to be able to find them there
when being invoked from the script's exec command.


PATH="${PATH}:${LD_LIBRARY_PATH}" export PATH exec /cygdrive/c/path/to/windows/binary.exe

The "PATH" variable is treated specially by Cygwin and is translated from
POSIX path format to Windows path format when calling Windows programs.
In your first case it was doing the translation twice, so C:\WINDOWS
became C;C:\WINDOWS.

-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (Darwin)


-- Unsubscribe info: Problem reports: Documentation: FAQ:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]