mine, which otherwise works just fine for me. Possibly they looked for cygwin1.dll in a specific place, possibly they tried to use PATH. I don't know. Anyway, they left me with multiple cygwin1.dll's so nothing worked at all until I tore them out by the roots.
OK, that may be the packagers problem, not ours. However, I'm wondering if we could make it easier? How about storing /HKLM/Cygnus Solutions/Cygwin/DLL_PATH="native:/path/to/cygwin1.dll and
/HKLM/Cygnus Solutions/Cygwin/DLL_VERSION="1.2.3"
And providing a simple C routine to return the critical information. I'm less sure about this piece -- most use things like InstallShield and I don't know how the scripting works there. Of course, if they simply looked at the mount point /HKLM/Cyg.../Cygwin/mounts_v2/bin, they could work it all out!!!
-- David A. Cobb, Software Engineer, Public Access Advocate "By God's Grace, I am a Christian man; by my actions a great sinner." -- The Way of a Pilgrim: R.French, Tr. Life is too short to tolerate crappy software!
-- 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/
