[EMAIL PROTECTED] wrote:
On Tue, 4 May 2004, [UTF-8] Branko Äibej wrote:
[EMAIL PROTECTED] wrote:
We need to solve that problem. Having apr.h include apr.hw isn't theMaybe I'm dense...what's apr.h doing in CVS? It shoudln't be there,
right solution. I need to think about what a valid solution is, and it
may be having a separate directory that the Windows build systems create
to store this header file, and we include that directory in the INCLUDES
path before the standard includes dir. That would also solve the problem
of doing a CVS diff after having built on Windows. (Namely, the cvs diff
returns a mess of hits in apr.h, IIRC, because apr.hw is copied over
apr.h. Netware would use the same system).
being a generated file.
Nope, I'm the dense one. The CVS argument is bogus, but I was paying
attention to my daughter while replying to you.
Heh, you weren't replying to me, either. :-)
Anyway, I agree: apr.h.in has no business including apr.hw. The mingw build process has to convert apr.hw to apr.h, just like the "regular" Windows build process. Otherwise everything goes to pot.
-- Brane
