public inbox for
 help / color / mirror / Atom feed
From: Brian Inglis <>
Subject: Re: [EXTERNAL] Re: [PATCH] Cygwin: Conditionally build documentation
Date: Sat, 15 Jan 2022 16:00:48 -0700	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On 2022-01-15 12:06, Lavrentiev, Anton (NIH/NLM/NCBI) [C] via 
Cygwin-patches wrote:
>> It is reported by 'configure --help', at the appropriate level (although
>> since enable is the default, I probably should have written
>> '--disable-doc' here).
> I'm sorry if I'm missing anything, but I updated y'day and this is what I see regarding the doc in configure:
> $ ./configure --help | grep doc
>    --infodir=DIR           info documentation [DATAROOTDIR/info]
>    --mandir=DIR            man documentation [DATAROOTDIR/man]
>    --docdir=DIR            documentation root [DATAROOTDIR/doc/PACKAGE]
>    --htmldir=DIR           html documentation [DOCDIR]
>    --dvidir=DIR            dvi documentation [DOCDIR]
>    --pdfdir=DIR            pdf documentation [DOCDIR]
>    --psdir=DIR             ps documentation [DOCDIR]

It looks like it's not propagated to newlib-cygwin/configure, and 
newlib-cygwin/configure --help=recursive seems to loop recursing on 
newlib 4.2.0, so it's only shown by winsup/configure:

$ ../winsup/configure --help=short
Configuration of Cygwin 0:

Optional Features:
   --disable-option-checking  ignore unrecognized --enable/--with options
   --disable-FEATURE       do not include FEATURE (same as 
   --enable-FEATURE[=ARG]  include FEATURE [ARG=yes]
   --enable-silent-rules   less verbose build output (undo: "make V=1")
   --disable-silent-rules  verbose build output (undo: "make V=0")
                           do not reject slow dependency extractors
                           speeds up one-time build
   --enable-debugging      Build a cygwin DLL which has more consistency
                           checking for debugging
   --enable-doc            Build documentation

Optional Packages:
   --with-PACKAGE[=ARG]    use PACKAGE [ARG=yes]
   --without-PACKAGE       do not use PACKAGE (same as --with-PACKAGE=no)
   --with-cross-bootstrap  do not build programs using the MinGW 
toolchain or
                           check for MinGW libraries (useful for 
                           a cross-compiler)

Some influential environment variables:
   CC          C compiler command
   CFLAGS      C compiler flags
   LDFLAGS     linker flags, e.g. -L<lib dir> if you have libraries in a
               nonstandard directory <lib dir>
   LIBS        libraries to pass to the linker, e.g. -l<library>
   CPPFLAGS    (Objective) C/C++ preprocessor flags, e.g. -I<include dir> if
               you have headers in a nonstandard directory <include dir>
   CXX         C++ compiler command
   CXXFLAGS    C++ compiler flags
   CPP         C preprocessor
   CCAS        assembler compiler command (defaults to CC)
   CCASFLAGS   assembler compiler flags (defaults to CFLAGS)

Use these variables to override the choices made by `configure' or to help
it to find libraries and programs with nonstandard names/locations.

Report bugs to <>.
Cygwin home page: <>.

Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]

  reply	other threads:[~2022-01-15 23:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-14 20:18 Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2022-01-15  5:04 ` Brian Inglis
2022-01-15 15:06 ` Jon Turney
2022-01-15 19:06   ` [EXTERNAL] " Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2022-01-15 23:00     ` Brian Inglis [this message]
2022-01-18 20:01       ` Jon Turney
2022-01-17 19:39   ` Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2022-01-18 19:57     ` Jon Turney

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).