On Fri, Mar 14, 2014 at 10:47:28PM +0100, Branko Čibej wrote:
> And of course you can't tweak the generator to ignore symbols that are
> not expanded, is that what you're saying? :)
Indeed, we cannot.
I'm generating pc.in files from build.conf to avoid having to
maintain duplicate dependency information for pkg-config support.
So we first generate .pc.in files from build.conf. At this stage,
we parse build.conf to see which variables could be expanded.
If we see $(SVN_INTL_LIBS) we put @SVN_INTL_LIBS@ in the pc.in file.
This part is what this discussion is about. And it is the only part
we can write code for.
Later we generate .pc files from .pc.in files using a pre-defined
autotools macro we don't control. It's done like this:
AC_CONFIG_FILES([${pc_file}])
This happens at the end of the configure script. At this stage we
perform substitutions of the form @SVN_INTL_LIBS@ -> -lsomething
depending on what the configure script found.
