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 To: cygwin@cygwin.com In-reply-to: <20020816170047.GA21626@redhat.com> (message from Christopher Faylor on Fri, 16 Aug 2002 13:00:47 -0400) Subject: Re: building a cygwin DLL to run on non-cygwin app References: <20020815235332.19EDF3DEB@cavall.jtang.org> <3D5CA285.8070904@scytek.de> <20020816165406.5550A3DBA@cavall.jtang.org> <20020816170047.GA21626@redhat.com> Message-Id: <20020816173323.CCED53DBA@cavall.jtang.org> Date: Fri, 16 Aug 2002 13:33:23 -0400 (EDT) From: tang@jtang.org (J. Tang) > Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm > Mail-Followup-To: cygwin@cygwin.com > Date: Fri, 16 Aug 2002 13:00:47 -0400 > From: Christopher Faylor > Mail-Followup-To: cygwin@cygwin.com > Content-Disposition: inline > > It is not currently possible to load the cygwin DLL only at runtime. > It has to be linked on the command line. > There are no plans to add this functionality. I do not understand what you mean. Withing libcygwin.a is the symbol "__cygwin_noncygwin_dll_entry@12", which sounds like what I need as my DLL's entry point. It is not a problem to statically link my DLL against cygwin1.dll. I do, however, need to then link my DLL against a vendor's program at runtime. -- Jason Tang / tang@jtang.org / http://www.jtang.org/~tang -- 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/