all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: 63330@debbugs.gnu.org
Subject: [bug#63330] [PATCH 0/4] Functional programming? In my C++?! It's more likely than you think!
Date: Sun, 07 May 2023 21:40:52 +0200	[thread overview]
Message-ID: <750a060f3435255a7765a0ee6df1ef60de46f483.camel@gmail.com> (raw)
In-Reply-To: <873548ysj8.fsf@gmail.com>

Hi,

Am Sonntag, dem 07.05.2023 um 13:12 -0400 schrieb Maxim Cournoyer:
> Liliana Marie Prikler <liliana.prikler@gmail.com> writes:
> 
> > Am Sonntag, dem 07.05.2023 um 11:30 -0400 schrieb Maxim Cournoyer:
> > > Did you report the wrong header usage upstream?  
> > I must admit, I did not.
> 
> Could you please do so, if that's not too much to ask?  Then include
> a (see: URL) next to the substitution comment.
I sent a mail to the address in the README; let's wait for a reply.

> > > A less intrusive fix for the catch/doctest include problem could
> > > be to add their include subdirectories as -I directives to the
> > > CXXFLAGS environment variable, or since that's CMake, via its
> > > CMAKE_CXX_FLAGS make options.  See 'clara' for an actual example.
> > There are other packages that take the approach I used here.  I do
> > think this is a CMakeFiles bug, but not one I want to fix.
Correction to myself: I now see that we only need to edit those source
files because we remove the bundled ones, but that's an argument
towards keeping that within the snippet imho. 

> I think catch2 is selfom used from the system (typically bundled),
> must not ship with any pkg-config or proper support to be auto-
> detected at configure time, which gives us the situation we're in.
Joke's on you, catch2 ships with both CMake's config stuff *and* pkg-
config.  Vendoring it is next to pointless (that is, unless you regard
sneaking it onto ancient Debian as the point).  Doctest also comes with
the usual CMake blurb.

Cheers




  reply	other threads:[~2023-05-07 20:03 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-06 16:04 [bug#63330] [PATCH 0/4] Functional programming? In my C++?! It's more likely than you think! Liliana Marie Prikler
2023-05-06 13:41 ` [bug#63330] [PATCH 2/4] gnu: Add immer Liliana Marie Prikler
2023-05-07 15:30   ` [bug#63330] [PATCH 0/4] Functional programming? In my C++?! It's more likely than you think! Maxim Cournoyer
2023-05-07 15:51     ` Liliana Marie Prikler
2023-05-07 17:12       ` Maxim Cournoyer
2023-05-07 19:40         ` Liliana Marie Prikler [this message]
2023-05-06 13:43 ` [bug#63330] [PATCH 3/4] gnu: Add zug Liliana Marie Prikler
2023-05-07 15:25   ` [bug#63330] [PATCH 0/4] Functional programming? In my C++?! It's more likely than you think! Maxim Cournoyer
2023-05-06 13:43 ` [bug#63330] [PATCH 4/4] gnu: Add lager Liliana Marie Prikler
2023-05-07 15:34   ` [bug#63330] [PATCH 0/4] Functional programming? In my C++?! It's more likely than you think! Maxim Cournoyer
2023-05-07 15:57     ` Liliana Marie Prikler
2023-05-07 17:10       ` Maxim Cournoyer
2023-05-11 13:23         ` Simon Tournier
2023-05-14 10:31           ` bug#63330: " Liliana Marie Prikler
2023-05-06 13:51 ` [bug#63330] [PATCH 1/4] gnu: Add c-rrb Liliana Marie Prikler

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=750a060f3435255a7765a0ee6df1ef60de46f483.camel@gmail.com \
    --to=liliana.prikler@gmail.com \
    --cc=63330@debbugs.gnu.org \
    --cc=maxim.cournoyer@gmail.com \
    /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.