[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Swftools-common] external libraries carried in source
From: |
Patrice Dumas |
Subject: |
Re: [Swftools-common] external libraries carried in source |
Date: |
Tue, 10 Jun 2008 23:34:53 +0200 |
User-agent: |
Mutt/1.5.18 (2008-05-17) |
On Wed, Jun 11, 2008 at 12:15:05AM +0200, Matthias Kramm wrote:
>
> > I know that, but my question was, would you accept patches to be able to
> > compile against system gocr and/or libart, and if yes, what design would
> > you prefer?
>
> I'd accept patches for both. (Reserving the freedom to, for the libart
> thing, requiring a configure flag like
> --yes-I-want-to-use-the-broken-system-libart, at least for now :))
Right.
> Concerning the design, it should be similar to how the lame detection
> logic works right now- check whether there's a lib/lame in the source
> tree, if not, try to find a system lame, if that's not found, don't
> use it. And only do that if there's is(n't) a configure flag saying so.
Ok.
> There's the OutputDev API. Using a different API would require
> a complete rewrite of pdf2swf. I don't think the poppler path is
> possible for now.
OutputDev.h is in poppler, at least on fedora...
--
Pat