On Thu, Jul 28, 2005 at 01:46:26AM +0200, steven mestdagh wrote: > On Thu, Jul 28, 2005 at 12:49:16AM +0200, steven mestdagh wrote: > > > Apparently some additional output modules are available if the > > > libraries they depend on are. I don't know about the others, but > > > at least libMagick++ is available through the ImageMagick port. > > > This points to the idea of enabling further modules in the build > > > and subpackaging them in MULTI_PACKAGES. > > > > Good idea, I'll look into that. You mean adding ImageMagick to LIB_DEPENDS > > and building --with-magick by default, and then putting that module in a > > subpackage? No flavors? It's usable quite well without ImageMagick, too, > > I think. > > Well, this module seems to work. The annoying part is that it insists on > ImageMagick opening two blank X11 windows. > Now I'm wondering if there are any advantages in using pstoedit with the > Magick++ module instead of just using ImageMagick's convert? Is this worth > the trouble?
Well, I've put this module in a subpackage. It does not use flavors so I reset LIB_DEPENDS when packaging - is this correct? Removed the special CXXFLAGS, doesn't seem to make a difference. Then I also removed the cdrom remark, the license is GPL so it should be ok to include. Only the man page gets installed as documentation, and the *.a and *.la modules are removed. Tested on i386. steven
pstoedit.tgz
Description: application/tar-gz
