Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
From: "Dave Korn" <dave DOT korn AT artimi DOT com>
To: <cygwin AT cygwin DOT com>
Subject: RE: Extending Cygwin Linux API - how to expose new API
Date: Fri, 5 Aug 2005 16:31:17 +0100
MIME-Version: 1.0
Content-Type: text/plain; 	charset="us-ascii"
Content-Transfer-Encoding: 7bit
In-Reply-To: <BAY106-F314A0770FA09D9EC3CF13FFBC70@phx.gbl>
Message-ID: <SERRANOisbTmrHVFf7E000000cf@SERRANO.CAM.ARTIMI.COM>

----Original Message----
>From: Eitan Eliahu
>Sent: 05 August 2005 16:22

> Folks,
> I would like to add a function to the Cygwin Linux API. Since the .def
> file is automatically generated this function can not be listed there. I
> am wondering if I need to have the keyword __export before the function
> but I noticed that other API functions don't use export.
> Is there any file where all the API functions are listed?


  I think cygwin.din is the place.  That's where gendef gets it from.


    cheers,
      DaveK
-- 
Can't think of a witty .sigline today....


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