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]

resolving directories


In a recent comedy of errors, I moved an executable from one machine
to another. I was at least bright enough to move its associated .dll
and even the .a for good measure. Not to surprisingly this did not
result in a working program. After some thought I determined that the
difference from one cygwin environment to another was the problem.
Given a two year difference this seemed like the culprit.
Unfortunately now is not a good time to upgrade the target machine, so
I cheated and copied the first machines cygwin1.dll (isolated in the
same directory along with the executable) to the second machine---
happiness ensued! Sort of. My executable while it worked, was unable
to resolve a simple path like /usr/data/files_that_it_needs. Rather
than giving in to despair, I idly thought to try
/cygdrive/c/cygwin/usr/data/files_that_it_needs--- worked like a
charm.

So with that as background would I be correct in that one of the
significant differences from version 1.5.25 to version 1.7.7 might lie
in directory resolution? If so could someone explain in terms an idiot
like myself might understand? More to the point in terms my boss might
understand?

thanks
--hsm

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


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