On 07/24/2013 07:39 PM, LRN wrote:
Or even better, separate config.h into two files - use one internally
(normal config.h), while the other will be both installed and used
internally (sadly, i can't tell you how exactly that can be done;
config.h.in is generated by autoheader, so they will have to either
tinker with autoheader, or just form the second (smaller) header
manually, at least an .in template of it).
We do exactly this in yat. We create a 'yat/utility/config_public.h'
from 'yat/utility/config_public.h.in', which is then installed. For
details please see http://dev.thep.lu.se/yat/browser/trunk/configure.ac
Cheers,
Peter
_______________________________________________
Autoconf mailing list
Autoconf@xxxxxxx
https://lists.gnu.org/mailman/listinfo/autoconf
