From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.help Subject: Re: Retrieving the "include" directory for Emacs Modules Date: Tue, 24 Dec 2024 00:06:07 -0500 Message-ID: References: <86ttbcdhwn.fsf@gnu.org> <865xnscj0s.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="22821"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Cc: Stefan Monnier via Users list for the GNU Emacs text editor To: =?windows-1252?Q?Bj=F6rn?= Bidar Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Tue Dec 24 06:07:18 2024 Return-path: Envelope-to: geh-help-gnu-emacs@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 1tPx8X-0005my-Mp for geh-help-gnu-emacs@m.gmane-mx.org; Tue, 24 Dec 2024 06:07:17 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1tPx7q-0007If-Cp; Tue, 24 Dec 2024 00:06:34 -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 1tPx7k-0007Hz-BJ for help-gnu-emacs@gnu.org; Tue, 24 Dec 2024 00:06:29 -0500 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1tPx7U-00017f-7g for help-gnu-emacs@gnu.org; Tue, 24 Dec 2024 00:06:14 -0500 Original-Received: from pmg1.iro.umontreal.ca (localhost.localdomain [127.0.0.1]) by pmg1.iro.umontreal.ca (Proxmox) with ESMTP id 3B40110004C; Tue, 24 Dec 2024 00:06:09 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1735016768; bh=h51J4vZe80R9CP1mtkYVwCPoZhjZoyrlcES9qSuJnFM=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=JLZ2MxHjl2FELRVQbRw7q+y9nehUPsoIveQhRJLYocfkCYKwi/i1Q3gNTca0nklMT Og2etUtrpFphLRX3FvrMJmeZ53nN8fNiJnnaMwagFRvp4f5z4y42N+rg1SrNQ6oC/T drobZWiJU88F/GxnODCop0q63u7N83ZhukdEVstQx8AGURAbLVodAAwQCGRN+OvgAq ES4GCaFZPjOIevJYGwfu923vlWfP+/ydDDguAHivaCCTmgUg5AU1PfWQAoeaA2taIG F1oqN0lR4rm5xGYD0biKEccEXeNBczntoAnlist5kA7z87S9Wi7ixT5I3t9oUCT0A5 1wfHEs0kOKrCw== Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg1.iro.umontreal.ca (Proxmox) with ESMTP id 3987A100035; Tue, 24 Dec 2024 00:06:08 -0500 (EST) Original-Received: from pastel (104-195-225-43.cpe.teksavvy.com [104.195.225.43]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id 113B81202C1; Tue, 24 Dec 2024 00:06:08 -0500 (EST) In-Reply-To: <871pxzxlfe.fsf@> (=?windows-1252?Q?=22Bj=F6rn?= Bidar"'s message of "Mon, 23 Dec 2024 03:00:53 +0200") Received-SPF: pass client-ip=132.204.25.50; envelope-from=monnier@iro.umontreal.ca; helo=mailscanner.iro.umontreal.ca X-Spam_score_int: -42 X-Spam_score: -4.3 X-Spam_bar: ---- X-Spam_report: (-4.3 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.help:148941 Archived-At: >>>> That's OK: the sole purpose of the change is to let ELPA packages call >>>> `gcc` with such a `-I`! >>> Which is wrong for Unix-like systems except on macOS. >> In which sense would it be wrong? >> I can see an argument that such a `-I` would tend to be redundant on >> systems where Emacs was "installed properly", but even on those systems >> I fail to see what would be "wrong" about it. > Headers don't go the Emacs data directory but in the include directory, > usually /usr/include or /usr/local/include. "Unusual" doesn't mean "wrong". So, I don't think it's a valid description of something that would be "wrong" about it. [ BTW, `locate '*.h' | sed 's|[^/]*$||' | sort -u` on this Debian system suggests Emacs would be far from the only package to place header files outside of `/usr/include` or `/usr/local/include`. ] > I don't think about imposing anything but keeping in mind that modules > built arbitrary native code which can bring it's own issues especially > when external dependencies come into play. Indeed, beside finding Emacs's own header file, there can be various other hurdles to making a module that can be built on "all" systems. > I wonder if there's something that could be learned from XEmacs approach > of emodules which were very similar. I'd be surprised if there isn't something to learn from them, indeed. > Especially the idea of ellcc[1] sounds very good in this context. AFAICT this deals with the issue of how to build a "shared lib" kind of object file, IOW something that solves the same kinds of problem that Libtool aims to solve, right? Maybe we should develop a "module-helper" package which provides various helpers to build modules. Stefan