unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "T.V Raman" <raman@google.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Native Compilation And External Packages
Date: Sat, 29 May 2021 10:14:43 -0700	[thread overview]
Message-ID: <p91zgwd1myk.fsf@google.com> (raw)
In-Reply-To: <83czt95wco.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 29 May 2021 19:38:15 +0300")

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=gb18030, Size: 1207 bytes --]

Eli Zaretskii <eliz@gnu.org> writes:


The warnings are inconsistent as in:

Compiling at the command line using -f batch-byte-compile produces no
warnings; the same code produces warnings when native-emacs is run

2. I should have been more explicit re Make:
I know about -f batch-native-compile, however writing the dependency
rule is what I guess I'm confused about -- since the .eln files that
result go into the eln-cache, not the directory where the .el files
live.


>> From: "T.V Raman" <raman@google.com>
>> Date: Sat, 29 May 2021 09:28:01 -0700
>> 
>> Q: How does one write a Makefile rule for native compilation of .el
>> files in a 3rd party (external) package?
>
> Use something like
>
>   emacs -batch -l comp -f batch-native-compile FOO.el
>
>>    2. Would also be nice if warnings from byte-compilation could be
>>       consistent with  native-compilation -- I'd be happy with either solution.
>
> In what sense are they inconsistent now?  They come from
> byte-compilation, AFAIU, so they are the same warnings you are used to
> while byte-compiling...

-- 

Thanks,

--Raman(I Search, I Find, I Misplace, I Research)
7©4 Id: kg:/m/0285kf1  •0Ü8



  reply	other threads:[~2021-05-29 17:14 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-29 16:28 Native Compilation And External Packages T.V Raman
2021-05-29 16:38 ` Eli Zaretskii
2021-05-29 17:14   ` T.V Raman [this message]
2021-05-29 17:36     ` Eli Zaretskii
2021-05-29 18:52       ` Stefan Monnier
2021-05-30  1:58         ` T.V Raman
2021-05-29 18:56     ` Stefan Monnier
2021-05-30  2:06       ` T.V Raman
2021-05-30  3:05         ` T.V Raman
2021-05-29 17:00 ` Stefan Monnier
2021-05-29 17:18   ` T.V Raman
2021-05-29 18:36   ` T.V Raman
2021-05-29 18:47     ` Eli Zaretskii

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=p91zgwd1myk.fsf@google.com \
    --to=raman@google.com \
    --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).