List for cgit developers and users
 help / color / mirror / Atom feed
From: Markus Mayer <>
To: CGIT List <>
Cc: Markus Mayer <>
Subject: [PATCH 0/1] cgit for macOS
Date: Fri, 27 Jan 2023 15:15:42 -0800	[thread overview]
Message-ID: <> (raw)

Hi all,

I first proposed this change over two and a half years ago.[1]
Unfortunately, it never seemed to gain any traction. I figured I'd give
it another shot.

Adding this open-source implementation of memrchr() allows for CGIT to
be built on macOS. This can be very convenient, be it for CGIT
development or to have a local CGIT instance that'll work even without
network connection.

The change seems quite small and well contained (less than 60 lines of
code added; no other platform affected), and it enables an additional
platform/OS for CGIT.

Proof that it actually builds (x86 works too, of course):

$ file cgit
cgit: Mach-O 64-bit executable arm64

$ otool -L cgit
/System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices (...)
/usr/lib/libz.1.dylib (compatibility version 1.0.0, current version 1.2.11)
/usr/lib/libiconv.2.dylib (compatibility version 7.0.0, current version 7.0.0)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1319.0.0)



Markus Mayer (1):
  global: provide memrchr implementation for macOS

 cgit.h    |  4 ++++   |  9 +++++++++
 memrchr.c | 44 ++++++++++++++++++++++++++++++++++++++++++++
 3 files changed, 57 insertions(+)
 create mode 100644 memrchr.c


             reply	other threads:[~2023-01-27 23:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-27 23:15 Markus Mayer [this message]
2023-01-27 23:15 ` [PATCH 1/1] global: provide memrchr implementation " Markus Mayer
     [not found]   ` <>
2023-01-28  0:35     ` Markus Mayer
     [not found]       ` <Y9R3X7bhwUAWofJ/@xps13>
2023-01-29 21:43         ` Markus Mayer

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:

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

  git send-email \ \ \ \

* 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 NNTP newsgroup(s).