public inbox for cygwin-cvs@sourceware.org
help / color / mirror / Atom feed
From: Jon Turney <jturney@sourceware.org>
To: cygwin-cvs@sourceware.org
Subject: [newlib-cygwin] Cygwin: configure: Add option to disable building 'dumper'
Date: Wed, 21 Dec 2022 11:48:50 +0000 (GMT)	[thread overview]
Message-ID: <20221221114850.B2442385802F@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=newlib-cygwin.git;h=1b5fc91a1daa90fb955f57937f4590c5079dd161

commit 1b5fc91a1daa90fb955f57937f4590c5079dd161
Author: Jon Turney <jon.turney@dronecode.org.uk>
Date:   Tue Dec 13 23:17:48 2022 +0000

    Cygwin: configure: Add option to disable building 'dumper'
    
    Rather than guessing, based on just the presence of libbfd, add an
    explicit configuration option, to build dumper or not, defaulting to
    building it.
    
    This might have some use when bootstrapping Cygwin for a new
    architecture, or when building your own Cygwin-targetted cross-compiler,
    rather than installing one from the copr, along with the dependencies of
    libbfd.

Diff:
---
 winsup/configure.ac            | 8 +++++---
 winsup/doc/faq-programming.xml | 3 ++-
 2 files changed, 7 insertions(+), 4 deletions(-)

diff --git a/winsup/configure.ac b/winsup/configure.ac
index 9205a8886..7a2121dae 100644
--- a/winsup/configure.ac
+++ b/winsup/configure.ac
@@ -111,10 +111,12 @@ AM_CONDITIONAL(CROSS_BOOTSTRAP, [test "x$with_cross_bootstrap" != "xyes"])
 
 AC_EXEEXT
 
-AC_CHECK_LIB([bfd], [bfd_init], [true],
-	     AC_MSG_WARN([Not building dumper.exe since some required libraries or headers are missing]))
+AC_ARG_ENABLE([dumper],
+	      [AS_HELP_STRING([--disable-dumper], [do not build the 'dumper' utility])],
+	      [build_dumper=$enableval],
+	      [build_dumper=yes])
 
-AM_CONDITIONAL(BUILD_DUMPER, [test "x$ac_cv_lib_bfd_bfd_init" = "xyes"])
+AM_CONDITIONAL(BUILD_DUMPER, [test "x$build_dumper" = "xyes"])
 
 AC_CONFIG_FILES([
     Makefile
diff --git a/winsup/doc/faq-programming.xml b/winsup/doc/faq-programming.xml
index a24b781cf..24c7f928e 100644
--- a/winsup/doc/faq-programming.xml
+++ b/winsup/doc/faq-programming.xml
@@ -685,7 +685,8 @@ installed; you at least need <literal>gcc-g++</literal>,
 <para>
 Additionally, building the <code>dumper</code> utility requires
 <literal>gettext-devel</literal>, <literal>libiconv-devel</literal>
-<literal>zlib-devel</literal>.
+<literal>zlib-devel</literal>.  Building this program can be disabled with the
+<literal>--disable-dumper</literal> option to <literal>configure</literal>.
 </para>
 
 <para>

                 reply	other threads:[~2022-12-21 11:48 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

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

  git send-email \
    --in-reply-to=20221221114850.B2442385802F@sourceware.org \
    --to=jturney@sourceware.org \
    --cc=cygwin-cvs@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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).