* Bundling Gnulib tests with an application
@ 2020-05-24 8:34 Marc Nieper-Wißkirchen
2020-05-31 19:51 ` Bruno Haible
0 siblings, 1 reply; 3+ messages in thread
From: Marc Nieper-Wißkirchen @ 2020-05-24 8:34 UTC (permalink / raw)
To: bug-gnulib
[-- Attachment #1: Type: text/plain, Size: 545 bytes --]
When an application bundles Gnulib tests in its distribution, say in a
folder named gnulib-tests, and has its own suite of Automake tests in the
folder tests, the console output by Automake when running
make check
is suboptimal because it will print something like
====================================
Testsuite summary for MyProgram 1.0
====================================
twice, once when processing the tests folder and once when processing the
gnulib-tests folder.
Is there a way to change the title that is printed by Automake?
Marc
[-- Attachment #2: Type: text/html, Size: 1339 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Bundling Gnulib tests with an application
2020-05-24 8:34 Bundling Gnulib tests with an application Marc Nieper-Wißkirchen
@ 2020-05-31 19:51 ` Bruno Haible
2020-06-02 9:33 ` Marc Nieper-Wißkirchen
0 siblings, 1 reply; 3+ messages in thread
From: Bruno Haible @ 2020-05-31 19:51 UTC (permalink / raw)
To: bug-gnulib; +Cc: Marc Nieper-Wißkirchen
Marc Nieper-Wißkirchen wrote:
> When an application bundles Gnulib tests in its distribution, say in a
> folder named gnulib-tests, and has its own suite of Automake tests in the
> folder tests, the console output by Automake when running
>
> make check
>
> is suboptimal because it will print something like
>
> ====================================
> Testsuite summary for MyProgram 1.0
> ====================================
>
> twice, once when processing the tests folder and once when processing the
> gnulib-tests folder.
>
> Is there a way to change the title that is printed by Automake?
I'm not aware of a documented way to change this.
Nevertheless, it is probably easy to do: When you look at the generated
Makefile.in and search for the string 'summary for', you will see that
it gets the text that follows it from a Makefile variable. This Makefile
variable gets its default value from the configure file. But if you
set a value in Makefile.am, it will override the value from the configure
file - locally in that Makefile only.
Bruno
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Bundling Gnulib tests with an application
2020-05-31 19:51 ` Bruno Haible
@ 2020-06-02 9:33 ` Marc Nieper-Wißkirchen
0 siblings, 0 replies; 3+ messages in thread
From: Marc Nieper-Wißkirchen @ 2020-06-02 9:33 UTC (permalink / raw)
To: Bruno Haible; +Cc: Marc Nieper-Wißkirchen, bug-gnulib
Am So., 31. Mai 2020 um 21:51 Uhr schrieb Bruno Haible <bruno@clisp.org>:
> I'm not aware of a documented way to change this.
>
> Nevertheless, it is probably easy to do: When you look at the generated
> Makefile.in and search for the string 'summary for', you will see that
> it gets the text that follows it from a Makefile variable. This Makefile
> variable gets its default value from the configure file. But if you
> set a value in Makefile.am, it will override the value from the configure
> file - locally in that Makefile only.
That's a great tip, thank you. And, maybe, it is a good idea to
automatically wire this into the test suite generated by Gnulib.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2020-06-02 9:33 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-05-24 8:34 Bundling Gnulib tests with an application Marc Nieper-Wißkirchen
2020-05-31 19:51 ` Bruno Haible
2020-06-02 9:33 ` Marc Nieper-Wißkirchen
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).