Re: configure-generated *.in's

[J.T. Conklin]

Bruce Korb <address@hidden> writes:
>> However, if I add foo.pc to AC_CONFIG_FILES, autoconf complains that
>> foo.pc.in does not exist (which it does not).  However, if I omit it,
>> foo.pc.in is generated at configure-time, but foo.pc is not.
>> 
>> Does anyone have any clue how to use this macro?
>
> My solution was a "mk-mumble-pc.sh" shell script.  I confess I
> already had a "mumble-config" script that was derived from
> "mumble-config.in", but shell scripts are pretty flexible.  
> I would be open to better suggestions :-).

While AC_CONFIG_PKGCONFIG_IN() is very appealing, writing a script
that takes similar arguments and generates a *.pc.in file that can
be included in the package isn't that much worse.  I think this is
what I'll pursue, since it also has the added benefit of working.

    --jtc

-- 
J.T. Conklin