Re: Native compilation on Windows, was Re: Bootstrap Compilation Speed

[Phillip Lord]

"H. Dieter Wilhelm" <dieter@duenenhof-wilhelm.de> writes:

>>>> I wouldn't!
>>>> 
>>>> CACHE=-C is used only on a snapshot build. These were always built
>>>> incrementally from the previous version because I judged that the risk
>>>> of a broken build was small compared to the significant time and cost
>>>> saving that the incremental build provided.
>>>
>>> AFAIU, Dieter said he did more than one build in the same tree for
>>> several different configurations, so I suggested to eliminate the
>>> cache as a possible factor for the problems he saw in the second
>>> build.  Apologies if I misunderstood.
>>
>>
>> Oh, sure, that's fine. Just saying that the `CACHE=-C` is there for
>> mostly good reasons!
>
> I'm too inexperienced to judge the options.
>
> But, for the moment, it seems to me when the $CACHE line is active then
> there is NO native compilation going on for my builds.  (No idea why,
> I'll try to confirm this.)
>
> The current idea is to build 28.0.91 with build-zips.sh - in the usual
> way but --with-native compilation - and then copy the lisp-native/
> folder into the archive.  Then checking if such a build is running and
> actually loading the .eln files on a Windows system without MSYS/MinGW.
>
> Hmm, how can I test if Emacs is actually loading some .eln and not the
> .elc files?


If you change the configure options in build-zips.sh, I would go for a
full clean build for sure. "make extraclean" I think will do the trick,
then run build-zips.sh with modified options.

Phil