X-Spam-Check-By: sourceware.org Message-ID: <11362324.post@talk.nabble.com> Date: Fri, 29 Jun 2007 08:37:03 -0700 (PDT) From: km4hr To: cygwin AT cygwin DOT com Subject: RE: How to link with third party libraries using gcc In-Reply-To: <011d01c7ba5a$f258fe50$2e08a8c0@CAM.ARTIMI.COM> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: km4hr AT netscape DOT net References: <11331072 DOT post AT talk DOT nabble DOT com> <4682C0EE DOT D7088ADD AT dessent DOT net> <11342161 DOT post AT talk DOT nabble DOT com> <4683D230 DOT 9030705 AT cygwin DOT com> <11348820 DOT post AT talk DOT nabble DOT com> <468409B0 DOT 7030705 AT cygwin DOT com> <11361112 DOT post AT talk DOT nabble DOT com> <011d01c7ba5a$f258fe50$2e08a8c0 AT CAM DOT ARTIMI DOT COM> X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Dave, You're right. I'm not listening. At least not entirely. The only thing I really needed to hear was that this is an "incredibly tricky and unreliable thing ... to do". Thanks for being up front about that! Dave Korn wrote: > > 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/ > > > -- View this message in context: http://www.nabble.com/How-to-link-with-third-party-libraries-using-gcc-tf3990417.html#a11362324 Sent from the Cygwin Users mailing list archive at Nabble.com. -- 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/