This is the mail archive of the cygwin-apps@cygwin.com mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: PCRE package for consideration


On Tue, 29 Apr 2003, Gerrit P. Haase wrote:
>> When taking a look at the generated cygpcreposix-0.dll, you'll see that 
>> the link is OK: the DLL depends on the local cygpcre-0.dll

>> It's the relink during the install that breaks the library:
> yep.

>> So, if we really want to use Libtool, would doing a 
>> libtool --finish /usr/lib 
>> in a postinstall script fix this?
> I guess with the patch Charles Wilson posted yesterday it should be ok,
> though I havn't tested it yet but I trust him, he is the libtool
> master;)
In that case, we'll have to wait for his patch to make it to Cygwin's
libtool to be able to use libtool for pcre. I will not use a CVS version
of libtool to make a release of a package - mostly because I don't know
libtool well enough to trust the CVS version blindly (although I have
every confidence in the Libtool developers, but IMO, if they thought it
was ready for release, they'd release it).

As for the patch itself: I haven't seen it (neither on any of the Cygwin 
lists I read (and the developers list is the only one I don't read 
regularly) nor on the libtool patch list, so I can't test it here :|

Anyways, I propose we release a pcre-4.2-1 w/o using libtool, wait for a 
workable libtool to be released and get rid of the Windows stuff for 
pcre-4.2-2. I'll ask mr Hazel to relibtoolize when the new libtool gets 
out, so we can build pcre OOTB for Cygwin (and perhaps MinGW too).

rlc



Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]