On Fri, Feb 13, 2015 at 6:59 AM, Andreas Müller <[email protected]> wrote: > had this in my private layer but think it could be useful here. > > Native tests: liberation-fonts (follow-up patch) / oxygen-fonts > Target test: gumstix overo / xfce image > > Signed-off-by: Andreas Müller <[email protected]> > --- > .../fontforge/fontforge_20141126.bb | 43 > ++++++++++++++++++++++ > 1 file changed, 43 insertions(+) > create mode 100644 meta/recipes-graphics/fontforge/fontforge_20141126.bb > > diff --git a/meta/recipes-graphics/fontforge/fontforge_20141126.bb > b/meta/recipes-graphics/fontforge/fontforge_20141126.bb > new file mode 100644 > index 0000000..835aa9b > --- /dev/null > +++ b/meta/recipes-graphics/fontforge/fontforge_20141126.bb > @@ -0,0 +1,43 @@ > +SUMMARY = "A font editor" > +HOMEPAGE = "http://fontforge.github.io/en-US/"; > +LICENSE = "GPLv3" > +LIC_FILES_CHKSUM = " \ > + file://COPYING.gplv3;md5=d32239bcb673463ab874e80d47fae504 \ > + file://LICENSE;md5=71d636ba7678baa1573e1b531041386e \ > +" > + > +inherit autotools pkgconfig pythonnative mime > + > +DEPENDS = "glib-2.0 pango giflib tiff libxml2 jpeg python libtool" Oops - just noticed that tiff is in meta-oe and even worse there was a discussion about moving tiff to oe-core long time ago [1]. Now the situation has changed slightly: To open upgrade path for liberation-fonts we need fontforge.
I see 3 ways to go: 1. Have tiff in oe-core 2. Have fontforge without tiff in oe-core. There seems to be a configure option disabling tiiff. This could be overridden in meta-oe. I have no idea if disabling tiff turns fontforge to useless condition from liberation-fonts's perspective. 3. Have fontforge in meta-oe and forget about upgrading liberation-fonts. Thoughts? Andreas -- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
