[fpc-devel] I've asked this before, but perhaps I wasn't specific enough that time: what do I *personally*, specifically need to do to ensure that a native Windows 64-bit build winds up on the FPC website for the next release?

Nikolay Nikolov nickysn at gmail.com
Fri Jan 14 05:52:39 CET 2022

On 1/14/22 06:45, Ben Grasset via fpc-devel wrote:
> On Thu, Jan 13, 2022 at 11:38 PM Nikolay Nikolov via fpc-devel 
> <fpc-devel at lists.freepascal.org> wrote:
>     For the record, I did try make cycle for ppc386 and ppcx64 on my
>     Windows 10 (with Windows Defender turned on) and both finished in
>     exactly 42 seconds :)
> Not surprising that you closed the gap a bit with your 5900X IMO, 
> although that's still a decent improvement over both of your Linux 
> results. I do think probably linking with GNU LD isn't as fast in most 
> cases as linking internally, as I mentioned before. Though using LLD 
> or mold instead of LD might be a different story.

No, it's not, because in linux I tested "make -j24 all" in the compiler 
directory, which also builds all the packages, textmode ide and 
utilities (and also does a parallel build), but in Windows I tested only 
"make cycle", like you did.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freepascal.org/pipermail/fpc-devel/attachments/20220114/acbc3796/attachment.htm>

More information about the fpc-devel mailing list