From: "Liāu, Kiong-Gē 廖宮毅" <gongyi.liao@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org, Andrea Corallo <akrl@sdf.org>
Subject: Re: Native-comp branch compilation error on Windows
Date: Thu, 17 Dec 2020 15:06:52 -0600 [thread overview]
Message-ID: <CALKwrMD=iY2CgUo6JMoM9X_5Kz5t1_XHZpadxd58s4sry14s3g@mail.gmail.com> (raw)
In-Reply-To: <83a6uc6td5.fsf@gnu.org>
I see. On the other hand, the epaths.h generated by configure on Linux:
/* Hey Emacs, this is -*- C -*- code! */
/*
Copyright (C) 1993, 1995, 1997, 1999, 2001-2020 Free Software
Foundation, Inc.
This file is part of GNU Emacs.
GNU Emacs is free software: you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation, either version 3 of the License, or
(at your option) any later version.
GNU Emacs is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with GNU Emacs. If not, see <https://www.gnu.org/licenses/>. */
/* Together with PATH_SITELOADSEARCH, this gives the default value of
load-path, which is the search path for the Lisp function "load".
Configure (using "make epaths-force") sets this to
${standardlisppath}, which typically has a value like:
<datadir>/emacs/VERSION/lisp where datadir is eg /usr/local/share.
*/
#define PATH_LOADSEARCH
"/home/kiong-ge/.local/emacs/native-comp/share/emacs/28.0.50/lisp"
/* Like PATH_LOADSEARCH, but contains the relative path from the
installation directory.
*/
#define PATH_REL_LOADSEARCH "28.0.50/lisp"
/* Like PATH_LOADSEARCH, but contains the non-standard pieces.
These are the site-lisp directories. Configure sets this to
${locallisppath}, which typically defaults to something like:
<datadir>/emacs/VERSION/site-lisp:<datadir>/emacs/site-lisp
but can be overridden by the --enable-locallisppath argument.
This is combined with PATH_LOADSEARCH to make the default load-path.
If the --no-site-lisp option is used, this piece is excluded.
*/
#define PATH_SITELOADSEARCH
"/home/kiong-ge/.local/emacs/native-comp/share/emacs/28.0.50/site-lisp:/home/kiong-ge/.local/emacs/native-comp/share/emacs/site-lisp"
/* Like PATH_LOADSEARCH, but used only during the build process
when Emacs is dumping. Configure (using "make epaths-force") sets
this to $buildlisppath, which normally has the value: <srcdir>/lisp.
*/
#define PATH_DUMPLOADSEARCH
"/home/kiong-ge/Downloads/emacs/native-comp/build/../src/lisp"
/* The extra search path for programs to invoke. This is appended to
whatever the PATH environment variable says to set the Lisp
variable exec-path and the first file name in it sets the Lisp
variable exec-directory. exec-directory is used for finding
executables and other architecture-dependent files. */
#define PATH_EXEC
"/home/kiong-ge/.local/emacs/native-comp/libexec/emacs/28.0.50/x86_64-pc-linux-gnu"
/* Where Emacs should look for its architecture-independent data
files, like the NEWS file. The lisp variable data-directory
is set to this value. */
#define PATH_DATA
"/home/kiong-ge/.local/emacs/native-comp/share/emacs/28.0.50/etc"
/* Where Emacs should look for X bitmap files.
The lisp variable x-bitmap-file-path is set based on this value. */
#define PATH_BITMAPS "/usr/include/X11/bitmaps"
/* Where Emacs should look for its docstring file. The lisp variable
doc-directory is set to this value. */
#define PATH_DOC
"/home/kiong-ge/.local/emacs/native-comp/share/emacs/28.0.50/etc"
/* Where the configuration process believes the info tree lives. The
lisp variable configure-info-directory gets its value from this
macro, and is then used to set the Info-default-directory-list. */
#define PATH_INFO "/home/kiong-ge/.local/emacs/native-comp/share/info"
/* Where Emacs should store game score files. */
#define PATH_GAME ((char const *) 0)
/* Where Emacs should look for the application default file. */
#define PATH_X_DEFAULTS
"/usr/share/X11/%L/%T/%N%C%S:/usr/share/X11/%l/%T/%N%C%S:/usr/share/X11/%T/%N%C%S:/usr/share/X11/%L/%T/%N%S:/usr/share/X11/%l/%T/%N%S:/usr/share/X11/%T/%N%S:/usr/lib/X11/%L/%T/%N%C%S:/usr/lib/X11/%l/%T/%N%C%S:/usr/lib/X11/%T/%N%C%S:/usr/lib/X11/%L/%T/%N%S:/usr/lib/X11/%l/%T/%N%S:/usr/lib/X11/%T/%N%S"
It seems having all the path environment variables generated at build
time, that's why I am a little bit confused
On Thu, Dec 17, 2020 at 3:00 PM Eli Zaretskii <eliz@gnu.org> wrote:
>
> > From: Liāu, Kiong-Gē 廖宮毅 <gongyi.liao@gmail.com>
> > Date: Thu, 17 Dec 2020 14:48:30 -0600
> > Cc: Andrea Corallo <akrl@sdf.org>, emacs-devel@gnu.org
> >
> > It seems the %emacs_dir% part is not expanded
>
> Of course it isn't: that happens at run time, not at build time.
prev parent reply other threads:[~2020-12-17 21:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-17 1:44 Native-comp branch compilation error on Windows Liāu, Kiong-Gē 廖宮毅
2020-12-17 19:51 ` Andrea Corallo via Emacs development discussions.
2020-12-17 20:43 ` Eli Zaretskii
2020-12-17 20:48 ` Liāu, Kiong-Gē 廖宮毅
2020-12-17 21:00 ` Eli Zaretskii
2020-12-17 21:06 ` Liāu, Kiong-Gē 廖宮毅 [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CALKwrMD=iY2CgUo6JMoM9X_5Kz5t1_XHZpadxd58s4sry14s3g@mail.gmail.com' \
--to=gongyi.liao@gmail.com \
--cc=akrl@sdf.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).