[PATCH:font/util] Add several new XORG_FONT* macros to replace code common to many font modules

[Dan Nicholson]

On Tue, Oct 6, 2009 at 2:05 AM, Peter Hutterer <peter.hutterer at who-t.net> wrote:
> On Mon, Oct 05, 2009 at 07:51:35PM -0700, Alan Coopersmith wrote:
>> XORG_FONT_REQUIRED_PROG(VARNAME, progname)
>> XORG_FONT_FCCACHE()
>> XORG_FONT_COMMON_UTILS()
>> XORG_FONT_BDF_UTILS()
>> XORG_FONT_SCALED_UTILS()
>> XORG_FONT_CHECK_COMPRESSION()
>> XORG_FONTDIR(subdir)
>>
>> Signed-off-by: Alan Coopersmith <alan.coopersmith at sun.com>
>> ---
>>  fontutil.m4 |  123 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>  1 files changed, 123 insertions(+), 0 deletions(-)
>>
>> diff --git a/fontutil.m4 b/fontutil.m4
>> index 3d22990..23f861b 100644
>> --- a/fontutil.m4
>> +++ b/fontutil.m4
>> @@ -225,3 +225,126 @@ AC_DEFUN([XORG_FONT_CHECK_KOI8_R],[
>>       AC_MSG_RESULT([$KOI8_R])
>>       AM_CONDITIONAL(KOI8_R, [test "x$KOI8_R" = xyes])
>>  ])
>> +
>> +# XORG_FONT_REQUIRED_PROG(VARNAME, progname)
>> +# ------------------------------------------
>> +# Minimum version: 1.1.0
>
> shouldn't you bump configure.ac as well or are you doing it as a separate
> commit? Or do you have any other changes queued up?
> just those three patches applied would result in failures if configure isn't
> bumped, no?

I'm not sure what you mean, but just adding macros to a m4 file
shouldn't cause any issues. There should be later patches to enable
use of these macros in the other modules, but I think this one is self
contained.

--
Dan