Re: 32 bits time_t and Y2038 issue

Michael Schwingen <news-1513678000@discworld.dascon.de> wrote:

On 2025-03-18, David Brown <david.brown@hesbynett.no> wrote:

>
These days I happily use it on Windows with recursive make (done
/carefully/, as all recursive makes should be), automatic dependency
generation, multiple makefiles, automatic file discovery, parallel
builds, host-specific code (for things like the toolchain installation
directory), and all sorts of other bits and pieces.

 
I converted to the "recursive make considered harmful" group long ago.
Having one makefile for the whole build makes it possible to have
dependencies crossing directories, and gives better performance in parallel
builds - with recursive make, the overhead for entering/exiting directories
and waiting for sub-makes to finish piles up.  If a compile takes 30 minutes
on a fast 16-cpu machine, that does make a difference.

I do not see substantial difference in build time between a single
Makefile approach and recursive make with job server.  That is
on Linux and with optimizing compilers.  Slower filesystem
handling or ultra-fast compilers could make a difference.

Also, I am trying to be explicit in my Makefile-s.  Normal 'make'
rules check (search) for various insane possibilities, being
explict limits need for searching.

Recursive make makes a lot of sense if build must be split into
stages and when directory structure reflects dependences.

--
                              Waldek Hebisch