delorie.com/archives/browse.cgi | search |
Hi! Wednesday, 24 October, 2001 Earnie Boyd earnie_boyd AT yahoo DOT com wrote: EB> Ok, for item 1 you simply EB> * mkdir /dll-1.3.3 EB> * mkdir /dll-test EB> * move /bin/cygwin1.dll to /dll-1.3.3 EB> * install your test cygwin1.dll to /dll-test EB> * cp /etc/profile /etc/profile-rls EB> * cp /etc/profile /etc/profile-test EB> * add the /dll-1.3.3 to the PATH settings in the /etc/profile-rls. EB> * add the /dll-test to the PATH settings in the /etc/profile-test. EB> * cp /cygwin.bat /cygwin-rls.bat EB> * cp /cygwin.bat /cygwin-test.bat EB> * add a copy of /etc/profile-rls to /etc/profile in the cygwin-rls.bat EB> * add a copy of /etc/profile-test to /etc/profile in the cygwin-test.bat EB> * issue - executing cygwin binaries outside of a Cygwin enabled shell. EB> * resolution - set the PATH manually before executing binaries. EB> This gives the isolation you need for the current releases of Cygwin EB> without fancy manipulations. EB> Given the simplicity of the isolation above, are differing mount tables EB> necessary? 1. somebody may want to have, say, /usr/include different across his cygwin "environments" or "profiles". 2. changing $PATH is not enough. for example, system() calls /bin/sh, and doesn't perform $PATH lookup. Egor. mailto:deo AT logos-m DOT ru ICQ 5165414 FidoNet 2:5020/496.19
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |