git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Ilya Kantor <iliakan@gmail.com>
Cc: git@vger.kernel.org, Junio C Hamano <junio@pobox.com>,
	Johannes Schindelin <Johannes.Schindelin@gmx.de>
Subject: Re: CMakeLists.txt from contrib/buildsystems fails to build on Mac
Date: Wed, 08 Feb 2023 12:57:35 +0100	[thread overview]
Message-ID: <230208.86sffgz7i1.gmgdl@evledraar.gmail.com> (raw)
In-Reply-To: <BFC8139A-0A9A-4E84-BC0B-D6EE5F469F82@gmail.com>


On Wed, Feb 08 2023, Ilya Kantor wrote:

> May that be because of some changes in MacOs Ventura? 
> Or is the CMakeLists.txt "dead and forgotten"? ;)
>
> P.S. The regular "make" route works.

You should just use "make", the "cmake" build method is currently in
some limbo. See my
https://lore.kernel.org/git/221227.86pmc4vrk3.gmgdl@evledraar.gmail.com/
for a recent overview/questions about it.

Since I wrote that 0949eba7fd0 (diagnose: another dup2() leak,
2022-12-06) landed on git.git's master, so we don't run it ourselves in
CI, even for Windows (which it was intended for).

As noted in previous exchanges I wouldn't mind fixing it up to work on
more platforms, but Junio wasn't enthusiastic about those patches &
dropped them.

Alternatively I think the best thing to do is to "git rm" it from
git.git, and leave it to git-for-windows. From what I understood from
Johannes he preferred that plan.

Or rather, that GFW would be fixing it up, but then I don't see why it
should be in git.git, which as your message shows just leads to
confusion about why this component is in git.git's tree.

  reply	other threads:[~2023-02-08 12:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-08 11:45 CMakeLists.txt from contrib/buildsystems fails to build on Mac Ilya Kantor
2023-02-08 11:57 ` Ævar Arnfjörð Bjarmason [this message]
2023-02-08 14:31   ` Phillip Wood
2023-02-08 14:34     ` Ilya Kantor
2023-02-08 16:53     ` Junio C Hamano

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: http://vger.kernel.org/majordomo-info.html

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

  git send-email \
    --in-reply-to=230208.86sffgz7i1.gmgdl@evledraar.gmail.com \
    --to=avarab@gmail.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=iliakan@gmail.com \
    --cc=junio@pobox.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 public inbox

	https://80x24.org/mirrors/git.git

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