Bug#605871: [Pkg-fonts-devel] Bug#605871: Bug#605871: fontforge runs find / during the configure step
On Mon, Apr 15, 2013 at 04:46:42PM +0900, Hideki Yamane wrote: > On Mon, 15 Apr 2013 09:16:12 +0200 > Fabian Greffrath wrote: > > If this configure options is only relevant for building the bundled > > freetype copy, then it should be alright as it currently is. The > > freetype system library in Debian already has the byte-code interpreter > > enabled. > > You mean, both --with-freetype-bytecode and --with-freetype-src are not > necessary to be specified? I want to know that. They are necessary to build FontForge's byte code debugger for people who want to work with TrueType instructions (hinting). --with-freetype-src is only used to access FreeType's internal headers BTW, as of last FontForge release not specifying this option or using --without-freetype-src will cause font FontForge to do a `find /`, you certainly don't want this. It is already fixed it in git master (the build system was rewritten using autotools), lets hope the current "team" will not screw it by the time of the next release. Regards, Khaled -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#605871: [Pkg-fonts-devel] Bug#605871: Bug#605871: fontforge runs find / during the configure step
On Mon, Apr 15, 2013 at 03:22:26PM +0800, Paul Wise wrote: > On Mon, Apr 15, 2013 at 2:44 PM, Hideki Yamane wrote: > > > --with-freetype-src option should be used with relevant path like > > "--with-freetype-src=/foobar". But anyway, freetype source file is > > necessary to include to build with --with-freetype-bytecode option. > > > > If not, configure script warns for it. > >> checking for valid freetype tree... missing ttobjs.h > >> Unable to find /usr/include/freetype2/freetype/src/truetype/ttobjs.h > > Please file a bug against freetype asking for them to do either of these: > > Ship the needed header/etc files somewhere. These are internal FreeType headers, and shouldn't be made public. FontForge's use of FreeType her is a very special case that FreeType developers are aware of but they don't want to make those headers public (for the obvious reasons), that is why FontForge needs a copy of FreeType source to access those headers. FontForge does not build a bundled copy of FreeType. Regards, Khaled -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#605871: [Pkg-fonts-devel] Bug#605871: Bug#605871: fontforge runs find / during the configure step
On Mon, 15 Apr 2013 15:27:12 +0800 Paul Wise wrote: > > No, definitely not. Please fix ttf-kochi too, it shouldn't copy > > freetype around either. > > Please do fix ttf-kochi though. No, I've said ttf-kochi is just an example for multiple upstrearm tarball and not including freetype source, so fix is not necessary. -- Regards, Hideki Yamane henrich @ debian.or.jp/org http://wiki.debian.org/HidekiYamane -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#605871: [Pkg-fonts-devel] Bug#605871: Bug#605871: fontforge runs find / during the configure step
On Mon, Apr 15, 2013 at 3:22 PM, Paul Wise wrote: > On Mon, Apr 15, 2013 at 2:44 PM, Hideki Yamane wrote: > Please file a bug against freetype asking for them to do either of these: Please ignore what I wrote here, Fabian is correct. >> Q: Should we include freetype source with fontforge? >> We can add it as multiple orig source as >> fontforge_0.0.20120101+git.orig-freetype-2.4.9.tar.xz >> like I did for ttf-kochi package. > > No, definitely not. Please fix ttf-kochi too, it shouldn't copy > freetype around either. Please do fix ttf-kochi though. -- bye, pabs http://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
