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 Date: Fri, 20 Sep 2002 12:15:41 -0400 From: Christopher Faylor To: "Buntain, Dave" Cc: cygwin@cygwin.com Subject: Re: First Attempt at a cygwin Project Message-ID: <20020920161541.GJ24740@redhat.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: "Buntain, Dave" , cygwin@cygwin.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4i On Fri, Sep 20, 2002 at 07:49:18AM -0600, Buntain, Dave wrote: >I've read the promotions on CygWin, but have not been able to find a >list of the CygWin API calls so that I can determine functional >capability of the Cygwin library. Can you point me to such a list ? "nm /usr/lib/libcygwin.a". Strip the __imp___ from the front of the symbols and you'll see all of the available functions. >I've read that porting the Unix to Windows requires a minimal amount of >source code changes. Is there a location on the web that is dedicated >to the porting process, and discusses the problems encountered ? Porting to cygwin is similar to porting to any other "UNIX" system. There are some Windows gotchas with things like case insensitive filename detection, and a more limited number of characters that can be used in filenames. Also, the FAQ is your friend. cgf -- Please do not send me personal email with cygwin questions. Use the resources at http://cygwin.com/ . -- 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/