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.help Subject: Re: Retrieving the "include" directory for Emacs Modules Date: Sun, 08 Dec 2024 18:39:07 +0200 Message-ID: <86bjxmf7tg.fsf@gnu.org> References: <86seqyflnz.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="12655"; mail-complaints-to="usenet@ciao.gmane.io" To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Sun Dec 08 17:39:58 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 1tKKK5-0003BD-LS for geh-help-gnu-emacs@m.gmane-mx.org; Sun, 08 Dec 2024 17:39:57 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1tKKJm-0006vr-Lz; Sun, 08 Dec 2024 11:39:38 -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 1tKKJj-0006vV-RK for help-gnu-emacs@gnu.org; Sun, 08 Dec 2024 11:39:36 -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 1tKKJh-0001s8-Ro for help-gnu-emacs@gnu.org; Sun, 08 Dec 2024 11:39:34 -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=U7TKCFYg0aTBAgRbnHmpv44IT5fnBWqRc/JOwzWXN1g=; b=nR5LRA+T05vY G0iWlWIwJU5q+dvwOfEwt2PbCN8eUcuVw6B/bF+5YKdBamDMWD51+dsJfaf5It9PbTsVmEhmG4++7 7TnQhSo9Yv3qBMsn55cohze+n4hpU/lHdNDjZHk1+jf2UqgvJwXFm+Qe0PRLC/jOuVr9Sm8+FTlSc vSsJOXWGWCoocG/h+2MKIPvVbwEa7JMB9XeMGKLnFuCgod7/7VAVWr1EEwAWYr+DN/93oTKsSggxK RAVDXvUXS6mWzPgomMcVi4VbPePQKKKOCceHh3YtuOtaDOfnwSnEVIIAqNKo1HQc7qxeq0f2+BjoF YVZQWHsrkgBjVrrtf8ijsA==; In-Reply-To: (message from Stefan Monnier via Users list for the GNU Emacs text editor on Sun, 08 Dec 2024 10:47:54 -0500) 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:148697 Archived-At: > Date: Sun, 08 Dec 2024 10:47:54 -0500 > From: Stefan Monnier via Users list for the GNU Emacs text editor > > > I honestly don't understand why you need this at all. emacs-module.h > > is supposed to be installed in the compilers include tree, where the > > compiler looks for header files by default. So you shouldn't even > > need to know where the header lives, in order to compile a module. > > The module's code should just do > > > > #include > > > > and that's it. Or what am I missing? > > That presumes that Emacs is installed system-wide (and "properly"). What other way is there to install Emacs? > When the compilation of the module is initiated from within Emacs, it > would make a lot of sense for this "ambient" Emacs to be able to tell > `make/gcc/younameit` explicitly and reliably where its own > `emacs-module.h` can be found. But if Emacs is "not installed properly", we don't know that.