[Top][All Lists]

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

RE: Questions: ./config.h.in & ./windows-NT/config.h.in

From: Conrad T. Pino
Subject: RE: Questions: ./config.h.in & ./windows-NT/config.h.in
Date: Fri, 14 May 2004 14:08:36 -0700

Hi Derek,

> From: Derek Robert Price
> Kinda.  Right now, config.h.in is autogenerated from the configure.in
> script.  We then copy bits into windows-NT/config.h.in as we find we
> need them.

Thank you for confirming my working hypothesis.

> >Is there a maintenance or synchronization goal?
> I've given it some thought, but haven't done anything about, at least
> since some of the GNULIB modules started using AH_VERBATIM.  My
> thought was that it might be useful to keep a windows-NT/file with a
> list of a #define XXXX YYY style, then generate the
> windows-NT/config.h file from that file and the root config.h.in so
> that these sort of changes would show up automatically, but I hadn't
> gotten around to it.  The same script should probably warn when macros
> in the windows-NT list disappear from the root config.h.in.

I was thinking along the lines of a Perl script that reads "./config.h.in"
to derive "./windows-NT/config.h.in" which is processed per the current
process to derive "./windows-NT/config.h" file.

The suggestion to drop a step requires modifing the current process but I
don't know where that occurs.  Can you provide me with a pointer to where
"./windows-NT/config.h.in" to "./windows-NT/config.h" step is found?

> Derek


reply via email to

[Prev in Thread] Current Thread [Next in Thread]