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 14:26:52 -0400 From: Christopher Faylor To: cygwin-apps AT cygwin DOT com Subject: Re: for interest: cygwin rpm on sourceforge Message-ID: <20010403142652.C31549@redhat.com> Reply-To: cygwin-apps AT cygwin DOT com Mail-Followup-To: cygwin-apps AT cygwin DOT com References: <200104031612 DOT MAA14548 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: <200104031612.MAA14548@envy.delorie.com>; from dj@delorie.com on Tue, Apr 03, 2001 at 12:12:55PM -0400 On Tue, Apr 03, 2001 at 12:12:55PM -0400, DJ Delorie wrote: >>Can cygwin1.dll be statically linked into setup.exe or rpm.exe ? > >No. > >>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. > >The whole point of setup is to avoid having to make the user do things >like this. Maybe we need a cygwin-apps FAQ. cgf