all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Arash Esbati <arash@gnu.org>
To: Darren Kenny <darren.kenny@oracle.com>
Cc: emacs-devel <emacs-devel@gnu.org>, john@palkovic.org
Subject: Re: Instructions for building Emacs with homebrew
Date: Tue, 11 Jul 2023 21:42:19 +0200	[thread overview]
Message-ID: <86y1jmxmjo.fsf@gnu.org> (raw)
In-Reply-To: <m28rc13uxv.fsf@oracle.com> (Darren Kenny's message of "Fri, 30 Jun 2023 15:07:24 +0100")

Darren Kenny <darren.kenny@oracle.com> writes:

> I don't know if you've seen this script, and the details that it has:
>
> - https://github.com/jimeh/build-emacs-for-macos
>
> I've been using this to build my version of Emacs for a while now on an
> M1, and usually it 'just works'.

Thanks for your message and sorry for my late response.  I did some
research and found the script above and also others like:

  • https://github.com/d12frosted/homebrew-emacs-plus

and a lot of blog entries like:

  • https://lars.ingebrigtsen.no/2020/08/02/emacs-on-macos-for-linux-peepshttps://andersmurphy.com/2021/11/14/emacs-building-from-source-on-macos.html

And I agree with Lars who writes:

  So I wondered what you'd have to do to build Emacs under Macos, and
  ...  I found a bunch of people talking about how easy it is, but nobody
  actually, like, says how to do it.

Hence my question about a canonical recipe for building Emacs under
macOS.  And I don't want to use a patched version of Emacs, that would
make submitting bug reports more complicated.  So I will start building
Emacs with homebrew and see how far I get.

Best, Arash



      parent reply	other threads:[~2023-07-11 19:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-30 12:24 Instructions for building Emacs with homebrew Arash Esbati
     [not found] ` <m28rc13uxv.fsf@oracle.com>
2023-07-11 19:42   ` Arash Esbati [this message]

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=86y1jmxmjo.fsf@gnu.org \
    --to=arash@gnu.org \
    --cc=darren.kenny@oracle.com \
    --cc=emacs-devel@gnu.org \
    --cc=john@palkovic.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/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.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.