Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Reply-To: Cygwin List Message-Id: <6.2.0.14.0.20041217171126.02f77900@pop.prospeed.net> Date: Fri, 17 Dec 2004 17:15:55 -0500 To: "Daniel Starin" , "'Cygwin List'" From: Larry Hall Subject: RE: Visual Studio linking Cc: In-Reply-To: <200412172135.iBHLZXAj001234@jalapeno.cc.columbia.edu> References: <6.2.0.14.0.20041212173750.02f613c8@pop.prospeed.net> <200412172135.iBHLZXAj001234@jalapeno.cc.columbia.edu> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" 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/