On 29 June 2007 15:26, km4hr wrote:
> computer. I have no idea how cygwin does that. But with all the complex
> obstacles that the cygwin developers have obviously overcome it's puzzling
> to me why something as seemingly ordinary as Windows libraries is so
> mystifying.
Because they are *windows* libraries, not *cygwin* libraries. The two are
*different*.
> In just this one series of messages I've been told the
> instructions in the cygwin user's guide make no sense.
The instructions in the user's guide do not address the incredibly tricky
and unreliable thing you are trying to do.
> Then I'm offered
> several opinions about what I should do.
No, you have been told the /same/ things by several people, but you just
aren't listening.
> It makes me wonder how Windows' own
> programming tools are able to link with their own libraries if the standards
> are so vague and haphazard.
They aren't "vague and haphazard", they are precise, and explicit - and
INCOMPATIBLE. Each standard is entirely consistent, but YOU ARE TRYING TO MIX
TWO DIFFERENT STANDARDS.
> I guess I'll just add one more entry to the
> list of things I can't comprehend about Windows. I'm ok with that because I
> don't care about Windows anyway.
>
> Thanks again from enlightening me.
Don't really think you've understood a word so far.
Once more, I'll suggest you try thinking of it this way: how easy would you
find it to link a windows DLL into a program running on your unix box?
Because that is equivalent to what you are trying to do.
cheers,
DaveK
--
Can't think of a witty .sigline today....
--
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/
