all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Hartmut Goebel <h.goebel@crazy-compilers.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 69554@debbugs.gnu.org
Subject: [bug#69554] [PATCH v2] build-system: cmake: Build tests depending on `#:tests?`.
Date: Tue, 16 Jul 2024 17:36:49 +0200	[thread overview]
Message-ID: <079bf725-1855-498f-8863-d7ac7a6c6065@crazy-compilers.com> (raw)
In-Reply-To: <87ed7v0z8m.fsf@gnu.org>

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

Am 15.07.24 um 11:40 schrieb Ludovic Courtès:
> My understanding is that ‘BUILD_TESTING’ is not standard, as the last
> sentence above suggests.  Thus I’m reluctant to passing this flag
> unconditionally, as I guess it would fail for ‘CMakeLists.txt’ that do
> not implement it, right?

I just tested it, and all you get is a warning:

$ cat CMakeLists.txt
cmake_minimum_required(VERSION 3.0)
project(doo)
$ cmake -DBUILD_TESTING=OFF .
…
-- Generating done (0.0s)
CMake Warning:
  Manually-specified variables were not used by the project:

    BUILD_TESTING


-- Build files have been written to: /tmp/xxx


-- 

Regards
Hartmut Goebel

| Hartmut Goebel          |h.goebel@crazy-compilers.com                |
|www.crazy-compilers.com  | compilers which you thought are impossible |

[-- Attachment #2: Type: text/html, Size: 2262 bytes --]

  reply	other threads:[~2024-07-16 15:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-04 21:48 [bug#69554] [PATCH] build-system: cmake: Build tests depending on `#:tests?` Hartmut Goebel
2024-03-04 22:58 ` [bug#69554] [PATCH v2] " Hartmut Goebel
2024-07-15  9:40   ` Ludovic Courtès
2024-07-16 15:36     ` Hartmut Goebel [this message]
2024-10-07 15:45       ` Greg Hogan
2024-10-08  9:06         ` Hartmut Goebel
2024-10-08 17:19           ` Greg Hogan
2024-10-09  7:32             ` Hartmut Goebel
2024-10-09 15:04               ` Greg Hogan
2024-10-15  9:17                 ` bug#69554: " Hartmut Goebel

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=079bf725-1855-498f-8863-d7ac7a6c6065@crazy-compilers.com \
    --to=h.goebel@crazy-compilers.com \
    --cc=69554@debbugs.gnu.org \
    --cc=ludo@gnu.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. 
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.