From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Tree-sitter introduction documentation Date: Tue, 27 Dec 2022 20:06:23 +0200 Message-ID: <834jtg202o.fsf@gnu.org> References: <83edszjslp.fsf@gnu.org> <87tu1vxs3a.fsf@ledu-giraud.fr> <831qozjob7.fsf@gnu.org> <87cz8jxoat.fsf@ledu-giraud.fr> <83wn6ri7pn.fsf@gnu.org> <5e0a3185-de82-b339-0fa2-956779e63d6f@cornell.edu> <868rj6vfep.fsf@gmail.com> <4895891b-e5ea-9c37-f51b-df2e479ee758@yandex.ru> <83y1qt11xq.fsf@gnu.org> <9eb013da-d0fc-8e17-c6e3-1e8f913aebfa@yandex.ru> <83pmc50xxc.fsf@gnu.org> <71cfe4e8-3bb8-b0a6-9be5-8c0a6d92cfab@yandex.ru> <83h6xg29z3.fsf@gnu.org> <87wn6cyey5.fsf@posteo.net> <837cyc22dz.fsf@gnu.org> <87o7royd9e.fsf@posteo.net> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="40716"; mail-complaints-to="usenet@ciao.gmane.io" Cc: monnier@iro.umontreal.ca, dgutov@yandex.ru, theophilusx@gmail.com, emacs-devel@gnu.org To: Philip Kaludercic Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue Dec 27 19:07:36 2022 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pAEMS-000AJj-DN for ged-emacs-devel@m.gmane-mx.org; Tue, 27 Dec 2022 19:07:36 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pAELI-0003HO-VQ; Tue, 27 Dec 2022 13:06:24 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pAELD-0003Gp-Ve for emacs-devel@gnu.org; Tue, 27 Dec 2022 13:06:19 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pAELB-0005Td-S8; Tue, 27 Dec 2022 13:06:18 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=31Hfl1cMK15Ma8bcp8UTC3/5W5jBELGeuYH7/nazZ7M=; b=A6K0AnCAM6pZ C13PyjQz/fADoD16sEQisbQyz+IaXSxnPDul30Cuoyli1XfL8TfJ3/YjsicM/akdvdKRw6hW4yBFx jw2rIzMRkE72CQ/3X5NC2IdjzlrlhX+8IZZwWC4Fn111JeVU0XXL1NV90AIDkCcdKrTdWp0dfZ2Zy WWnVe1SN+fgUMmQnjbiqwZaUgT9EL7rqal6dbDIA5NW/HBXdpKouU3Ytz77aoNYPYBxMn4qAYXucB PDewEUpHV5w5ED9cxp/EZ2dpdGSBUpEfjIzfJ+XFuzdP7TVqnwHccxmZdl26OGfpmS8SVJI77KIZt XeYGNT937wRXKJ0jsTIE1Q==; Original-Received: from [87.69.77.57] (helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pAELA-0005K5-Qi; Tue, 27 Dec 2022 13:06:17 -0500 In-Reply-To: <87o7royd9e.fsf@posteo.net> (message from Philip Kaludercic on Tue, 27 Dec 2022 17:20:29 +0000) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:301980 Archived-At: > From: Philip Kaludercic > Cc: monnier@iro.umontreal.ca, dgutov@yandex.ru, theophilusx@gmail.com, > emacs-devel@gnu.org > Date: Tue, 27 Dec 2022 17:20:29 +0000 > > > It _is_ as simple as above (modulo the need to detect C++ sources and > > use g++ in that case). And I already said that such a command will > > have its place in Emacs (and Stefan agrees, AFAIU). So there should > > be no argument anymore about the possibility; it's just a matter of > > Someone sitting down and coding the darn thing. Like everything else > > in Emacs. > > I'd be glad to help, if I knew what the interface/input/output should > be. But I'm guessing that is half the work. I already did that half ;-) Here's a simple Makefile I use to build (almost) all the grammar libraries: PARSER_NAME = $(notdir $(abspath $(CURDIR)/..)) DLL = $(addsuffix .dll,$(addprefix lib,$(PARSER_NAME))) CPPSRC := $(filter-out schema.generated.cc,$(filter-out binding.cc,$(wildcard *.cc))) SRC := $(wildcard *.c) SRC += $(CPPSRC) OBJ := $(addsuffix .o,$(basename $(SRC))) CC = gcc ifeq (, $(CPPSRC)) CCLD = gcc else CCLD = g++ endif CFLAGS = -O2 -I. CXXFLAGS = -O2 -I. all: $(DLL) $(DLL): $(OBJ) $(CCLD) $(LDFLAGS) -shared $^ $(LDLIBS) -ltree-sitter -o $@ This is for Windows, thus "DLL" and stuff, not .so. Also, Posix platforms need -fPIC compiler switch. There are a couple of grammars that need a slightly more complex approach, because their repositories produce more than one shared library. One notable example is tree-sitter-typescript (which Emacs uses). HTH