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 content-class: urn:content-classes:message Subject: Re: Packaging cURL for cygwin distribution ??? (was:RE: curl, libcurl, libcomprex, leakbug) MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-MimeOLE: Produced By Microsoft Exchange V6.0.4712.0 Date: Fri, 12 Oct 2001 14:47:48 -0400 Message-ID: <6EB31774D39507408D04392F40A10B2BACC5EB@FDYEXC202.mgroupnet.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: curl, libcurl, libcomprex, leakbug (was:Re: Packaging cURL for cygwin distribution ???) Thread-Index: AcFTS68M4Sb17J3wTeG86eVX+nq7YAAAiBfA From: "Roth, Kevin P." To: X-OriginalArrivalTime: 12 Oct 2001 18:47:48.0624 (UTC) FILETIME=[63935900:01C1534E] Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id f9CImA815007 > cURL package is full libtoolized and they use also > autoconf 2.52 so it was the easiest way to add a macro to > configure.in and the LDFLAG to Makefile.am, but i also > needed to remove one macro call in configure.in ... What macro did you remove? I couldn't find any mention of it in the diff you posted. > Depends on where you want to compile it, cross-compilation is > a special issue where i cannot help much because I don't use > linux (nowadays). Actually I wasn't thinking of cross-compilation, so much as just creating a shell script, which could be part of the curl distribution (in the packages sub-directory somewhere), that I could run to make cygwin tarballs out of a standard curl distribution... I'm sure I could throw one together, but I know it wouldn't be very sophisticated. --Kevin