From: Hrvoje Niksic <[EMAIL PROTECTED]>
> > Also, am I missing something obvious, or should the configure script
> > (as in, "To configure Wget, run the configure script provided with
> > the distribution.") be somewhere in the CVS source?
>
> The configure script is auto-generated and is therefore not in CVS.
> To get it, run autoconf. See the file README.cvs.
Sorry for the stupid question. I was reading the right document but
then I got distracted and failed to get back to it. Thanks for the
quick, helpful responses.
> > And I'm just getting started, but is there any good reason for the
> > extern variables output_stream and output_stream_regular not to be
> > declared in some header file?
>
> No good reason that I can think of.
I'm busy segregating all/most of the VMS-specific stuff into a "vms"
directory, to annoy the normal folks less.
Currently, I have output_stream, output_stream_regular, and
total_downloaded_bytes in (a new) main.h, but I could do something else
if there's a better plan.
Rather than do something similar for version_string, I just
transformed version.c into version.h, which (for the moment) contains
little other than:
#define VERSION_STRING "1.10-alpha1_sms1"
Was there any reason to do this with a source module instead of a simple
macro in a simple header file?
Was there any reason to use '#include <config.h>' instead of
'#include "config.h"'? This hosed my original automatic dependency
generation, but a work-around was easy enough. It just seemed like a
difference from all the other non-system inclusions with no obvious (to
me) reason.
Currently, I'm working from a CVS collection taken on 11 April.
Assuming I can get this stuff organized in the next few days or so, what
would be the most convenient code base to use?
------------------------------------------------------------------------
Steven M. Schweda (+1) 651-699-9818
382 South Warwick Street [EMAIL PROTECTED]
Saint Paul MN 55105-2547
