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: [ITP] libungif-4.1.0-1



Lapo Luchini wrote:

Steven's 'mkdll.sh' script is just plain wrong. libungif is a libtoolized package, you should just relibtoolize.

Problem is.. what is libtool? 0=)
Well one of the reasons why I work on cygwin is just to learn... I guess it is time to do some google:libtool and go finding a FAQ/manual about it
(grrr, www.gnu.org is down... I hope libtool manual's mirror at www.delorie.com is fresh enough)

'info libtool' should help...


Whoa, 950kb instead of 9k patch?

Yes, but it's (almost) all automatically generated.


Now I understand fully all those messages "relibtoolized source package" vs "libtoolize in the script"... I think I prefer the latter, the patch is much cleaner and the user that wants to rebuild the package just needs to install things, doesn't need any special knowledge.

But you don't. If the package (that'd be you) includes a complete patch including all of the relibtoolized bits, then the end user need only "./configure; make'.


OK, I prepared the package using "aclocal && libtoolize --force" at the beginning of the "conf" phase.
Only difference from the past package is that instead of usr/bin/cygungif.dll it creates usr/bin/cygungif-4.dll, is this normal/expected?

Yes, that is normal.

--Chuck




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