From: Eli Zaretskii <eliz@gnu.org>
To: Alan Mackenzie <acm@muc.de>
Cc: emacs-devel@gnu.org
Subject: Re: Difficulty building tree-sitter grammars [was: Help sought from C++ expert: ....]
Date: Fri, 20 Jan 2023 08:44:39 +0200 [thread overview]
Message-ID: <83lelxogbs.fsf@gnu.org> (raw)
In-Reply-To: <Y8mubWj6GHxTRUIA@ACM> (message from Alan Mackenzie on Thu, 19 Jan 2023 20:56:13 +0000)
> Date: Thu, 19 Jan 2023 20:56:13 +0000
> Cc: emacs-devel@gnu.org
> From: Alan Mackenzie <acm@muc.de>
>
> > I'm not going to make NEWS a step-by-step tutorial for how to compile
> > a bunch of files into a shared library. That is too much to expect
> > from us. It is NOT our job to teach people how to do that.
>
> Believe it or not, I've never built a shared library in my life (aside
> from invoking makefiles) and I'm sure I'm far from being alone.
Like I said: then building the libraries is not something you should
try on your own.
> These libraries come with makefiles, so there is no need to get into the
> details of how to build them.
Only some of them come with Makefiles, the majority doesn't. Which is
why those Makefiles aren't mentioned in NEWS: you cannot rely on their
being there.
> At Dmitry pointed out, it turns out there's a makefile-equivalent for
> these grammar libraries, namely treesit-install-language-grammar. This
> worked well for me.
>
> Why is it not mentioned first in NEWS, something like "Typically you can
> build and install a grammar with ....." followed by "To build a grammar
> outside of Emacs ..." and the description of compiling linking and so on?
Isn't that already so?
But that command cannot solve all the problems for users who have no
experience in building from sources. So some of them will still need
someone else to do this.
next prev parent reply other threads:[~2023-01-20 6:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-19 14:53 Help sought from C++ expert: is this `value' a type or something else (what)? Alan Mackenzie
2023-01-19 14:59 ` Eli Zaretskii
2023-01-19 17:14 ` Difficulty building tree-sitter grammars [was: Help sought from C++ expert: ....] Alan Mackenzie
2023-01-19 17:53 ` Dmitry Gutov
2023-01-19 18:06 ` Eli Zaretskii
2023-01-19 18:16 ` Dmitry Gutov
2023-01-19 17:53 ` Eli Zaretskii
2023-01-19 20:56 ` Alan Mackenzie
2023-01-20 6:44 ` Eli Zaretskii [this message]
2023-01-19 15:41 ` Help sought from C++ expert: is this `value' a type or something else (what)? Michael Welsh Duggan
2023-01-21 14:34 ` Alan Mackenzie
2023-01-19 16:22 ` Óscar Fuentes
2023-01-21 14:59 ` Alan Mackenzie
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: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83lelxogbs.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=acm@muc.de \
--cc=emacs-devel@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 public inbox
https://git.savannah.gnu.org/cgit/emacs.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).