Re: 32 bits time_t and Y2038 issue

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.

using ninja instead of make works even better in such a scenario.

cu
Michael
--
Some people have no respect of age unless it is bottled.