Mailing-List: contact cygwin-apps-help AT sourceware DOT cygnus DOT com; run by ezmlm Sender: cygwin-apps-owner AT sourceware DOT cygnus DOT com List-Subscribe: List-Archive: List-Post: List-Help: , Delivered-To: mailing list cygwin-apps AT sources DOT redhat DOT com Date: Tue, 3 Apr 2001 11:08:38 -0400 From: Christopher Faylor To: cygwin-apps AT cygwin DOT com Subject: Re: for interest: cygwin rpm on sourceforge Message-ID: <20010403110838.B30401@redhat.com> Reply-To: cygwin-apps AT cygwin DOT com Mail-Followup-To: cygwin-apps AT cygwin DOT com References: <200104020358 DOT XAA03886 AT envy DOT delorie DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: ; from ans@beethoven.cpe.ku.ac.th on Tue, Apr 03, 2001 at 08:33:02PM +0700 On Tue, Apr 03, 2001 at 08:33:02PM +0700, Anon Sricharoenchai wrote: >On Sun, 1 Apr 2001, DJ Delorie wrote: >>>Why don't make setup a cygwin app ? >> >>Setup can't be a cygwin app because cygwin hasn't been installed yet. >>What happens when cygwin1.dll is itself inside an RPM file? >> >>>Anyway, even though setup isn't a cygwin app, it can make call to >>>rpm.exe (which is a cygwin app) to install RPMs. >> >>Ditto. > >Can cygwin1.dll be statically linked into setup.exe or rpm.exe ? Or >cygwin1.dll may be placed in the same directory with setup.exe or >rpm.exe, so they can load cygwin1.dll in the setup time. We have discussed this fairly recently in this mailing list. I sent out a pointer yesterday. cgf