Re: [xmlroff] Building xmlroff from CVS

[Dave M. <da...@da...>]

On Thu, 2003-07-24 at 07:53, Tony Graham wrote:
> Dave Malcolm wrote at 22 Jul 2003 19:31:36 +0000:
>  > I'm attempting to built xmlroff from CVS, but am having problems.
> ...
>  > It looks to me like the macro in configure.in to setup the version info
>  > hasn't worked properly; it's come out as "::" rather than "0:2:3" (or
>  > whatever)
>  > 
>  > Have anyone got any suggestions?  Have I forgotten something obvious? 
>  > Should I have set something when I configured the code?
> 
> It was my problem, not your problem.
> 
> I checked in a modified configure.in and Makefile.am on 22nd July
> after I found that I had the problem after breaking things on 21st
> July.
> 
> Please do an update and see if you still have the problem.

OK - it fixed that problem.  Thanks!

I'm now attempting to link Conglomerate against libfo, and am running
into random crashes.  

I'm using a vanilla Red Hat 9 machine.  I've built PangoPDF and xmlroff,
installing them to /usr/local, with PKG_CONFIG_PATH set to
/usr/local/lib/pkgconfig.

When I build and run my app (linking against libfo), the Gtk libraries
seem to dynamically link against the local PangoPDF version of the Pango
symbols, rather than the /usr/lib build of the "real" Pango, and crashes
occur (probably there are a few things out of sync here and there).

Is this the anticipated behaviour i.e. do I need to rebuild my entire
Gtk/Gnome build environment on top of PangoPDF (please no!) or can
anyone suggest a simple solution?  Is there something simple I've
missed?

> 
> Also, please provide an opinion on the usability of separating out
> (and not installing) fo-doc-commands.h.

I'm thinking of doing some hacking on the gnome print backend (to
implement passing a GnomePrintJob and forcing the code to stick to the
paper size in that, as discussed in a previous email); I can't really
comment until I've got everything building and running within my app.

-- 
David Malcolm
www.conglomerate.org