[Top][All Lists]

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

RE: Windows Build Broken - Feature Branch

From: Conrad T. Pino
Subject: RE: Windows Build Broken - Feature Branch
Date: Tue, 11 May 2004 22:27:53 -0700

Hi Derek,

> From: Derek Robert Price
> It would probably be better to use the error messages from the build
> to tell you since some of the new files may not be needed on Windows.

Thank you.  Suggestion was very helpful.

> You should be able to find a description of each new #define in the
> top level config.h.in.

Thanks again.  I totally missed this one until you pointed it out.

> You should also be able to find the macros which create the #defines
> dynamically on other platforms in the m4/*.m4 files, though that may
> be harder to interpret.  The content of these files is, well, if you
> are not familar with m4 & Autoconf, hacked up Bourne Shell scripts, to
> put it succinctly.  The srclist.txt file contains correlations between
> the *.c & *.h files in lib and the various macro files.

My knowledge of m4 is limited to SendMail .mc to .cf file generation
and SendMail rule set hacking.  Definitely possible and painful too.

> >This seems like a good opportunity to move build of "lib/*.c" files
> >into "libcvs" project which is a feasable concept which I tested while
> >working on new build files for stable branch.  I'll do this also unless
> >someone points out a reason not to do so.
> Sure.

This is done and working except for "gettime" and "nanosleep" modules.
I don't see much point in doing it as a separate patch.  Hopefully the
GNULib gang will work some magic in our favor soon.

> Derek


reply via email to

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