public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Larry Hall <lh-no-personal-replies-please@cygwin.com>
To: "Daniel Starin" <ds708@columbia.edu>,
	"'Cygwin List'" <cygwin@cygwin.com>
Cc: <alastair.growcott@bakbone.co.uk>
Subject: RE: Visual Studio linking
Date: Fri, 17 Dec 2004 22:20:00 -0000	[thread overview]
Message-ID: <6.2.0.14.0.20041217171126.02f77900@pop.prospeed.net> (raw)
In-Reply-To: <200412172135.iBHLZXAj001234@jalapeno.cc.columbia.edu>

At 04:36 PM 12/17/2004, you wrote:
>So, I realized I had the compile option "Use Managed Extensions" on in VS
>.NET and that was causing the problem.  


Really.  That was it?  Well, that's pretty non-intuitive.  Nice job finding 
that.


>Now that I can include the libs in
>my project, are there any header files that I can include from Visual Studio
>to use them?...


I doubt it.  Cygwin provides POSIX APIs that VS doesn't so the mere existence
of Cygwin indicates that there's not going to be such an overlap.  Also, 
Cygwin's header files are it's own.  It's not a big surprise that they 
contain specific info that's not understood by VS.  The reverse is also 
true.  You'll need to build your own set of function declarations and 
needed symbols, etc.


--
Larry Hall                              http://www.rfk.com
RFK Partners, Inc.                      (508) 893-9779 - RFK Office
838 Washington Street                   (508) 893-9889 - FAX
Holliston, MA 01746                     


--
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/

  reply	other threads:[~2004-12-17 22:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-12 22:38 Daniel Starin
2004-12-12 22:55 ` Larry Hall
2004-12-17 21:35   ` Daniel Starin
2004-12-17 22:20     ` Larry Hall [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-06-02  8:20 Alastair Growcott
2004-06-02  8:52 ` Max Bowsher
2004-06-02  9:18   ` Re[2]: " Alastair Growcott
2004-06-02 12:16     ` Re[3]: " Alastair Growcott
2004-06-02 13:45       ` Re[4]: " Alastair Growcott
2004-06-07 14:40         ` Re[5]: " Alastair Growcott
2004-06-07 14:56           ` Christopher Faylor
2004-06-07 16:15             ` Re[2]: " Alastair Growcott
2004-06-07 16:25               ` Christopher Faylor
2004-06-08  9:04                 ` Alastair Growcott
2004-06-08 13:02                   ` Christopher Faylor

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6.2.0.14.0.20041217171126.02f77900@pop.prospeed.net \
    --to=lh-no-personal-replies-please@cygwin.com \
    --cc=alastair.growcott@bakbone.co.uk \
    --cc=cygwin@cygwin.com \
    --cc=ds708@columbia.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).