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, 16 Aug 2002 13:46:06 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: building a cygwin DLL to run on non-cygwin app Message-ID: <20020816174606.GB21392@redhat.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <20020815235332.19EDF3DEB@cavall.jtang.org> <3D5CA285.8070904@scytek.de> <20020816165406.5550A3DBA@cavall.jtang.org> <20020816170047.GA21626@redhat.com> <20020816173323.CCED53DBA@cavall.jtang.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020816173323.CCED53DBA@cavall.jtang.org> User-Agent: Mutt/1.3.23.1i On Fri, Aug 16, 2002 at 01:33:23PM -0400, J. Tang wrote: >From: Christopher Faylor >> >>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 "currently possible". It's broken. You can't load the cygwin DLL via LoadLibrary. >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. Just to be clear, when you link in the cygwin DLL, your code becomes automatically GPLed. 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/