bug-gnulib@gnu.org mirror (unofficial)
 help / color / mirror / Atom feed
From: Simon Josefsson via Gnulib discussion list <bug-gnulib@gnu.org>
To: bug-gnulib@gnu.org
Subject: [PATCH] doc: Repeat warning that --with-tests cannot be used twice.
Date: Mon, 04 Jan 2021 01:12:46 +0100	[thread overview]
Message-ID: <87eej1muf5.fsf@latte.josefsson.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1749 bytes --]

Hi.  I am experimenting with using bootstrap+gnulib in a project that
has a library and a command-line tool, and thus needs two gnulib
instances.  The limitation that --with-tests cannot be used in this case
is helpful to repeat in the relevant section, it caused hard to
understand build errors.

Does anyone know whether it will work to have ONE gnulib tests
directory, or if having two gnulib instances causes even a single gnulib
tests directory to be unreliable?  It appears to be working for me with
one directory, so I'll keep doing that to notice breakage.

/Simon

* doc/gnulib-tool.texi (Multiple instances): Remind reader of
--with-tests limitation.
---
 ChangeLog            | 5 +++++
 doc/gnulib-tool.texi | 3 +++
 2 files changed, 8 insertions(+)

diff --git a/ChangeLog b/ChangeLog
index 6c042f567..3bd13281b 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,8 @@
+2021-01-04  Simon Josefsson  <simon@josefsson.org>
+
+	* doc/gnulib-tool.texi (Multiple instances): Remind reader of
+	--with-tests limitation.
+
 2021-01-03  Bruno Haible  <bruno@clisp.org>
 
 	iconv, iconv_open: Improve documentation.
diff --git a/doc/gnulib-tool.texi b/doc/gnulib-tool.texi
index 3dc6bf002..f3b034f85 100644
--- a/doc/gnulib-tool.texi
+++ b/doc/gnulib-tool.texi
@@ -673,6 +673,9 @@ in the interest of brevity):
     `-- Makefile.am
 @end example
 
+As discussed in @ref{Unit tests}, you may not use @samp{--with-tests}
+for this project since the @code{configure.ac} is shared.
+
 Integration with your code is basically the same as outlined in
 @ref{Initial import} with the one exception that you have to add both
 the macro @code{gl_EARLY} and the macro @code{gl_tools_EARLY} to your
-- 
2.20.1


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]

                 reply	other threads:[~2021-01-04  0:13 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

  List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib

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

  git send-email \
    --in-reply-to=87eej1muf5.fsf@latte.josefsson.org \
    --to=bug-gnulib@gnu.org \
    --cc=simon@josefsson.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).