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 19:46:11 +0200 Message-ID: <865xnuf4po.fsf@gnu.org> References: <86seqyflnz.fsf@gnu.org> <86bjxmf7tg.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="11675"; 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 18:46:55 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 1tKLMs-0002uu-SG for geh-help-gnu-emacs@m.gmane-mx.org; Sun, 08 Dec 2024 18:46:55 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1tKLMI-0003NZ-4g; Sun, 08 Dec 2024 12:46:18 -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 1tKLMF-0003K9-Rv for help-gnu-emacs@gnu.org; Sun, 08 Dec 2024 12:46:15 -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 1tKLMF-0000cR-KF for help-gnu-emacs@gnu.org; Sun, 08 Dec 2024 12:46:15 -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=cSXeqYdWJ3ssZCjglelkITIJT8HyOcqHUvLnRt16wCE=; b=Pru7CkFSzGDG ZtYs3ksTz8mvmHBrQ9Ya5N7f0vidBmL+0lnCShuWnWowyNkz+t+8GHdmUo9CwcAyoNARkpj/z23Mt HnMNVtnmwODT37CYg9P6oF7OHFbgzeku3rQ9w9CjsoNZW7Zfq1ZOSrqt0aLHY6nn0Iw/1abmzqssh UMHgVmV7TpDn21tfedgKdxLQkWe8LnNJ0eq0g0W8x/w8ynS2ykAAyZg19luc9KHetZcw+It7sjGCJ CasC8Neg/fp4UVhC3O1tTtx3/Wbk+o27VMm3mh2WRbdwxGNLxLe3NVFMf0WrWL/g58ZItZ68G5Upq WdJGfdc1JCmh2TTkF4mvBQ==; In-Reply-To: (message from Stefan Monnier via Users list for the GNU Emacs text editor on Sun, 08 Dec 2024 11:48:24 -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:148699 Archived-At: > Date: Sun, 08 Dec 2024 11:48:24 -0500 > From: Stefan Monnier via Users list for the GNU Emacs text editor > > >> > #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? > > Compile manually and run from the build tree? That's called "run uninstalled". And in that case, the user who does that knows very well where the header lives: in the same directory from which he/she runs Emacs. > Uncompress a downloaded pre-compiled archive into a directory and just > use it from there (AFAIK, very common under macOS and Windows)? If that doesn't place emacs-module.h in the system-wide include directory, it is a broken installation. > With luck on some systems the C (or other) compiler is installed in > a similar way (i.e. in its own subdirectory, siloed from Emacs). That's not how multi-package installation should be organized if the user wants the packages to cooperate. > >> 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. > > Emacs *should* know that, just like it knows where is its > `lisp-directory`. That's impractical expectation. Recall how hard we worked to find the pdumper file and the preloaded *.eln files, what with all the tricks people use when installing Emacs. I'm not interested in adding another burden to our maintenance so that Emacs will paper over broken installations. Sorry.