[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [External] : Emacs pretest 28.0.91 is out

From: H. Dieter Wilhelm
Subject: Re: [External] : Emacs pretest 28.0.91 is out
Date: Thu, 13 Jan 2022 08:15:33 +0100
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.90 (gnu/linux)

Eli Zaretskii <eliz@gnu.org> writes:

>> From: "H. Dieter Wilhelm" <dieter@duenenhof-wilhelm.de>
>> Cc: Corwin Brust <corwin@bru.st>,  luangruo@yahoo.com,  stefan@marxist.se,
>>   drew.adams@oracle.com,  emacs-devel@gnu.org
>> Date: Wed, 12 Jan 2022 22:15:57 +0100
>> > I'm not sure this is correct/justified.  Wouldn't it be better to have
>> > just one build that could support both variants?  It is supposed to
>> > work that way, but I don't think anyone tested this in practice.  It
>> > would be good to see if that indeed works as intended, and if not,
>> > report the issues which prevent that.
>> I don't quite understand, does this mean that ALL .elc files are getting
>> .eln companions?  
> Not necessarily.  If you use the "normal" build procedure, only the
> Lisp files that are preloaded (and a few additional support files)
> will be natively compiled, the rest will be left as *.elc files.

Indeed, I observed this behaviour under MinGW2.

> But I'm not sure I understand why you are asking this.

I wanted to know if it makes sense (and is possible) to natively compile
all *.elc files for Windows? :-)

>> Or can this work as under Gnu-Linux with JIT compilation?
> If libgccjit is not available, Emacs should use the *.elc files.

I thought this. I'm also wondering how much the additional .eln files
will enlarge the Emacs distribution..

Thank you

Best wishes
H. Dieter Wilhelm
Zwingenberg, Germany

reply via email to

[Prev in Thread] Current Thread [Next in Thread]