Re: configure-generated *.in's

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Sorry to follow-up to myself, but with a little help from autoreconf's
-verbose flag I just figured out that this may be failing in automake,
not autoconf.  The underlying problem remains.

    --jtc

jtc@xxxxxxxxxxxxxxxxxx (J.T. Conklin) writes:
> Roger Leigh's AC_CONFIG_PKGCONFIG_IN macro from the autoconf macro
> archive generates a *.pc.in files.  The intent seems to be for the
> *.pc.in file to be post-processed by AC_CONFIG_FILES to expand any
> @macros@, and then the resulting *.pc file can be installed for use 
> by pkg-config.
>
> 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?
>
>     --jtc

-- 
J.T. Conklin


_______________________________________________
Autoconf mailing list
Autoconf@xxxxxxx
http://lists.gnu.org/mailman/listinfo/autoconf

[Index of Archives]     [GCC Help]     [Kernel Discussion]     [RPM Discussion]     [Red Hat Development]     [Yosemite News]     [Linux USB]     [Samba]

  Powered by Linux