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 13:40:00 +0200 Message-ID: <86seqyflnz.fsf@gnu.org> References: Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="19048"; 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 12:40:36 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 1tKFeN-0004nP-DA for geh-help-gnu-emacs@m.gmane-mx.org; Sun, 08 Dec 2024 12:40:35 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1tKFdu-0002QU-Iq; Sun, 08 Dec 2024 06:40:06 -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 1tKFds-0002QH-Mg for help-gnu-emacs@gnu.org; Sun, 08 Dec 2024 06:40:04 -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 1tKFds-0000vB-CP for help-gnu-emacs@gnu.org; Sun, 08 Dec 2024 06:40:04 -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=A4tm64a0ncR0vaurAXWDGWMtVuO3U9F7xnU2yfNUWaU=; b=TwcAMSk+kaTl T2shROWbd+Gf7uZTIA/djcphcJCghMcIErfdXkBNa0pjMWQh8LaReUTPjgRxtVZifqEPB9sLfmQG0 HVKcLrtwCd+OUJ1rycycMLgaSxIPTCHcNkX1dRO5GnETkrA7p0AP5buSx6vYMO2NhOybi+nD0HN1Q 8pZO0gp9YEiqhmmFOxJ6I3HuiWzr6pTZ60QORlp1wfLOsgEfcYFFLsXZmQGvUCpWqFvs0UPulTbUO 55bd3yLP424mFyx7GxXQEkYN4ItlWjGn8Eax7eBwQEB1hmwwOYR1WWmIqsmR+aegXxvMDrlN5MibO +NQgNaYkBRoaPD6eob1v1A==; In-Reply-To: (message from Marco Antoniotti on Sun, 8 Dec 2024 10:59:28 +0100) 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:148674 Archived-At: > From: Marco Antoniotti > Date: Sun, 8 Dec 2024 10:59:28 +0100 > > Sorry Eli > > your solution is not portable and it doesn't work on Mac and Windows (29.2) > > On Mac the following works > > ELISP> (expand-file-name "../include" data-directory) > "/Applications/Emacs.app/Contents/Resources/include" > > On Windows the include folder is "higher" up. > "C:\Program Files\Emacs\emacs-29.2\include\" Sorry, I used too few "..". The correct way is (expand-file-name "../../../../include" data-directory) > Given that people (like me) are experimenting with emacs modules, I'd lobby > for the introduction of a 'include-direcotry' variable. 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?