[ITP] freetype2 2.1.5 - Ready for review
Original from http://www.freetype.org/ Description === A Free, High-Quality, and Portable Font Engine. Changes from original ITP = 1) Both shared and static libs are being built correctly. 2) Broke monolithic package up into three packages (below). 3) Setup external-source references for the libfreetype26 and libfreetype2-devel packages. 4) I believe the package is feature complete and ready to be posted. freetype2 = http://www.msu.edu/~huntharo/cygwin/freetype2/freetype2-2.1.5-1-src.tar.bz2 (1048 KiB) http://www.msu.edu/~huntharo/cygwin/freetype2/freetype2-2.1.5-1.tar.bz2 (3 KiB) http://www.msu.edu/~huntharo/cygwin/freetype2/setup.hint (1 KiB) libfreetype26 = http://www.msu.edu/~huntharo/cygwin/freetype2/libfreetype26/libfreetype26-2.1.5-1.tar.bz2 (172 KiB) http://www.msu.edu/~huntharo/cygwin/freetype2/libfreetype26/setup.hint (1 KiB) libfreetype26 = http://www.msu.edu/~huntharo/cygwin/freetype2/libfreetype2-devel/libfreetype2-devel-2.1.5-1.tar.bz2 (332 KiB) http://www.msu.edu/~huntharo/cygwin/freetype2/libfreetype2-devel/setup.hint (1 KiB) Please remember to vote when finished reviewing, Harold
[ITP] freetype2 2.1.5
Original from http://www.freetype.org/ Questions for other maintainers === 1) freetype2 is built as part of XFree86 right now as a shared library, but configuring with --enable-shared and --disable-static doesn't produce a .dll when building the standalone tree. 2) Any tips for getting the standalone tree to emit a shared library? I tried relibtoolizing it (aclocal, autoheader, autoconf, libtoolize, forcing copy of files) to no avail. 3) There is a warning coming from libtool: libtool: link: warning: undefined symbols not allowed in i686-pc-cygwin shared libraries The whole build log is here in case anyone can give some insight from it: http://www.msu.edu/~huntharo/cygwin/freetype2/build.log.bz2 (4 KiB) Initial version of package files http://www.msu.edu/~huntharo/cygwin/freetype2/freetype2-2.1.5-1-src.tar.bz2 (841 KiB) http://www.msu.edu/~huntharo/cygwin/freetype2/freetype2-2.1.5-1.tar.bz2 (320 KiB) Any help would be appreciated, Harold
Re: [ITP] freetype2 2.1.5
Harold L Hunt II wrote: Original from http://www.freetype.org/ Questions for other maintainers === 1) freetype2 is built as part of XFree86 right now as a shared library, but configuring with --enable-shared and --disable-static doesn't produce a .dll when building the standalone tree. 2) Any tips for getting the standalone tree to emit a shared library? I tried relibtoolizing it (aclocal, autoheader, autoconf, libtoolize, forcing copy of files) to no avail. Well, it's a bit confusing to me without actually running configure myself, but I can't tell if fontconfig really actually use autoconf/automake/libtool the right way, or if instead it merely uses them to generate a JamFile for the 'jam' package building tool. 3) There is a warning coming from libtool: libtool: link: warning: undefined symbols not allowed in i686-pc-cygwin shared libraries Well, that's either (a) a warning that the relevant libtool link command line does not contain the -no-undefined flag, which indicates that the maintainer asserts that the library will have no undefined symbols at link time, or (b) an indication that, contrary to expectations, the library DID have undefined symbols at link time. When I get a chance, I'll download your source and see what I can make of it. Ping me if you don't hear in a few days. -- Chuck
Re: [ITP] freetype2 2.1.5
Chuck, Thanks for your help. I got it with the one-two combination: 1) Re libtoolize it. 2) Add LDFLAGS=-no-undefined in my package script. A DLL is now created. Haven't rebuilt XFree86 yet to how it operates. Note that before relibtoolizing it I got an error about an undefined reference to WinMain16. Relibtoolizing it fixed that problem. Thanks again, Harold Harold L Hunt II wrote: Charles Wilson wrote: Well, it's a bit confusing to me without actually running configure myself, but I can't tell if fontconfig really actually use autoconf/automake/libtool the right way, or if instead it merely uses them to generate a JamFile for the 'jam' package building tool. Hmm... I think it optionally uses jam. It certainly doesn't use automake (no Makefile.am, etc.). It is a very strange package indeed. Well, that's either (a) a warning that the relevant libtool link command line does not contain the -no-undefined flag, which indicates that the maintainer asserts that the library will have no undefined symbols at link time, or (b) an indication that, contrary to expectations, the library DID have undefined symbols at link time. Thanks Chuck. It has been a while since I worked with the autotools. For (b), does this contradiction require that '-no-undefined' be passed? Right now I am not passing -no-undefined and am getting this warning. When I get a chance, I'll download your source and see what I can make of it. Ping me if you don't hear in a few days. Okay, thanks. There is a freetype2-2.1.5-1.sh script included and doing a prep conf build takes about two minutes on my box. Just FYI. Harold
