Re: [PATCH] enable build of shared module on Cygwin

Tony Graham <[email protected]> Fri, 15 Oct 2004 12:33:49 +0100
Newsgroups gmane.text.xml.xmlroff.pangopdf
Message-ID <[email protected]>
"Gerrit P. Haase" <[email protected]> writes:
> I'm currently preparing the first public release of the GNOME desktop
> for Cygwin.  I like the new PangoPDF very much, no more hassle with
> building and installing, great work!

Thank you.

Note that the current PangoXSL doesn't actually do anything except
allow xmlroff to compile and stop xmlroff from crashing when it runs.
The properties that PangoXSL defines are not currently supported in
any rendering code.

PangoPDF used to implement the properties by having its own version of
Pango's rendering code, but because PangoPDF was (by necessity rather
than choice) an alternative to rather than an add-on for Pango caused
problems.  The fact that PangoPDF used (or could use) PDFlib caused
other problems of the license nature.

The necessity for PangoPDF to be built as an alternative to Pango was
because it implemented a PDF backend for Pango since there wasn't
anything capable of doing that at the time that I started. PangoPDF
initially used PDFlib and later used either PDFlib or GNOME Print.

With current Pango and GNOME Print, the GNOME Print backend of
PangoPDF became redundant.  Given that, I decided to kill two or maybe
three birds with one stone by making PangoPDF use the current GNOME
Print instead of its own GNOME Print backend, drop the PDFlib backend
because it caused unwanted complications, and make PangoPDF be an add
on to Pango so there wasn't the either/or conundrum.

The new PangoPDF is called PangoXSL both because I wanted to use a new
CVS module so I wouldn't have to 'CVS remove' all the old files and
yet still be left with a bunch of empty directories and because the
'PDF' in the name no longer reflects its function.

This first iteration of PangoXSL still defines some additional
properties but since I took the shortest route to getting a no-backend
library, there's no rendering code for the additional properties.

I expect that the next iteration of PangoXSL will support the
'callback' attribute as post-processing on top of what GNOME Print
renders.  Once it's working (which it never did for the GNOME Print
backend), I'll look to patching Pango to support it and then submit
the patch as an enhancement request.

I would like to do the same for the other properties, but to do the
baseline properties properly requires Pango to use the baseline tables
in OpenType fonts, which it doesn't at present, but I consider that
right now what time I have to spend on xmlroff would be better spent
working on xmlroff itself.

> One little change was needed, to get a shared library from libtool for
> Cygwin is the -no-undefined LDFLAG needed.
>
> Patch is attached.

Thanks.  I ended up borrowing how Pango tests for Windows and how it
sets -no-undefined.

Regards,


Tony.



-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl