www.delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin-apps/2001/03/07/09:24:09

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: <mailto:cygwin-apps-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-apps/>
List-Post: <mailto:cygwin-apps AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-apps-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/lists.html#faqs>
Delivered-To: mailing list cygwin-apps AT sources DOT redhat DOT com
Message-ID: <00bb01c0a712$180e63a0$9865fea9@edward>
From: "edward" <tailbert AT yahoo DOT com>
To: <cygwin-apps AT cygwin DOT com>
Cc: <libtool AT gnu DOT org>
Subject: miscellaneous cygwin libtool patch
Date: Wed, 7 Mar 2001 09:22:50 -0500
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
X-Apparently-From: Swiftnsavv AT aol DOT com

This is a multi-part message in MIME format.

------=_NextPart_000_00B8_01C0A6E8.2E7AD800
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

hi peeps

in a fit of pique, i managed to get cvs libtool running for dll/static =
libs on the cygwin platform. i think i broke most other windows, and =
possibly other platforms though. anyways, in case anyone wants to take a =
look at it. i have placed the entire patched source, with an example =
trivial project demonstrating static archive and dll generation here:

http://www.tailifer.com/misc/libtool-cygwin.tar.bz2

If you just want the patch, it's here:

http://www.tailifer.com/misc/libtool-cygwin.patch

if you have a .def file, then make, make check, make install work on =
cygwin, including the script wrappers. other than defining the proper =
automake commands for cygwin, there is relatively little modifications =
required to use it in your project. the bzip2 file contains relatively =
little explanation of what i did, but has a decent log of how i did it.

warning: this really isn't good enough to be put into cvs, but it makes =
*my* life a heck of a lot easier. until we get a good version of libtool =
from the fine libtool peeps, this might do.

cheers,
edward

PS. who put all the funky binary characters in cvs libtool.m4 version =
1.148? sounds like an "oops" to me.






------=_NextPart_000_00B8_01C0A6E8.2E7AD800
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 5.50.4611.1300" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>hi peeps</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>in a fit of pique, i managed to get cvs =
libtool=20
running for dll/static libs on the cygwin platform. i think i broke most =
other=20
windows, and possibly other platforms though. anyways, in case anyone =
wants to=20
take a look at it. i have placed the entire patched source, with an =
example=20
trivial project demonstrating static archive and dll generation=20
here:</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><A=20
href=3D"http://www.tailifer.com/misc/libtool-cygwin.tar.bz2">http://www.t=
ailifer.com/misc/libtool-cygwin.tar.bz2</A></FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>If you just want the patch, it's =
here:</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><A=20
href=3D"http://www.tailifer.com/misc/libtool-cygwin.patch">http://www.tai=
lifer.com/misc/libtool-cygwin.patch</A></FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>if you have a .def file, then make, =
make check,=20
make install work on cygwin, including the script wrappers. other than =
defining=20
the proper automake commands for cygwin, there is relatively little=20
modifications required to use it in your project. the bzip2 file =
contains=20
relatively little explanation of what i did, but has a decent log of how =
i did=20
it.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>
<DIV><FONT face=3DArial size=3D2>warning: this really isn't good enough =
to be put=20
into cvs, but it makes *my* life a heck of a lot easier. until we get a =
good=20
version of libtool from the fine libtool peeps, this might =
do.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>cheers,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>edward</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>PS. who put all the funky binary =
characters in cvs=20
libtool.m4 version 1.148? sounds like an "oops" to me.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV></BODY></HTML>

------=_NextPart_000_00B8_01C0A6E8.2E7AD800--

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019