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

Matthew Bogosian mattb@columbia.edu
Wed Feb 9 01:51:00 GMT 2005


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Howdy all,

I've searched through the archives on this, but I've come up empty, so 
I figured I'd ask....

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.

Before someone suggests the obvious, I am using Cygwin and bash (etc.) 
as a test harness for a binary I'm writing. I may test several 
different versions of the binary on the same machine. The DLLs cannot 
reside in c:\windows\..., nor can they reside in the same directory as 
binary.exe because binary.exe is actually c:\Python24\python.exe and 
the DLLs are from different versions of a third-party SDK that I'm 
accessing via swig/python. In short, I need to be able to override 
where the DLLs are found by the cygwin-ignorant version of Python in a 
shell script on an ad hoc basis.

Please don't tell me to use Cygwin's python either, since I have to 
test the Windows version using the same test harness.

Does anyone know how to do this? Any help is much appreciated.

	-- Matt

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

iD8DBQFCCUCMnLpDzL5I7l8RAu0hAJwKF4C/6vyb/lJNLc8Ml5lDj/tRawCeIxrb
xVavIVr4YXHG29NeTJZdnSQ=
=yoUB
-----END PGP SIGNATURE-----


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/



More information about the Cygwin mailing list