Mail Archives: cygwin/2002/05/06/14:03:57
On Mon, May 06, 2002 at 01:47:20PM -0400, Larry Hall (RFK Partners, Inc) wrote:
>You bet. I like the details. It helps guide me in my responses,
>though I have to admit these details confuse me. So you have your app
>already built against Cygwin? Why do you need to do it again then?
>And why can't you do it the way it was done? I have a better idea of
>what you're trying to do but I'm not sure I really understand why you
>have the problem you do. Anyway, it sounds to me like you want to
>debug into Cygwin to understand this difference. That would mean that
>you need more than just an import library. You need a debug version of
>Cygwin. You'd have to build that. Also sounds to me like you need to
>figure out what Cygwin does so you can emulate it. The quickest way to
>that is to look at the source. Of course, that probably gets a little
>sticky since it's not quite proper to effectively copy Cygwin source.
>
>OK, I should stop speculating on your issues! ;-)
Can I suggest that since we're discussing ways of getting rid of the
cygwin DLL this is probably not really on-topic here? This is supposed
to be a list which discusses how to use cygwin not how to not use
cygwin.
Maybe www.mingw.org is what is required.
Or, alternatively, a Red Hat commercial license might be applicable.
Click on the "Red Hat Cygwin Product" link at http://cygwin.com/,
if so.
cgf
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
- Raw text -