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 From: "Gerrit P. Haase" Organization: Esse keine toten Tiere To: cygwin-apps AT cygwin DOT com Date: Fri, 12 Oct 2001 08:25:09 +0200 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: Packaging cURL for cygwin distribution ??? Reply-to: cygwin-apps AT cygwin DOT com Message-ID: <3BC6A8E5.5981.3BD0EBB7@localhost> In-reply-to: <20011011181700.F3488@redhat.com> References: <6EB31774D39507408D04392F40A10B2BC1FD6C AT FDYEXC202 DOT mgroupnet DOT com> X-mailer: Pegasus Mail for Win32 (v3.12cDE) X-Hops: 1 Roth, Kevin P. writes: >>Before I do that, I have a question: >>cURL's configure script includes an option "--disable-shared". >>I *think* "--enable-shared" is the default, however I don't >>really understand exactly what these options mean. >> >>Is there any best practice about whether or not these options >>should be used for cygwin builds? Does it build .dll libraries, say libcurl.dll? And do the executables linked against it work along with this dll? Well then it is o.k. to use the shared version. cgf writes: >What kind of shared libraries does it produce? > >I don't think that it really matters either way. Personally, >I'd have a preference for the default configuration, though. 'ruby' doesn't build a shared libruby.dll by default (on cygwin), but it is better because easier to get additional modules loaded as it is in perl, too. Else the main executable always needs to be recompiled if a new module is added. So not always is the 'default' the best option (IMHO). Another question: Now, since we have libcurl, do you know of other packages that make use of libcurl? Have you tried to build one? Gerrit -- =^..^=