"Tischler, Ron" wrote: > I am trying to use Cygwin to write a PC application that calls the > function named FtpCommand. Microsoft documentation that I found online > says that there is a header named wininet.h and a library named > wininet.lib to link in. On my PC, under the Cygwin stuff, I see > wininet.h, but not wininet.lib. This version of wininet.h does have a > declaration of FtpCommand. > > My PC also has copies of wininet.h and wininet.lib under "Program > Files", but this copy of wininet.h and wininet.lib does not contain > FtpCommand. When I compile, this header gets brought in, not the Cygwin > one, so my use of FtpCommand doesn't compile cleanly. I can get around > that by typing in the declaration of FtpCommand myself. But then, of > course, I get link time errors because it didn't find a wininet.lib that > contained FtpCommand. > > Should I be trying to get a copy of wininet.lib from Cygwin, or a more > up-to-date version of wininet.lib from Microsoft? Either way, what > would I need to do to link it into my application?
You don't have to worry about any of that stuff. Just make sure you have the w32api package installed, then #include the header as usual and add -lwininet to the end of your link command line. Don't try to mix in any other source of headers or libraries, especially the pSDK. w32api has everything. Cygwin does not use .lib files, and the naming of libraries is that of unix. So you use -lfoo to link with libfoo.a (or sometimes libfoo.dll.a) which is the import library for the DLL. Brian -- 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/
