README | 15 +++++++++++++++ configure.ac | 4 ++-- 2 files changed, 17 insertions(+), 2 deletions(-)
New commits: commit e5dfe6b4987b5723ea0c7fe88f5ff821ee3e44f5 Author: Drew Parsons <dpars...@debian.org> Date: Thu Oct 29 20:26:23 2009 +1100 README discusses build issues around libXfont 1.4. libXfont 1.4 removed Xprint font support, so need built-in fonts: Need ./configure --enable-builtin-fonts However this causes unresolved segfaults in client programs. The default situation (--disable-builtin-fonts) successfully uses external fonts but only builds against libXfont 1.3. Also included suggestion to use libcairo instead of Xprint for those who need the WYSIWYG or print-to-pdf/postscript functionality. diff --git a/README b/README new file mode 100644 index 0000000..2f2eb35 --- /dev/null +++ b/README @@ -0,0 +1,15 @@ +Xprint is now deprecated. + +For a WYSIWYG-style printing API giving equivalence between what appears in an +X windows and what gets printed on paper or to pdf or postscript, you may want +to consider using libcairo, the Cairo graphics library +(http://cairographics.org/) + +Font support for Xprint was removed from libXfont 1.4. To build Xprt under +libXfont 1.4 (or later) you will need to use built-in fonts + ./configure --enable-builtin-fonts +(By default built-in fonts are not used, equivalent to --disable-builtin-fonts). + +However built-in fonts may cause a segfault in client programs, which has not +been debugged since Xprint is deprecated. For an operational Xprt you may want +to built against libXfont 1.3. commit 48dcb52fb56999b59d8b8ff037a127cbd4fddca1 Author: Drew Parsons <drew.pars...@anu.edu.au> Date: Thu Oct 29 20:04:49 2009 +1100 Revert "By default, enable built-in fonts in configure script." This reverts commit f7b940677eae414ab08ce41fe6bdb7253b7a7864. The built-in fonts (--enable-builtin-fonts) trigger a segfault with clients. That is, Xprt will build and run successfully with them, but when a client such as xpsimplehelloworld tries to print via Xprt, it segfaults. Since Xprint is deprecated, motivation is not high for fully debugging this problem. The workaround around will be to not use built-in fonts (i.e. reverting the previous commit to use --disable-builtin-fonts by default again), and build against libXfont 1.3 (rather than the latest libXfont 1.4, which has Xprint support removed). diff --git a/configure.ac b/configure.ac index a58c303..48ca285 100644 --- a/configure.ac +++ b/configure.ac @@ -504,9 +504,9 @@ AC_ARG_ENABLE(install-libxf86config, [Install libxf86config (default: disabled)]), [INSTALL_LIBXF86CONFIG=$enableval], [INSTALL_LIBXF86CONFIG=no]) -AC_ARG_ENABLE(builtin-fonts, AS_HELP_STRING([--enable-builtin-fonts], [Use only built-in fonts (default: use built-in fonts)]), +AC_ARG_ENABLE(builtin-fonts, AS_HELP_STRING([--enable-builtin-fonts], [Use only built-in fonts (default: use external)]), [BUILTIN_FONTS=$enableval], - [BUILTIN_FONTS=yes]) + [BUILTIN_FONTS=no]) AC_ARG_ENABLE(null-root-cursor, AS_HELP_STRING([--enable-null-root-cursor], [Use an empty root cursor (default: use core cursor)]), [NULL_ROOT_CURSOR=$enableval], [NULL_ROOT_CURSOR=no]) -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org